We had to disable XI2/multidevice support in bug 1170342 due to focus and scrolling related issues. We should monitor these issues to see if it would be possible to re-enable XI2 in the future.
Please add option to reenable via about:config or something - I'm really got used to it...
(In reply to Kuba Niewiarowski from comment #1) > Please add option to reenable via about:config or something - I'm really got > used to it... Just set MOZ_USE_XINPUT2=1 env variable which enables it in Firefox.
(In reply to Martin Stránský from comment #2) > Just set MOZ_USE_XINPUT2=1 env variable which enables it in Firefox. Not working... I'm using Aurora builds from https://launchpad.net/~ubuntu-mozilla-daily/+archive/ubuntu/firefox-aurora
MOZ_USE_XINPUT2=1 is in Nightly (bug 1207973) but not yet in Aurora.
Severity: normal → enhancement
Priority: -- → P3
Using "MOZ_USE_XINPUT2=1" &e10s worked for me (https://bugzilla.mozilla.org/show_bug.cgi?id=1268599#c10), but not very smooth (scrolling, afterwords opening the menu item, then trying to scroll results in an un-scrollable page). Fedora already compiles FF with "MOZ_USE_XINPUT2=1", which is very smooth on my tablet. However, it would be interesting how this is handled by Firefox for Android, which clearly needs touch support and XINPUT2.
I think we can enable the XInput2 for recent Gtk+ versions (say Gtk+ >= 3.20) as the related Gtk+ focus bugs was fixed but for XInput2 only. Also Fedora enables XInput2 by default and we don't have any user complains.
Severity: enhancement → normal
Priority: P3 → P2
Before the switch we need to address Bug 1182700. Bug 1170342, Bug 1196777 should be fixed for reasonable recent systems.
For Bug 1182700 looks like gnome folks gave up (https://bugzilla.gnome.org/show_bug.cgi?id=750994#c8) and recommend to use Wayland. I wonder how big complication is it and if benefits from enabled xinput2 outweigh it, especially when the focus bugs should be fixed on recent systems.
Gnome issue 750994 has been migrated to their Gitlab instance: https://gitlab.gnome.org/GNOME/gtk/issues/558
You need to log in before you can comment on or make changes to this bug.