*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. take chrome based window 2. drag it to the side to do a split screen window (try a few times) OBSERVED RESULT window snaps to screen but window contents are drawn displaced down by the hight of the panel EXPECTED RESULT window should be drawn from where it is located SKDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 wayland ADDITIONAL INFORMATION default window compositor in use only happens with chrome windows sometimes it doesnt happen window size is correct
Hi - with this issue, do the window controls actually still reside in the intended places? e.g. If you click where a tab should be, instead of where it's displaced down on the screen, does it activate? I'm wondering if this might be the same core issue as https://bugs.kde.org/show_bug.cgi?id=499039 ?
Yes. This is related. Chrome window and electron apps are affected. Ive since moved to firefox but can report issues Sent from my iPad > On Mar 25, 2025, at 10:47 PM, John Kizer <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=492232 > > John Kizer <john.kizer@proton.me> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC| |john.kizer@proton.me > > --- Comment #1 from John Kizer <john.kizer@proton.me> --- > Hi - with this issue, do the window controls actually still reside in the > intended places? e.g. If you click where a tab should be, instead of where it's > displaced down on the screen, does it activate? > > I'm wondering if this might be the same core issue as > https://bugs.kde.org/show_bug.cgi?id=499039 ? > > -- > You are receiving this mail because: > You reported the bug.
Thanks - merging these together for improved visibility *** This bug has been marked as a duplicate of bug 499039 ***