Bug 85537

Summary: Accessibility: hold-to-right click implementation
Product: Wayland Reporter: Peter Hutterer <peter.hutterer>
Component: libinputAssignee: Wayland bug list <wayland-bugs>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: medium CC: bugzilla, peter.hutterer, samuel.thibault
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Peter Hutterer 2014-10-28 01:32:55 UTC 
From https://help.gnome.org/users/mousetweaks/stable/mouse-a11y-functions-description.html.en#mouse-a11y-ssc-description

"When the user activates this feature, he will be able to perform secondary clicks by using the primary mouse button. This is especially useful for users that have only one mouse button at their disposal."

Is this something that's best in libinput or better off in the compositor?
Comment 1 Rui Tiago Matos 2014-10-29 10:10:10 UTC 
Given the caveats described in the  "Differences To The Normal Secondary Click" section of that document, I'd say that this should even be a client feature (i.e. toolkit) which would allow apps to avoid those caveats.

That said, and given that this would mean the same work would have to be done for all toolkits and that users of the feature are likely already used to the current behavior (perhaps even because it's the same on other systems?) maybe it is better to do it in the compositor.
Comment 2 Peter Hutterer 2014-11-02 22:45:56 UTC 
I think the compositor is the safer option here as it guarantees the feature is reliable and globally available.

just as a note, in another discussion the concept of per-seat a11y features came up, this could be implemented in libinput as a per-seat feature.
Comment 3 Peter Hutterer 2015-04-22 03:50:51 UTC 
closing this buts. This won't be implemented in libinput, see the above comments.
Comment 4 Bastien Nocera 2015-04-22 09:49:49 UTC 
See GNOME bug:
https://bugzilla.gnome.org/show_bug.cgi?id=748286

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.