| Summary: | System Settings becomes extremely laggy when opening “Notifications” panel (LANGUAGE=zh_CN) | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kirigami | Reporter: | silvigarabis |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde, mariusz.libera, nate, notmart |
| Priority: | NOR | ||
| Version First Reported In: | 6.19.0 | ||
| Target Milestone: | Not decided | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/frameworks/qqc2-desktop-style/-/commit/ed82077889fce696f993a5376c27c13f177d5bb8 | Version Fixed/Implemented In: | 6.20 |
| Sentry Crash Report: | |||
|
Description
silvigarabis
2025-10-18 17:33:08 UTC
Confirmed with these steps A possibly relevant merge request was started @ https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/486 Git commit ed82077889fce696f993a5376c27c13f177d5bb8 by Marco Martin. Committed on 20/10/2025 at 11:03. Pushed by mart into branch 'master'. SpinBox: Make paddings integer to avoid potential polish loops This is not about pixel alignment on fractipnal scaling, but about a quirk adapting QStyle pixelmetrics, that are always integer, with QML items which can potentially have fractional sizes right padding depends from the size - styleitem.editRect.right) which will change the implicit width, which might change the width, which will change the right padding. right padding is always fixed if sizes are integer as styleitem.x + styleitem.width - styleitem.editRect.right is always the same result, but only if styleitem.width is integer, because styleitem.editRect will always be integer This is very visible on the notifications kcm with the chinese language Make sure that leftPadding and rightPadding are always rounded so this won't happen again M +3 -2 org.kde.desktop/SpinBox.qml https://invent.kde.org/frameworks/qqc2-desktop-style/-/commit/ed82077889fce696f993a5376c27c13f177d5bb8 *** Bug 510966 has been marked as a duplicate of this bug. *** |