Created attachment 142447 [details] SystemSettings left-most pixel of empty space SUMMARY In a sidebar view, when nested group of settings is opened (e.g. the topmost Global Theme, or Network Settings, or any other with an arrow indicator), and there is enough vertical space to fit all the child items in a list, then clicking on a left-most 1px of an empty area acts as a "back" button. STEPS TO REPRODUCE 1. Open System Settings. 2. Click on Any menu with an arrow, e.g. Global Theme. 3. Move the window to the left edge of your screen. 4. Move cursor to the left-most position, anywhere on an empty area under the list of KCMs. 5. Clikk OBSERVED RESULT Goes back, as if a back button was pressed. EXPECTED RESULT Nothing should happen at all. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 970M/PCIe/SSE2 ADDITIONAL INFORMATION
Now that's pretty weird.
> Now that's pretty weird. "Why do I always get the weird ones?" >:D
The way the sidebar works is as a pagestack. The left most page is the main navigation, when you click on a category the page for that category is pushed onto the stack and shifting the main page out towards the left. In other words there's a page to the left, outside the visible area of the scene - the main page is still there we just can't see it. At the very right edge of the main page is the scrollbar and that is what you are triggering when clicking. You can actually see it animating the scroll at the very end of the video. It scrolls down, away from the 'global theme' entry. Figuring out what exactly goes wrong may be a bit hellish though. Could be the mouse coordinate calculation or any of the page offsets I'd guess. Doesn't seem to affect discover though, so I suppose it's not a general kirigami problem.
This appears to have been fixed now, as I could reproduce the issue before but can't anymore.
Can confirm, not reproducible anymore. Probably one of those ScrollablePage tweaks fixed it.