You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been waiting for tagged wayland-protocols releases, though I don't know if that's necessary.
Removing the wlr protocols like that isn't really appropriate though. Even if a protocol is just renamed without change to the ext namespace, the old version is still needed for the time being to support existing compositors. (At some point perhaps it could be removed; but that would also be a breaking API change.) In the case of foreign toplevel, wlr-foreign-toplevel-management-unstable-v1 supports things that ext-foreign-toplevel-list-v1 doesn't. The ext protocol for now provides less information, and doesn't have requests to set anything about windows.
Interesting, yeah I'm not sure what the game plan is for migrating to ext-data-control for example. Will compositors and clients be in a weird state where they need to support both for a while?
https://gitlab.freedesktop.org/wayland/wayland-protocols
Also it looks like a few protocols can be removed from wayland_protocols_wlr as they were promoted to core:
foreign_toplevel
-> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/staging/ext-foreign-toplevel-list/ext-foreign-toplevel-list-v1.xmldata_control
-> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/staging/ext-data-control/ext-data-control-v1.xmlThe text was updated successfully, but these errors were encountered: