Long live Firefox and high praises to all those who develop, maintain and package it.
Release notes: “Firefox now defaults to the Wayland compositor […] It is also a known issue that windows are not correctly placed when restoring a previous session on launch.” I had been led to believe that one of Wayland’s strengths was solving the correct window coordinates save-and-restore problem. Does someone know what happened here?
I had been led to believe that one of Wayland’s strength was solving the correct window coordinates save-and-restore problem. Does someone know what happened here?
It’s literally the opposite. Windows aren’t allowed to position themselves on Wayland (because it’s unsafe or something). Window state save restoration must implemented by the compositor itself. Not sure about GNOME, but KDE doesn’t have that.
because it’s unsafe or something
It’s one of those bits that haven’t been done yet. The protocol extension is being discussed as there are a lot more different use-cases than one would think and a number of ways to do it. Wayland is great but nothing is perfect and this is one of its weaknesses: evolving it takes time as we’re afraid of getting it wrong.
Window state save restoration must implemented by the compositor itself. Not sure about GNOME, but KDE doesn’t have that.
Actually KDE has a feature where you can set which display any app shows on, and if it should be maximized horizontally or vertically or both.
I use that for Firefox specifically, as I always like it on my secondary monitor.
Just right click on the title bar of any application to get to those settings.
(I’m using KDE on Fedora.)
