After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 593629 - Use touchpad for clicks disabled by default?
Use touchpad for clicks disabled by default?
Status: RESOLVED NOTABUG
Product: gnome-control-center
Classification: Core
Component: Mouse
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-31 08:53 UTC by Dominique Leuenberger
Modified: 2009-12-15 15:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Leuenberger 2009-08-31 08:53:04 UTC 
Hi,

The mouse-properties got a new 'tickbox' to 'disable' the clicking by tap completely (I think before it was only possible to 'delay' it).

Nevertheless, the 'default' seems now to be to have this disabled? This is rather confusing to people (can be seen in several blog posts, like
http://lizards.opensuse.org/2009/08/27/clicks-with-touchpad-trick-11-2-m6/
)

any chance to get this inverted for the final 2.28 release?
Comment 1 Rastislav Krupansky 2009-08-31 09:01:19 UTC 
I´d appreciate this feature enabled by default, as in the past. IIRC, none OS has this feature disabled by default and it´s a little confusing behaviour.
Comment 2 Peter Hutterer 2009-09-09 03:22:19 UTC 
Tap-to-click enabled by default is confusing for those users that aren't aware of this particular feature (and more so that it is enabled). They get erroneous clicks without an explanation why. This is the reason tapping was disabled in the upstream driver as well.

OS X seems to have it disabled by default too (Switching to the Mac: The Missing Manual, Tiger Edition, Pogue and Goldstein, 2005, p373)
Comment 3 palfrey 2009-12-15 15:12:23 UTC 
It should probably default to whatever the upstream driver does currently on an individual system when there isn't a setting to start with, i.e. for those like me who have customised it to be enabled, then enable it, but if someone's running a stock install with the upstream default of disabled, then run with that. Probably needs a third state other than disabled/enabled as "as system" - not as user-visible, but as a behind the scenes initial default that displays as whatever the system setting is.