https://bugs.kde.org/show_bug.cgi?id=468689
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Summary|Dark mode doesn't apply |Elisa falls back to Fusion
|correctly on EndeavourOS |theme with has incorrect
| |colors when
| |plasma-integration isn't
| |used
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFIRMED
--- Comment #7 from Nate Graham <n...@kde.org> ---
I had a feeling.
Basically this is a bit of a mismatch between what KDE (and QT apps in general)
expect and how KDE apps are typically packaged.
Qt apps expect a "platform integration" tool to be installed; "Plasma
Integration" is ours. If one is not installed, the app falls back to the basic
one built into Qt and the app gets themed with the default Fusion theme with
basic Qt-provided color support. This does not work well for KDE apps that
expect for certain things provided by Plasma Integration to be present, such as
specifying the Breeze app style and richer color scheme compatibility.
We have a few options:
1. Mark plasma-integration as a mandatory dependency for Elisa
2. Change Elisa and other KDE frameworks to work better with the Fusion app
style and not have these color incompatibility issues
3. Hardcode Elisa to always use for the Breeze app style if plasma-integration
isn't detected
The issue with #1 is that it would conflict with distros that intentionally
ship a *different* platform integration tool; they would patch out this change
and things would still be broken. I guess that would be on them, them.
The issue with #2 is that it would be a lot of work for gains that would never
be visible to most users, since in general these apps are run in a Plasma
environment where Plasma Integration is already present. Also no developers are
running the app this way, so it's a largely untested codepath.
Perhaps we should do #3.
--
You are receiving this mail because:
You are watching all bug changes.
