https://bugs.kde.org/show_bug.cgi?id=340982

--- Comment #253 from Nate Graham <n...@kde.org> ---
We can indeed implement option 1 and fix this issue for KDE apps.

If your perspective is "I would rather have it work the way I want at least
some of the time than none of the time", that's valid.

The problem is that if we make this possible to satisfy those people, we're
making the system more confusing for people who don't have that preference, or
don't even know that that preference is a thing that can exist. 

Gradually we're trying to move away from what I call "broken promise" global
options: options that are presented as global in scope but really aren't
because they only affect some parts of the system. Experience shows that these
options are a recurring source of bug reports from normal users as well as
picky technical users who care a lot about consistency.

When we can't fully get rid of kinds of options, we try to add textual
explanations, but even those are imperfect. Experience also shows that even if
we did something super in-your-face and added a giant banner in the Region &
Language KCM that said:

"ALERT! Changing this only affects KDE apps! It will not affect the way dates
are expressed in any non-KDE app such as Thunderbird, Firefox, Chrome,
LibreOffice, and Blender"

...then I can 100% guarantee you that we would *still* get bug reports from
confused users complaining that Thunderbird, Firefox, Chrome, LibreOffice, and
Blender don't respect their date display preferences. And we would have to
explain the underlying reason over and over again.

So for you folks who want it to at least work some of the time because some is
better than none, I understand your perspective, but hopefully you can see how
satisfying this preference would make the system less coherent to people
without that preference.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to