Failure to recognize touch inputs galliumos
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
People
(Reporter: Senhara, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Run GalliumOS 3.0 on a laptop with touchscreen support (for specifics, I'm working on an HP chromebook that no longer runs ChromeOS)
Open Firefox
Attempt to use touch controls
Actual results:
Firefox treats the finger input as a touch or drag
Expected results:
Firefox should treat the input as a scroll
Comment 1•5 years ago
|
||
Does setting the environment variable MOZ_USE_XINPUT2=1 help?
I forgot the account that I submitted this ticket from has an email that no longer exists attached to it. I'm not sure how to edit environment variables, where would I do that? Editing the profile under ~/.mozilla does nothing.
Comment 3•5 years ago
|
||
The priority flag is not set for this bug.
:botond, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 4•5 years ago
•
|
||
(In reply to jtjamrog from comment #2)
I forgot the account that I submitted this ticket from has an email that no longer exists attached to it. I'm not sure how to edit environment variables, where would I do that? Editing the profile under ~/.mozilla does nothing.
In a terminal, with Firefox not already running, try running:
MOZ_USE_XINPUT2=1 firefox
Updated•5 years ago
|
This has fixed it, I would suggest adding an option to forcibly enable touch screen support, but idk how that works.
(In reply to jtjamrog from comment #5)
This has fixed it, I would suggest adding an option to forcibly enable touch screen support, but idk how that works.
In settings I mean, I'm too tired to be typing right now, sorry
Comment 7•5 years ago
|
||
(In reply to jtjamrog from comment #5)
This has fixed it
Thanks, that makes this a duplicate of bug 1207700, which tracks enabling XInput2 by default.
Comment 8•5 years ago
|
||
(In reply to jtjamrog from comment #6)
(In reply to jtjamrog from comment #5)
This has fixed it, I would suggest adding an option to forcibly enable touch screen support, but idk how that works.
In settings I mean, I'm too tired to be typing right now, sorry
We could add a flag to about:config easily enough; I filed bug 1601850 for this.
Description
•