protocol: wl_subsurface will never be focused
The spec does not describe which actions cause the compositor to assign keyboard focus to a surface, leaving this up to the compositor. Compositors differ in their behavior when the user clicks on a sub-surface. Some will move the keyboard focus to the subsurface whereas others will only ever assign the keyboard focus to toplevel surfaces. Some applications (e.g. firefox) seem to require the second behavior. This patch specifies that sub-surfaces never get the keyboard focus. Signed-off-by: Julian Orth <ju.orth@gmail.com>
This commit is contained in:
parent
86588fbdeb
commit
6626d4d98c
|
@ -3078,6 +3078,8 @@
|
||||||
|
|
||||||
If the parent wl_surface object is destroyed, the sub-surface is
|
If the parent wl_surface object is destroyed, the sub-surface is
|
||||||
unmapped.
|
unmapped.
|
||||||
|
|
||||||
|
A sub-surface never has the keyboard focus of any seat.
|
||||||
</description>
|
</description>
|
||||||
|
|
||||||
<request name="destroy" type="destructor">
|
<request name="destroy" type="destructor">
|
||||||
|
|
Loading…
Reference in New Issue
Block a user