summaryrefslogtreecommitdiffstats
path: root/audio/out
diff options
context:
space:
mode:
authorDudemanguy <random342@airmail.cc>2021-03-02 16:38:54 -0600
committerDudemanguy <random342@airmail.cc>2021-03-02 16:40:13 -0600
commit99968e1ce5b40cc806651a053aaa337d104abfe5 (patch)
tree8949360935e2ddb060e8c5d79d365973c0466f09 /audio/out
parent0888e53fc485fa08e882e4970c53c72c20bd8a06 (diff)
downloadmpv-99968e1ce5b40cc806651a053aaa337d104abfe5.tar.bz2
mpv-99968e1ce5b40cc806651a053aaa337d104abfe5.tar.xz
wayland: no mouse dragging in fullscreen/maximized
The wayland code takes mouse dragging into account in order to trigger a client-side request for a window move or window resize. According to the xdg-shell spec*, "[t]he server may ignore move[/resize] requests depending on the state of the surface (e.g. fullscreen or maximized)". Since it is not actually a hard requirement, that means the compositor could actually respond to a clientside move/resize request even if the mpv window was fullscreen. For example, it was pointed out that in sway, if mpv is a floating window, you could drag it around off screen even though the window is fullscreen. This kind of behavior does not really have any practical use. A user can should pan a video if he/she wishes to move its orientation while fullscreen (or maximized for that manner). Naturally, a maximized or fullscreened window should never be manually resized (every compositor likely ignores this anyway). The fix is to simply just not trigger the smecial mouse dragging case if the wayland surface is fullscreened or maximized. *:https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/master/stable/xdg-shell/xdg-shell.xml
Diffstat (limited to 'audio/out')
0 files changed, 0 insertions, 0 deletions