#1658 closed defect (fixed)
mouse events in black border around desktop area
Reported by: | mviereck | Owned by: | mviereck |
---|---|---|---|
Priority: | minor | Milestone: | 2.4 |
Component: | client | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
xpra v2.2-r17160 on debian 9
If running xpra --start-desktop
and maximizing the client window, there can be a black area around the shown desktop if the vfb X server does not provide a matching resolution.
Mouse events (moving and clicks) in the black area should not do anything, but they happen to the outer border of the desktop.
Example: mouse click in black area above clock in xfce4-panel shows calendar, but this should only happen if I click directly on the clock.
Mouse movements in black area above the panel causes highlighting of nearest panel objects.
Not really a problem so far, just different from what I would expect.
Attachments (1)
Change History (13)
comment:1 Changed 5 years ago by
Milestone: | 2.2 → 3.0 |
---|---|
Status: | new → assigned |
Changed 4 years ago by
Attachment: | black-border.jpg added |
---|
example of black border around the window contents
comment:2 Changed 4 years ago by
Description: | modified (diff) |
---|
there can be a black area around the shown desktop if the vfb X server does not provide a matching resolution.
This is less of a problem nowadays since you can:
- use Xvfb and have perfect match for any resolutions
- Xdummy now has a large set of pre-defined resolutions which should match all possible configurations with a maximum gap of 128 pixels
(converted link to an attachment so it doesn't bitrot)
comment:3 Changed 4 years ago by
This happens rather with Xwayland than with Xvfb or Xdummy as it unfortunately does not support resolution changes with xrandr.
In seamless mode for single applications I do not expect an issue as they are always scaled up to the client screen resolution. In that case I am not able to move the mouse outside of the virtual desktop.
comment:4 Changed 4 years ago by
This happens rather with Xwayland than with Xvfb or Xdummy as it unfortunately does not support resolution changes with xrandr.
Then this is an unsupported configuration, we rely on randr to make things match. Use Xvfb instead.
comment:5 Changed 4 years ago by
Use Xvfb instead.
For most things I use Xvfb or Xdummy. Xwayland has the advantage of supporting hardware acceleration, but the disadvantage of bad xrandr support.
Aside from this minor issue of mouse events at the edge in desktop mode, xpra works quite well with Xwayland. Also, xpra clients sets the window size right, the issue only appears if I maximize the window.
So far, it is fine for me, xpra handles Xwayland quite well.
comment:6 Changed 4 years ago by
Milestone: | 3.0 → 2.4 |
---|
comment:7 Changed 4 years ago by
Testing as per ticket:1656#comment:12
- I can only reproduce this bug by maximizing the window, so r19613 detects wayland / that randr doesn't work and the window is now made non-resizable, non-maximizable
- the non-opengl backends have problems rendering correctly with the offsets, new ticket: #1874
- r19615 fixes the pointer events issue: shadow and desktop servers discard events that land outside the vfb rather than clipping them (seamless servers are unchanged: the events may be outside the window but they will still land on the vfb so we still want them) - easier to test by patching
check_randr_sizes
to return True (just like #1874)
Still TODO:
- check win32 and macos shadow servers with multi-window mode (#1805) and check for regressions
- maybe handle the transition from discarded to not-discarded and back by sending cursor updates so that the client doesn't show the cursor that would apply if the pointer was still in the active region of the window? (ie: the edge of the window may have a resize handle, which is no longer relevant when hovering over the padding area since both motion and button events will be ignored there)
comment:8 Changed 4 years ago by
comment:9 Changed 4 years ago by
Owner: | changed from Antoine Martin to mviereck |
---|---|
Status: | assigned → new |
Was worth re-testing (I temporarily disabled size-hints to get black borders without using fullscreen or maximize): r19615 was buggy for the multi-monitor multi-window case (#1805), fixed in r20162.
I have not re-tested on macos shadow servers since that involves lugging too many things around. Those are similar to mswindows shadow servers anyway.
@mviereck: please close if this works for you. beta builds with these changes can be found here: https://xpra.org/beta
comment:12 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1658
Originally reported in #1656, see ticket:1656#comment:24.
If we swallow pointer motion events, there are some potential problems with seamless mode when the window size does not match its contents exactly: the virtual pointer could linger on the edge of the server side window - which could trigger unwanted behaviour.