cross-posted from: https://programming.dev/post/5946015
Guardrails have been in place where the Firefox browser has enabled Wayland by default (when running on recent GTK versions) but as of today that code has been removed…
cross-posted from: https://programming.dev/post/5946015
Guardrails have been in place where the Firefox browser has enabled Wayland by default (when running on recent GTK versions) but as of today that code has been removed…
🤖 I’m a bot that provides automatic summaries for articles:
Click here to see the summary
Guardrails have been in place where the Firefox browser has enabled Wayland by default (when running on recent GTK versions) but as of today that code has been removed… Firefox will try to move forward with stable releases where Wayland will ship by default!
Mozilla Bug 1752398 to “ship the Wayland backend to release” has been closed this evening!
After the ticket was open for the past two years, it’s now deemed ready to hopefully ship enabled for Firefox 121!
This patch drops the “early beta or earlier” check to let Wayland support be enabled by default when running on recent GTK versions (GTK 3.24.30 threshold).
Firefox 121 is due for release around 19 December and if all continues to hold, it will finally ship with the Wayland back-end enabled by default as another big step forward.
With KDE Plasma 6.0 using Wayland by default, XWayland rootful mode improving, and other (X)Wayland progress, 2024 could very well be the year of Wayland shining in the Linux desktop limelight.
Saved 0% of original text.
Still a good bot. pats diodes