Bug 509881 - Metabug: QColorDialog no longer remembers custom colors globally, so each implementation needs to do it manually
Summary: Metabug: QColorDialog no longer remembers custom colors globally, so each imp...
Status: REPORTED
Alias: None
Product: kde
Classification: I don't know
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR task
Target Milestone: ---
Assignee: Unassigned bugs
URL: https://codereview.qt-project.org/c/q...
Keywords:
Depends on: 502957 509709 509811
Blocks:
  Show dependency tree / graph
 
Reported: 2025-09-24 18:41 UTC by Nate Graham
Modified: 2025-09-29 16:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2025-09-24 18:41:48 UTC 
https://codereview.qt-project.org/c/qt/qtbase/+/626629 changed QColorDialog to stop saving and loading custom colors globally. As a result, KDE is now receiving bug reports from all quarters about custom colors no longer being saved.

Assuming this behavior won't be reverted, we need to write some code to save and restore custom colors.

Options I can see:
1. Restore the former behavior by making a wrapper around QColorDialog in plasma-integration that saves and restores custom colors globally, so no changes are required in KDE apps.
2. Make C++ and QML wrappers around QColorDialog that does all of this automatically on behalf of the calling app, and then port all apps to use it.
3. Leave it up to each individual app to handle it.