Summary: | Cannot exit from fullscreening when a client fullscreened from maximize | ||
---|---|---|---|
Product: | Wayland | Reporter: | Anu Reddy <anasuyax.r.nannuri> |
Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | maximize-to-fullscreen |
Description
Anu Reddy
2014-05-07 22:07:55 UTC
Created attachment 98646 [details]
maximize-to-fullscreen
I investigated this a little bit, but I'm not sure what is the proper solution. On the client side, the window frame is changed on the frame resize handler, which is triggered by a configure event sent when the surface state changes to maximized or fullscreen. The server, however, doesn't send a configure event when the surface goes from fullscreen to non-fullscreen, even it has the maximized state on. One solution would be to send the configure event when removing the fullscreen state if the surface is maximized. Another would be to make the client remember it is maximized and what size it was and change back to that state when it decides to no longer be fullscreen. Closing the bug. This is no longer reproducible on following environment. wayland (HEAD) remotes/origin/HEAD-0-g6d0f298 drm (HEAD) heads/master-16-gd686160 mesa (HEAD) remotes/origin/10.2-0-gd82ca4e libva (HEAD) libva-1.3.1-0-g053f70f intel-driver (HEAD) 1.3.1-0-ga720bc8 cairo (HEAD) heads/1.12-0-g59e2a93 libinput (HEAD) heads/master-163-gbb10ec8 weston (HEAD) remotes/origin/master-0-g652c794 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.