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

--- Comment #2 from Daniel <siliz...@mail.com> ---
(In reply to Nate Graham from comment #1)
> Thanks for registering your opinion. I don't think this will be changing
> though.
> 
> If you want to change it, you can do so in three clicks: open System
> Settings, make the change, click "Apply". That's pretty simply in terms of
> giving users choice and putting them in control.

Hi Nate,

Thanks again for your reply. I understand your point, but I believe it still
misses the core issue.

Yes, technically it's just three clicks to change the setting — but that's not
the real problem. The issue is that KDE silently changed a decades-old default
without notifying the user or offering a choice during first setup.

KDE has always been about freedom and flexibility. But users can only be in
control if they are aware that something fundamental has changed. Altering such
a long-standing UX behavior — like switching from single-click to double-click
— without any dialog or heads-up doesn’t feel empowering. It feels confusing
and inconsistent, especially to long-time KDE users.

And while it's true that the setting can be changed manually, **defaults still
matter**. They shape:
– the experience for new users unfamiliar with KDE’s historical defaults,  
– the relevance of existing documentation and tutorials,  
– and KDE’s identity as a distinct desktop, not a clone of mainstream
environments.

Also, and importantly: **Even after re-enabling single-click**, it currently
**doesn't behave properly in Dolphin**.  
There's a bug where clicking a file or folder in single-click mode **sometimes
results in other directory levels or unrelated entries being unexpectedly
selected or highlighted**.  
This makes navigation inconsistent and clearly shows that the feature is not
fully functional in its current state.

Beyond that, single-click behavior is also an **accessibility feature** for
many users.  
It requires fewer fine motor actions, is faster, and is often preferred by
users with physical limitations.  
This makes the silent change to double-click not only a UX regression, but also
an accessibility concern — and those should always be treated with particular
care.

Finally, when user feedback like this is immediately marked as resolved and
closed, it doesn’t feel like community input is truly welcome.  
KDE is an open-source project, but openness is not just about source code —
it’s about listening, engaging with users, and staying true to KDE’s founding
principles.

I hope the team will reconsider not just the default itself, but also how such
changes are communicated and handled.  
A simple first-run dialog offering the choice would be a respectful and
KDE-like solution.

Thanks again for reading.

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

Reply via email to