Closed Bug 291038 Opened 20 years ago Closed 20 years ago

No support for onmousewheel or equivalent events

Categories

(Core :: DOM: Events, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 111647

People

(Reporter: support, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Mozilla does not provide any DOM event when the mouse-wheel is scrolled.
In Internet Explorer (6.0) a canceleable 'onmousewheel' event is fired, allowing
a handler to perform some custom action in response to the user scrolling the
mouse wheel, AND suppress page level scrolling normally instantiated by the
mouseWheel event.

This event (or an equivalent) should be fired when the scroll wheel is rotated
so the developer can write custom handling for the mouse-wheel within their web
application, such as scrolling, modifying selection, etc.

Note: This is not a duplicate of 189308 -
https://bugzilla.mozilla.org/show_bug.cgi?id=189308.  
That report is requesting that the onscroll event is fired when scrolling is
triggered from a mouse-wheel, rather than having an additional mouse-wheel event.  
This issue should be addressed in addition to that issue in order to make it
possible to respond to scroll wheel events without scrolling the page (or some
lower level element that responds to scroll wheel events such as an IFRAME).

Reproducible: Always

Steps to Reproduce:
1.Create any HTML page with <body onmousewheel='alert(1)'>
2.Load the page and scroll the mouse scroll wheel anywhere on the page.


Actual Results:  
The page will scroll but no onmousewheel event is generated - the handler
doesn't fire

Expected Results:  
The handler should fire and show the alert.
Assignee: firefox → events
Component: General → DOM: Events
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → Trunk
This is bug 111647, it was closed as WORKSFORME erroneously in my opinion. It
seems dependent on the mouse driver. Anyways, comments belong there, not here.

*** This bug has been marked as a duplicate of 111647 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.