Open
Bug 384683
Opened 18 years ago
Updated 2 years ago
autoscroll should reset if the pointer is outside the content
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
NEW
People
(Reporter: Peter6, Unassigned)
References
Details
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070615 Minefield/3.0a6pre ID:2007061522
repro:
Open a page that has scrollbars
middleclick to set autoscroll mode on
move the pointer outside the page (anywhere in chrome)
result:
the autoscroll image doesn't go away.
side effect, for any action in chrome (e.g. try to open bookmarks menu) you need 2 clicks, one to remove the autoscroll, two to do what you wanted in the fist place.
Comment 1•18 years ago
|
||
That's mostly expected behaviour. Only the "side effect" is a regression from bug 242621.
Blocks: 242621
Severity: major → normal
Updated•18 years ago
|
OS: Windows XP → All
Hardware: PC → All
I consider that pretty much by design... the cursor is tracked over chrome, so if you happen to middle-click at the very top of the content area you can still scroll up. This should be exactly what we've had in SeaMonkey for at least 2 releases.
After using old Firefox for a bit, that behavior is actually decent... I'll look at what it'd take to get it working.
Neil, I tried playing with captureRollupEvent, but couldn't get the event to go through. Could you help me here?
Comment 5•18 years ago
|
||
You called popupBoxObject.setConsumeRollupEvent with ROLLUP_NO_CONSUME just before opening the popup?
Yup:
this._autoScrollPopup.popupBoxObject.setConsumeRollupEvent(2);
this._autoScrollPopup.showPopup(document.documentElement,
event.screenX,
event.screenY,
"popup", null, null);
Maybe I'm misunderstanding what that does...
Comment 7•18 years ago
|
||
Looks like the flag only has any effect on Windows. But it isn't too hard to fix on other platforms. On Linux, the function nsWindow::check_for_rollup just has to return false if the flag was set after calling Rollup. On Mac, don't return early in nsChildView::mouseDown.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•