<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Port backend to use xdg-shell unstable v6" href="https://bugzilla.gnome.org/show_bug.cgi?id=769937#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: Port backend to use xdg-shell unstable v6" href="https://bugzilla.gnome.org/show_bug.cgi?id=769937">bug 769937</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>(In reply to Matthias Clasen from <a href="show_bug.cgi?id=769937#c19">comment #19</a>) > Review of <a href="attachment.cgi?id=333364&action=diff" name="attach_333364" title="wayland: Port to xdg_shell unstable v6">attachment 333364</a> <a href="attachment.cgi?id=333364&action=edit" title="wayland: Port to xdg_shell unstable v6">[details]</a> <a href='review?bug=769937&attachment=333364'>[review]</a> [review]: > > do we stop working with any current (non-shell) compositors by bumping the > xdg-shell version ? We wont work on weston 1.11, but will work with 1.12 which will support unstable v6. I'd guess we will stop working on most compositors really, but that's a fundamental issue with relying on xdg-shell before it was declared stable. Eventually we have to break the world, and (hopefully only once) again for the next backward incompatible xdg-shell version. The alternative is to add a "best-effort" wl_shell fallback, but that'll work a lot worse than falling back to X11.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>