Can't scroll with mouse wheel when mouse is above input type="number" and type="range"




Layout: Form Controls
a year ago
3 months ago


(Reporter: arni2033, Unassigned)



Firefox Tracking Flags

(Not tracked)


(Whiteboard: [browser-overrides-user-actions])



a year ago
>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
1. Open url   data:text/html,<input autofocus type='number' value=0 min=0><style>body{height:10000px}
2. Hover mouse over <input>   (happens accidentally)
3. Rotate mouse wheel down once

AR:  No visible action
ER:  The page should scroll down


a year ago
No longer blocks: 1277113


a year ago
Component: Untriaged → Layout: Form Controls
Product: Firefox → Core
Works as expected on mac with two finger touchpad scrolling and one finger magic mouse scrolling at least.

Comment 2

a year ago
In this bug reporter meant that after bug 949989, bug 1261674, bug 1261673, bug 1283353 etc. it's now possible to encounter a "trap" on web page that would prevent you from scrolling w/ wheel.

Reference of good behavior: there's a long-standing bug 1234958 in Firefox (read its summary). It was decided to implement a work-around (about-config pref) for that bug, to allow users live w/o unwanted "traps" on web pages, see bug 1250050.

Reporter also referred to another trap - bug 1199861. There're no such traps on Google Chrome browser.
If you think that the reported trap should be unavoidable for users, please close the bug.

Comment 3

3 months ago
A number of users sees the reported behaviour on <input type="number"> as undesireable for desktop browsing.

See details on which also discusses workarounds.

We also got a report about usability issues from a customer for whom we have created a web application (for reference (Scrollwheel may surprisingly change number input fields (on Firefox)).

As already pointed out by @castiel743: Chromium behaves better here.
I'd expect Firefox on the desktop to keep browsing if the mouse pointer is over an input field and leave the value of input type="number" as it is.

(This comments adds more evidence about the user expectations and a link to possible workarounds.)
You need to log in before you can comment on or make changes to this bug.