this post was submitted on 10 Jan 2024
162 points (98.8% liked)

Firefox

16992 readers
25 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 44 points 6 months ago* (last edited 6 months ago) (6 children)

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?

[–] [email protected] 19 points 6 months ago (4 children)

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.

[–] [email protected] 8 points 6 months ago (2 children)

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.

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

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.

load more comments (1 replies)
load more comments (2 replies)
load more comments (3 replies)