• andrew@lemmy.stuart.funEnglish
        2·
        1 year ago

        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.

    • spez@sh.itjust.worksEnglish
      1·
      1 year ago

      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.firefox

  • AutoTL;DR@lemmings.worldBEnglish
    11·
    1 year 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!

  • highduc@lemmy.ml
    1·
    1 year ago

    Nice! Hope they fix the bug where opening a new tab with the MMB freezes the whole browser!