[winswitch] Google chrome can't resize
antoine at nagafix.co.uk
Fri Jun 19 14:40:41 BST 2015
On 19/06/15 12:31, John Smith wrote:
> I'm running xpra 0.15.0 r9556 release version for both server(trusty) and
> client(MS Windows 7 64bit).
> I have some problems with it.
> 1. I found that Firefox, xterm can resize but the Chrome can not.
That's a known issue with non-X11 clients: 0.15 now supports
Which chrome uses to trigger a move or resize.
This works fine for X11 clients which generally support the feature
(most window managers do nowadays), but this needs to be worked around
for OSX and win32:
I am hoping to have this implemented in time for 0.16
At this point you may question why we don't turn off the feature if the
client does not support it... and the answer is that we cannot: this
property is read by the application when it starts, which may well be
before the client has connected...
I may still add a environment variable to turn this off globally,
applications like chrome should then revert to client-side managed move
and resize. (and the window will then get its double title bar back..)
> 2. If use encode=rgb, compression=lz4, and :
> a. Play the Firefox ( not maximize), everything is great and fast.
> b. Play the Firefox ( maximize), it seems slower than (a) and a bit lag.
> The resolution of my client is 1366x768
What do you mean by "Play the Firefox"? Play a video? Scroll a page?
The logic which adjusts compression quality, speed and the auto-refresh
delay takes into account whether the window is fullscreen / maximized /
It is possible that this has regressed somehow. What exactly "seems
slower"? We are currently tracking down a performance regression in
0.15, this could well be it.
> Except those problems, I feel the new version is faster than 0.14.x. It's
> so good.
> Thank you,
> shifter-users mailing list
> shifter-users at lists.devloop.org.uk
More information about the shifter-users