- cross-posted to:
- linux
- cross-posted to:
- linux
You must log in or # to comment.
You can set MOZ_ENABLE_WAYLAND=1 to have it today!
How do you make it permanent though?
You can always add the env var in /etc/profile, though there are likely more fine grained approaches (like editing the firefox.desktop file) that won’t set vars for everything.
That’s described in the linked article. You can add it to the environment variables in the bash profile, but I put it in the KDE environment variables in
$HOME/.config/plasma-workspace/env/.What do you mean?
Also, if using the flatpak version, you can use flatseal to give it access to that variable under “Environment” or use
flatpak override --env=MOZ_ENABLE_WAYLAND=1 org.mozilla.firefoxYou could do that years ago. I’ve been using Wayland for 1+year and its solid
Yes, but you can also do it today if you didn’t do it years ago :)
This is the best summary I could come up with:
Firefox 121 is aiming to ship with Wayland support enabled by default rather than falling back to XWayland on modern Linux desktops.
So far things are looking up for this indeed remaining the case for next month’s Firefox 121 stable release.
This native Firefox Wayland support allows for touchpad and touchscreen gestures, swipe-to-nav, per-monitor DPI settings, better graphics performance and more.
With time the Firefox Wayland support has matured quite well and is in robust shape now.
The meta bug tracker is tracking a few bugs in recent days including the input method window position lags behind, an unconfirmed Firefox crash when dragging the window across multiple monitors, etc, but hopefully they will be resolved and/or not lead to a last minute change of defaults for Firefox 121.
Firefox 121 is planned for release on 19 December as what would make a great Christmas present with Wayland support enabled by default.
The original article contains 240 words, the summary contains 151 words. Saved 37%. I’m a bot and I’m open source!
Nice! Hope they fix the bug where opening a new tab with the MMB freezes the whole browser!
Any progress on the chromium side yet?
