Buttons on-screen are not functional with mouse input, yet are functional with touch screen input



Tech Evangelism
2 years ago
4 months ago


(Reporter: Grover, Unassigned)


Firefox 51
Windows 10

Firefox Tracking Flags

(firefox51 affected)


(Whiteboard: [needscontact])



2 years ago

Touch Enabled Device Windows: Device Manager > Human Interface Devices > HID-compliant touch screen (Enable)
Multiprocess Windows (Enabled)
Asynchronous Pan/Zoom (wheel input enabled; touch input enabled)
Mouse & Keyboard
Firefox Nightly 32-bit
javascript.options.asyncstack; false
browser.tabs.remote.force-enable; true
browser.tabs.remote.autostart.2; true & about:support Multiprocess Windows 1/1 (Enabled by user)
layers.async-pan-zoom.enabled; true & about:support Asynchronous Pan/Zoom wheel input enabled; touch input enabled

[Steps to Reproduce]
1. Navigate to http://www.nasaprospect.com/ 
2. Use mouse to tap the up and down buttons on the webpage itself (not on the scroll bar).

[Expected Results]
The up and down buttons are functional with mouse input.

[Actual Results]
The up and down buttons when pressed with mouse input do not function and nothing happens.

This appears regardless of whether e10s is enabled or not.
This is a website bug. In http://nasaprospect.com/js/lib/hammer.custom.js they have this code:

p=Modernizr?Modernizr.touch:"ontouchstart"in window,Q=p?"touchstart":"mousedown"

and generally seem to be assuming that if touch is supported, then mouse is not. The same issue appears in Chrome (clicking on the up/down buttons with mouse doesn't work).
Component: Panning and Zooming → Desktop
Product: Core → Tech Evangelism
Version: 51 Branch → Firefox 51
Looks like the site should handle both click and touch input, not either-or. 

Setting to needscontact.
Whiteboard: [needscontact]

Comment 3

2 years ago
I don't see this issue on Internet Explorer. On Surface Pro, with latest build of nightly(20160907030427)up and down buttons are not working either with touch or mouse click.
Yeah IE/Edge doesn't support touch events, so it will work fine for them.
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.