https://bugs.kde.org/show_bug.cgi?id=429665
Tyson Tan <tyson...@tysontan.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tyson...@tysontan.com
--- Comment #2 from Tyson Tan <tyson...@tysontan.com> ---
I do have a question though. If this is supposed to be handled by Libinput and
distro, then how is it while on the same system, GNOME has tap-to-click enabled
by default, but not Plasma?
>From my decades' experience working as an IT support and system administrator,
I have never came across a laptop with its factory system not enabling
tap-to-click by default.
Not only that, nowadays, most new laptops do not have physical buttons visible
around the touchpad's surface. Some touchpads can only do gesture taps.
For example, on my Lenovo Yoga 730 (which was a 2018 model, mind you), already
has no visible buttons. The whole touchpad is a big continuous piece. So if I
want to mouse click without tap-to-click, I have to press really hard on the
bottom corners -- which 100% of the time, will cause the cursor to move a bit,
so I can never click exactly on the place I want to click. Not to mention
dragging, it's impossible to drag accurately with so much force constantly
needed to press down the dang thing. Just imagine the usability issue it will
cause in productivity apps with a lot of tiny options.
Most users, at least in my organization and my relatives, do not know, or
simply just forgot about the touchpad on their laptops can be pressed down --
myself included until I encountered this issue yesterday.
Without tap-to-click, I found it impossible to use a modern laptop with no
individual touchpad buttons. Maybe you are using some kind of Thinkpad, but
Thinkpad is always an exception, not the standard when it comes to touchpads.
In my opinion, this is a major usability issue and certainly should be a
counted as a 15 minutes bug -- heck, it's a 5 seconds bug really!
I sincerely implore you to review, re-investigate, and reconsider this issue.
--
You are receiving this mail because:
You are watching all bug changes.
