If X11 support is a concern, at least a configurable toggle should be made available to highlight that a tradeoff between security and compatibility has been made.
Currently, users must enter MOZ_ENABLE_WAYLAND=1 into MB's env vars to force it to use Wayland. It is also not obvious that xWayland is being used. I myself only discovered this when troubleshooting for #134.
On Linux, MB appears to default to xWayland. Type in
about:support
, Graphics > Window Protocol to verify.As pointed out in https://discuss.privacyguides.net/t/mullvad-browser-on-wayland/12335, MB being a privacy focused browser, should naturally prefer Wayland over xWayland for its improved security.
If X11 support is a concern, at least a configurable toggle should be made available to highlight that a tradeoff between security and compatibility has been made. Currently, users must enter
MOZ_ENABLE_WAYLAND=1
into MB's env vars to force it to use Wayland. It is also not obvious that xWayland is being used. I myself only discovered this when troubleshooting for #134.