SUMMARY The Avatar OverlaySheet doesn't have a scrollbar even if the content can't be accommodated in the current area. Resizing the system settings window can work around it. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: plasma-workspace at b910507a4cd36a211b4d14ccd133c39f196033b1 KDE Frameworks Version: Qt Version: 6.5.2 ADDITIONAL INFORMATION
Can reproduce.
StackView docs say: "StackView does not inherit an implicit size from items that are pushed onto it." I have a feeling this is what we're running into.
For me it becomes scrollable if I resize the window to be larger and then smaller again.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/302
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3649
I can't help but wonder if we should port away from the sheet tech and use a regular page on the stack instead. This isn't the first silly bug we've had with it. I suspect it also won't be the last.
In this case I agree. The sheet takes up 95% of the available space anyway, which suggests that it wanted to be a page all along.
Git commit 2869a550ec4e33108f0aa0e9ee7683b785c0a45d by Harald Sitter. Committed on 04/12/2023 at 12:41. Pushed by ngraham into branch 'master'. kcms/users: derive columns count from implicitWidth otherwise **I think** we have an implicit dependency loop where the effective width of the StackView depends on its content, but its content width depends on the width of the view. meanwhile implicitWidth is simply the page width minus spacing so that is always a fixed value we can hold onto for the maximum width we may be able to occupy M +1 -2 kcms/users/src/ui/PicturesSheet.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/2869a550ec4e33108f0aa0e9ee7683b785c0a45d
Regression in Qt6.8
(In reply to Fushan Wen from comment #9) > Regression in Qt6.8 Do you mean Q6.7?
Let's get a new bug report going for that, since it'll end up being a separate issue from this one, and we also aren't formally supporting either Qt 6.7 or 6.8 yet. Thanks!