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.
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.
Sure, it’s hard to craft a perfect solution. However the status quo for a long time was that applications were doing it themselves. And Wayland took it away without providing a replacement.
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.
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.
Sure, it’s hard to craft a perfect solution. However the status quo for a long time was that applications were doing it themselves. And Wayland took it away without providing a replacement.
Better this way honestly