[RFC] Implementing Wayland Security Module
Bill Spitzak
spitzak at gmail.com
Mon Mar 9 13:24:49 PDT 2015
Fullscreen is not any more of a problem than resizing, except for the
fact that a bunch of people think "fullscreen" == "always on top". Due
to child windows this is not going to be true, compositors have to
support floating windows atop the fullscreen one.
People are being confused by the panels and "layers". Layers are NOT the
way to do this. Instead the panel has a rule about where it is placed in
the surface stack: if there are any fullscreen windows it is placed
below the bottom-most one. If there are no fullscreen windows it is
placed atop all windows. The order between fullscreen and normal windows
is arbitrary.
A hostile client must not be able to prevent something like Alt+Tab from
raising another window atop it, and should be prevented from rapidly
raising it's window (the current fullscreen request is really doing a
raise request which is why it is a problem).
On 03/09/2015 12:52 PM, Manuel Bachmann wrote:
> - critical actions on the outputs : fullscreen, resolution change...
A popular one missing from your list is global shortcut keys.
More information about the wayland-devel
mailing list