https://bugs.kde.org/show_bug.cgi?id=503446
Lenzoid <strong.drum0...@fastmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOT A BUG |DUPLICATE
--- Comment #4 from Lenzoid <strong.drum0...@fastmail.com> ---
Hi Piotr, thanks for taking the time and testing this out on such a recent
system like Neon. That's really cool. I'm by no means an expert on this, but it
seems that this is just one of the messy things inherited from the X11 era,
where windows could place themselves and many making their own implementations
on how they remember position.
Nate has written an explanation about this, giving some background about how
positioning windows is different in X11 than in Wayland:
"Native Wayland windows are not allowed to determine where to place themselves
on screen at all; the compositor does this."
https://invent.kde.org/ngraham/canned-responses#user-reports-that-wayland-app-doesnt-remember-its-window-position-observes-that-it-works-on-x11-for-them-and-requests-an-explanation-of-why-theres-a-difference
>From my first tests, a possible solution (not remembering per se but an initial
positioning on session start) for us users could be System Settings > Window
Management > Window Rules > Add new... > Detect Window Properties and click the
window which position you wish to be enforced. Click the Plus and check mark
buttons on Window class, Position, Size etc. Haven't tried this for Firefox
windows but I imagine it's difficult identifying your three different windows.
Maybe this helps you, it did for me.
*** This bug has been marked as a duplicate of bug 15329 ***
--
You are receiving this mail because:
You are watching all bug changes.
