diff options
| -rw-r--r-- | unstable/xdg-shell/xdg-shell-unstable-v5.xml | 10 | ||||
| -rw-r--r-- | unstable/xdg-shell/xdg-shell-unstable-v6.xml | 10 |
2 files changed, 20 insertions, 0 deletions
diff --git a/unstable/xdg-shell/xdg-shell-unstable-v5.xml b/unstable/xdg-shell/xdg-shell-unstable-v5.xml index ef0180d..59fa9de 100644 --- a/unstable/xdg-shell/xdg-shell-unstable-v5.xml +++ b/unstable/xdg-shell/xdg-shell-unstable-v5.xml @@ -478,6 +478,11 @@ If the surface was already maximized, the compositor will still emit a configure event with the "maximized" state. + + Note that unrelated compositor side state changes may cause + configure events to be emitted at any time, meaning trying to + match this request to a specific future configure event is + futile. </description> </request> @@ -500,6 +505,11 @@ If the surface was already not maximized, the compositor will still emit a configure event without the "maximized" state. + + Note that unrelated compositor side state changes may cause + configure events to be emitted at any time, meaning trying to + match this request to a specific future configure event is + futile. </description> </request> diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml b/unstable/xdg-shell/xdg-shell-unstable-v6.xml index dfaf784..7fb4658 100644 --- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml +++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml @@ -827,6 +827,11 @@ If the surface was already maximized, the compositor will still emit a configure event with the "maximized" state. + + Note that unrelated compositor side state changes may cause + configure events to be emitted at any time, meaning trying to + match this request to a specific future configure event is + futile. </description> </request> @@ -849,6 +854,11 @@ If the surface was already not maximized, the compositor will still emit a configure event without the "maximized" state. + + Note that unrelated changes in the state of compositor may cause + configure events to be emitted by the compositor between processing + this request and emitting corresponding configure event, so trying + to match the request with the event is futile. </description> </request> |