Probably not anytime soon. This is just an issue to track various toolkits/clients progress.
Just a heads up that the next GStreamer release will have support for XDG shell stable in at least glimagesink and vaapisink
Annnd if this gets merged in time, GStreamer 1.16 will also have support for XDG shell in waylandsink
Seems like Gstreamer 1.16 has been released with xdg-shell stable support.
Seems like we're about ready to ditch it. I don't really care about Ozone.
Looking at that ozone code, it appears they have both v6 and stable support.
Doesn't look like it supports xdg-shell stable to me. Still think we should axe v6 though
Ah, you right. I was getting confused by seeing https://chromium.googlesource.com/chromium/src/+/master/ui/ozone/platform/wayland/host/wayland_connection.cc#648, but I forgot that got renamed to xdg_wm_base_ping.
So this commit kills chromium-ozone on sway ?
on launch I get:
ERROR:wayland_connection.cc(92)] No xdg_shell object
FATAL:ozone_platform_wayland.cc(160)] Failed to initialize Wayland platform
Is there any other way to run native wayland chromium on sway-wayland ?
Is there any other way to run native wayland chromium on sway-wayland ?
Yes: send a patch for xdg-shell stable.
Looks like Ozone has support now, which will be released in chromium 80: https://chromium-review.googlesource.com/c/chromium/src/+/1939493
There are changelogs for Qt 5.12 that mention support for xdg-shell stable if you need them:
https://wiki.qt.io/New_Features_in_Qt_5.12
https://www.qt.io/blog/2018/12/14/whats-new-wayland-platform-plugin-qt-5-12
Just an FYI, that's all.
Thanks, updated the list since this may be used as reference by other projects.
@emersion No problem. :)
Most helpful comment
Just a heads up that the next GStreamer release will have support for XDG shell stable in at least glimagesink and vaapisink