Last Comment Bug 564021 - Javascript preferences should have an option to disable binding to scroll events
: Javascript preferences should have an option to disable binding to scroll events
Status: UNCONFIRMED
:
Product: Core
Classification: Components
Component: Event Handling (show other bugs)
: unspecified
: All All
: -- enhancement with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
http://www.thepittsburghchannel.com/n...
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-05 13:20 PDT by Ben Ford
Modified: 2012-11-22 18:09 PST (History)
1 user (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Ben Ford 2010-05-05 13:20:23 PDT
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_3; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.29 Safari/533.4
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6

There are a few valid reasons to bind to scroll events, such as zooming in a map.  However, almost every time this happens, it is by ACCIDENT and is NOT what I wanted to do.  I would gladly lose the ability to zoom a map, or scroll a div with sexed up widgets with the wheel if it meant that I could actually scroll the page without having to be ridiculously careful about where I put the mouse cursor.

A better solution perhaps would be to implement some sort of timeout.  Only send the scroll events to a div after it has had focus for greater than X ms, or when the page is not currently scrolling.

Reproducible: Always

Steps to Reproduce:
1.  Load the example page
2.  Scroll the page
3.  Curse like hell when the page stops scrolling and the map zooms out to galaxy level because the cursor happened to be over the embedded map
Actual Results:  
The page stopped scrolling and the map zoomed out to galaxy level because the cursor happened to be over the embedded map

Expected Results:  
The page should have continued scrolling.

Note You need to log in before you can comment on or make changes to this bug.