The Ozone/Wayland implementation had a few places where the Wayland
objects were bound without proper checking for their versions. That was
part of the technical debt not addressed before, and ended up causing
the issue explained in the linked crbug: the compositor terminates the
client that binds to the protocol that it does not actually support.
This patch fixes the issue by adding the necessary checks in all places
where they were missing. Also a convenience macro for validating the
version is proposed.
The Ozone/Wayland implementation had a few places where the Wayland objects were bound without proper checking for their versions. That was part of the technical debt not addressed before, and ended up causing the issue explained in the linked crbug: the compositor terminates the client that binds to the protocol that it does not actually support.
This patch fixes the issue by adding the necessary checks in all places where they were missing. Also a convenience macro for validating the version is proposed.
author Alexander Dunaev
Backport patch to fix this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1279574
Signed-off-by: MarkusVolk f_l_k@t-online.de