Summary: | Always on top is not respected | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | viktor.horsmanheimo |
Component: | core | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | nate |
Priority: | NOR | ||
Version: | 5.27.4 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
viktor.horsmanheimo
2023-05-16 20:06:48 UTC
There may be some confusion here; "always on top" doesn't mean that windows lower in the stacking order aren't resizable. It just means that the window marked as "always on top" is never overlapped by another window going over it. (In reply to Nate Graham from comment #1) > There may be some confusion here; "always on top" doesn't mean that windows > lower in the stacking order aren't resizable. It just means that the window > marked as "always on top" is never overlapped by another window going over > it. It seems to have disappeared after restart, but it's not that the lower stacking order shouldn't be resizable, but that you literally clicked through the window. The top window was not registering the clicks, sadly I do not have a video of this. That's odd. What part of the window clicked through? An area that was clearly opaque, or an area around the edges, like in the shadow? (In reply to Nate Graham from comment #1) > There may be some confusion here; "always on top" doesn't mean that windows > lower in the stacking order aren't resizable. It just means that the window > marked as "always on top" is never overlapped by another window going over > it. Never mind, I just figured out how to reproduce the issue, it has to do with multiple monitors. You need to move the window to the second screen and back. (In reply to Nate Graham from comment #3) > That's odd. What part of the window clicked through? An area that was > clearly opaque, or an area around the edges, like in the shadow? I'll record a video.(In reply to Nate Graham from comment #3) > That's odd. What part of the window clicked through? An area that was > clearly opaque, or an area around the edges, like in the shadow? I made a video to show the POC of it https://youtu.be/HlY1U5E1UnY. Thanks, that;s helpful. Let's do some investigation. Can you try the following: - Unset "always on top" for that window and see if it still happens - Set "always on top for another window" and see if it still happens - Try to make it happen with another window that doesn't have "always on top" - Try all of the following on Wayland and see if it still happens (In reply to Nate Graham from comment #6) > Thanks, that;s helpful. Let's do some investigation. Can you try the > following: > - Unset "always on top" for that window and see if it still happens > - Set "always on top for another window" and see if it still happens > - Try to make it happen with another window that doesn't have "always on top" > - Try all of the following on Wayland and see if it still happens 1. Does not seem to happen without always on top 2. It does not seem to happen with two always on top windows, I believe it's due to the fact that the lower one having to be moved offscreen. If you move the top one it does not seem to happen. 3. It seems to work with any program that does not have a custom window theme. Tested with firefox, thunderbird and discord that it works and that it does not work with steam. 4. I don't currently have a wayland machine, I'll try to set one up, I'll get back to you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |