[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 David Redondo changed: What|Removed |Added Resolution|INTENTIONAL |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-systemmonitor/-/c ||ommit/27e0cce0bd0413e5a8c19 ||af4413d29689b61812e --- Comment #36 from David Redondo --- Git commit 27e0cce0bd0413e5a8c19af4413d29689b61812e by David Redondo. Committed on 12/12/2023 at 12:24. Pushed by davidre into branch 'master'. Save maximized state The hidden state is ignored to not overwrite when closing the window. The state is applied via initial properties because using a binding would create a loop and Component.onCompleted is to late. M +10 -0src/Main.qml M +3-0src/main.cpp https://invent.kde.org/plasma/plasma-systemmonitor/-/commit/27e0cce0bd0413e5a8c19af4413d29689b61812e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 David Edmundson changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||k...@davidedmundson.co.uk Status|CONFIRMED |RESOLVED --- Comment #35 from David Edmundson --- >So far KWin devs are not convinced that #1 is appropriate, This was rediscussed, with the same conclusion. #2 has not been done yet even for KDE's own apps, so the problem is not fixed. It has been done for KXmlGui. Other apps need relevant bugs filing on those applications -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Anthony Fieroni changed: What|Removed |Added CC||bvb...@abv.bg --- Comment #34 from Anthony Fieroni --- (In reply to Nate Graham from comment #33) > Not fixed; this requires one of two things to be done to fix it: > 1. KWin interprets "open window at maximum size" to be equal to "open window > in maximized state" on Wayland as it does on X11 > 2. All apps exhibiting this problem are changed to request opening in the > maximized state rather than at the maximum window size > > So far KWin devs are not convinced that #1 is appropriate, and #2 has not > been done yet even for KDE's own apps, so the problem is not fixed. I think 1. is sufficient because there is no meaning of maximize size without maximize state, i.e. no difference from user's perspective. Actually same applies to all other windows state like KWin positioning when touch edge 1/4, 1/2 i.e. when the size match a predefined state it should activate it. Actually there is (was) a problem in X11, (I'm not use it for few years) but when restart 1/2 window, it could start on its normal state (which is not 1/2 just random size), I investigate in the problem and came with conclusion especially difference between KWin sets normal state of the window which read from config its normal coordinates and size, but instead KWin should activate 1/2 state. In other hand the app (Kate) doesn't well store and read its state. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 soredake changed: What|Removed |Added CC|broaden_acid002@simplelogin | |.com| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Patrick Silva changed: What|Removed |Added Version|5.26.90 |5.27.80 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Status|NEEDSINFO |CONFIRMED --- Comment #33 from Nate Graham --- Not fixed; this requires one of two things to be done to fix it: 1. KWin interprets "open window at maximum size" to be equal to "open window in maximized state" on Wayland as it does on X11 2. All apps exhibiting this problem are changed to request opening in the maximized state rather than at the maximum window size So far KWin devs are not convinced that #1 is appropriate, and #2 has not been done yet even for KDE's own apps, so the problem is not fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Fushan Wen changed: What|Removed |Added Resolution|--- |FIXED CC||qydwhotm...@gmail.com Status|CONFIRMED |NEEDSINFO --- Comment #32 from Fushan Wen --- Anyone can confirm it's fixed in 5.27.8? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added CC||amanita+kdeb...@mailbox.org --- Comment #31 from Nate Graham --- *** Bug 473005 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Quinten Kock changed: What|Removed |Added CC||quintenk...@gmail.com --- Comment #30 from Quinten Kock --- Just chiming in to say this is still an issue, but only for some applications. For example, Dolphin behaves correctly and even restores to the right size, but System Monitor is affected, as is Elisa. GTK apps seem to handle this correctly on my Plasma Wayland desktop, at least Nautilus and Lutris do, although the latter doesn't remember the size to restore to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added CC||plata.h...@kdemail.net --- Comment #29 from Nate Graham --- *** Bug 470010 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 whyhow3@gmail.com changed: What|Removed |Added CC||whyhow3@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Patrick Silva changed: What|Removed |Added Version|5.24.90 |5.26.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added Priority|HI |NOR -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 postix changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=434116 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 --- Comment #28 from Nate Graham --- *** Bug 434762 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Nate Graham changed: What|Removed |Added Summary|On Wayland, Windows that|On Wayland, Windows that |were closed when maximized |were closed when maximized |will open in the maximized |and do not record their own |position, but not the |maximized state will open |maximized state |in the maximized position, ||but not the maximized state -- You are receiving this mail because: You are watching all bug changes.
