SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Mozilla Firefox 116 To Allow For Wayland-Only Builds
Code:
Another exciting milestone has been reached on Mozilla's long journey of improving the native Wayland
support for the Firefox web browser on Linux.
With the Firefox 116 release, it will now be possible to enable Wayland-only Linux builds of Firefox.
To this point even if caring just about Wayland support, the X11 dependencies have still been pulled
into the Firefox builds. But now it's possible with the latest Firefox development code to specify
"cairo-gtk3-wayland-only" if wanting to exclusively support Wayland without all the baggage of X.Org.
News from 15.0 /testing/ packages:
firefox-115.0.3esr now identifies blackbox as a desktop environment, where previous versions reported "unknown".
Here, about:support now reports this:
Quote:
Desktop Environment - blackbox 0.77
So now there's at least some hope that GNOME will not be the only officially supported environment.
Something changed fairly recently with how firefox uses alsa device.
Previously, audio/video playback in firefox took control over the device, and denied other applications access to device.
Now, video playback in firefox works without taking exclusive control over the device and the system now allows audio playback from 2 sources at the same time.
This is without libpulse BTW, not sure if firefox changed something or alsa stack changed to support multiple outputs.
Packages used for testing:
Mozilla Might Finally Enable Firefox's Wayland Backend Soon
Code:
While some Linux distributions like Fedora and Arch are enabling
the native Wayland back-end for Firefox by default, upstream Firefox
continues to not enable this Wayland support as part of their default builds.
But -- at long last -- that might finally change soon.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Rep:
Quote:
Firefox Is Going To Try And Ship With Wayland Enabled By Default
By Michael Larabel. 13 November 2023.
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! ................
I don't know if it's on the brink or not but I access one site (government) I need to access I get this:
Quote:
Our website has detected that you are using an unsupported browser that will prevent you from accessing certain features. An update is not required, but it is strongly recommended to improve your redacted experience.
The current list of browsers supported by redacted includes:
• Chrome 72 or later
• Edge 80 or later
So far no issues with site usage.
Last edited by chrisretusn; 12-06-2023 at 02:16 AM.
If you want to run Firefox under Wayland, as oppose to xwayaland, use this..
Code:
export MOX_ENABLE_WAYLAND=1
After, or anytime, you can check what window protocol Firefox is using by going to "about:support" in Firefox.
Personally I found this well worth it, as performance (on an older machine) is notably better on Wayland than on xwayland. This especially applies if you are interested in hardware acceleration in Firefox, but should be the same generally.
Last edited by zeebra; 12-06-2023 at 04:22 AM.
Reason: wrong code brackets
I forgot about this thread, so here is a tip I have this buried in another thread.
If you are using an old style Window Manager (twm, vtwm, mwm...) and have "AutoRaise" enabled, you may have noticed issues with Menus in Firefox. How to fix is noted below. This came from the vtwm mail list. FWIW, for me, fvwm works fine without doing this since its autoraise is a module.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.