For most apps there’s no difference, but dealing with multi-window apps that can spawn new windows, merge them, display video content in its own window etc. there’s a lot of communication that Firefox has to do with the technology that draws its window to the screen.
I guess before now, default Firefox setups would’ve used XWayland to translate those communications which would’ve worked fine if not for some overhead and edge cases. This would make Firefox a truly Wayland-native application, when running on Wayland.
Finally. I was having some weird graphical glitches, so I switched it to the Wayland backend, and I’ve not noticed any issues. It’s totally stable (at least for me).
only glitch recently is that I couldn’t get multi-account containers to work. 2 years ago I couldn’t even open setting’s menu under wayland, so it’s been evolving
And it needs even less memory than Electron, even if it runs as an own instance with a different profile! I replaced Discord with it a year ago and it’s much better in literally every way. I just wish there would be a FF alternative for Electron.
Add comment