| Summary: | Provide a user-accessible method to enable/disable middle-click functionality | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | Nate Graham <nate> |
| Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | nate, peter.hutterer |
| Version: | 1.5.0 | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Nate Graham
2016-11-21 16:03:24 UTC
if you enable middle button emulation on the touchpad while in 'area' mode the middle button area goes away and you're left with only left/right buttons (but obviously you can still middle click by clicking both). I know you're not responsible for graphical front-ends to libinput, but do you know how I would do that? On Fedora 25 + GNOME 3.22, I haven't found any kind of way to turn off middle-clicking, either via a GUI interface or documentation for a CLI interface. I've turned off the "middle-click paste" option in GNOME Tweak Tool, but that didn't seem to turn off the middle-mouse button functionality itself. the middle-click paste thing would be just that - middle click to paste the content of the clipboard (google has more if you're interested) I can't find anything in gsettings that looks like it enables middle button emulation and nothing in the mutter sources either. So for GNOME on Wayland it looks like you're out of luck, GNOME on X you could set it with an xorg.conf snippet or with xinput at runtime. All right, thanks. I've filed a bug on GNOME to expose the setting: https://bugzilla.gnome.org/show_bug.cgi?id=774873 Another acceptable resolution would be to improve Clickfinger behavior, where it's much harder to accidentally trigger a middle click: https://bugs.freedesktop.org/show_bug.cgi?id=98799 https://bugs.freedesktop.org/show_bug.cgi?id=98800 https://bugs.freedesktop.org/show_bug.cgi?id=98801 |
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.