10-31-2019, 09:09 PM
Firefox tips for Fedora 31
<div><p>Fedora 31 Workstation comes with a Firefox backend moved from X11 to Wayland by default. That’s just another step in the ongoing effort of moving to Wayland. This affects GNOME on Wayland only. This article helps you understand some changes and extra steps you may wish to take depending on your preferences.</p>
<p> <span id="more-29565"></span> </p>
<p>There is a <em>firefox-wayland</em> package available to activate the Wayland backend on KDE and Sway desktop environments.</p>
<p>The Wayland architecture is completely different than X11. The team merged various aspects of Firefox internals to the new protocol where possible. However, some X11 features are missing completely. For such cases you can install and run <em>firefox-x11</em> package as a fallback.</p>
<p>If you want to run the Flash plugin, you must install the <em>firefox-x11</em> package, since Flash requires X11 and GTK 2. Wayland also has a slightly different drag and drop behavior and strict popup window hierarchy.</p>
<p>Generally, if you think Firefox is not behaving like you want, try the <em>firefox-x11</em> package. In this case, ideally you should report the misbehavior in <a href="http://bugzilla.redhat.com/">Bugzilla</a>.</p>
<p>The Wayland architecture comes with many benefits, and overcomes many limitations of X11. For instance, it can deliver smoother rendering and better HiDPI and screen scale support. You can also enable EGL hardware acceleration on Intel and AMD graphics cards. This decreases your power consumption and also gives you partially accelerated video playback. To enable it, navigate to <a href="config">about:config</a>, and search for <em>layers.acceleration.force-enabled</em>. Set this option to <em>true</em> and restart Firefox.</p>
<p>Brave users may wish to try the Firefox next-generation renderer, called WebRender, written in Rust. To do that, search for <em>gfx.webrender.enabled</em> and <em>gfx.webrender.all</em> in <a href="config">about:config</a>. Set them to <em>true</em>, then cross your fingers and restart Firefox.</p>
<p>But don’t worry — even if Firefox crashes at start after these experiments, you can launch it in safe mode to reset these options. Start Firefox from a terminal using the following command:</p>
<pre class="wp-block-preformatted">$ firefox -safe-mode</pre>
</div>
https://www.sickgaming.net/blog/2019/10/...fedora-31/
<div><p>Fedora 31 Workstation comes with a Firefox backend moved from X11 to Wayland by default. That’s just another step in the ongoing effort of moving to Wayland. This affects GNOME on Wayland only. This article helps you understand some changes and extra steps you may wish to take depending on your preferences.</p>
<p> <span id="more-29565"></span> </p>
<p>There is a <em>firefox-wayland</em> package available to activate the Wayland backend on KDE and Sway desktop environments.</p>
<p>The Wayland architecture is completely different than X11. The team merged various aspects of Firefox internals to the new protocol where possible. However, some X11 features are missing completely. For such cases you can install and run <em>firefox-x11</em> package as a fallback.</p>
<p>If you want to run the Flash plugin, you must install the <em>firefox-x11</em> package, since Flash requires X11 and GTK 2. Wayland also has a slightly different drag and drop behavior and strict popup window hierarchy.</p>
<p>Generally, if you think Firefox is not behaving like you want, try the <em>firefox-x11</em> package. In this case, ideally you should report the misbehavior in <a href="http://bugzilla.redhat.com/">Bugzilla</a>.</p>
<p>The Wayland architecture comes with many benefits, and overcomes many limitations of X11. For instance, it can deliver smoother rendering and better HiDPI and screen scale support. You can also enable EGL hardware acceleration on Intel and AMD graphics cards. This decreases your power consumption and also gives you partially accelerated video playback. To enable it, navigate to <a href="config">about:config</a>, and search for <em>layers.acceleration.force-enabled</em>. Set this option to <em>true</em> and restart Firefox.</p>
<p>Brave users may wish to try the Firefox next-generation renderer, called WebRender, written in Rust. To do that, search for <em>gfx.webrender.enabled</em> and <em>gfx.webrender.all</em> in <a href="config">about:config</a>. Set them to <em>true</em>, then cross your fingers and restart Firefox.</p>
<p>But don’t worry — even if Firefox crashes at start after these experiments, you can launch it in safe mode to reset these options. Start Firefox from a terminal using the following command:</p>
<pre class="wp-block-preformatted">$ firefox -safe-mode</pre>
</div>
https://www.sickgaming.net/blog/2019/10/...fedora-31/