Closed
Bug 558915
Opened 15 years ago
Closed 15 years ago
Scroll wheel zooming breaks after pan
Categories
(Firefox for Android Graveyard :: Panning/Zooming, defect)
Firefox for Android Graveyard
Panning/Zooming
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mbrubeck, Assigned: mbrubeck)
Details
Attachments
(3 files, 1 obsolete file)
1.17 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
1.25 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
5.26 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Steps to reproduce (requires a mouse with a scroll wheel):
1. Open any web page.
2. Drag to pan the web page.
3. Use the scroll wheel to zoom the page.
Expected: Page zooms.
Actual: Nothing happens.
Assignee | ||
Comment 1•15 years ago
|
||
"this" in the timeout callback is set to the global object, so writes to a global variable "pendingEvent" instead of the intended instance variable.
Attachment #438588 -
Flags: review?(mark.finkle)
Assignee | ||
Updated•15 years ago
|
Attachment #438588 -
Attachment is patch: true
Attachment #438588 -
Attachment mime type: application/octet-stream → text/plain
Assignee | ||
Comment 2•15 years ago
|
||
ungrab is never called with its first argument null, so this is dead code. I see no no need calling it with null in the future either. (If the InputHandler was not grabbed, then there should be no ignored events to restore.)
Attachment #438590 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 3•15 years ago
|
||
http://hg.mozilla.org/mobile-browser/rev/6629e9516bb1 adds support for nested grab/ungrab calls, but requires one call to ungrab() for every call to grab().
MouseModule disobeys this since it calls grab many times (on mousedown *and* on each mousemove), but calls ungrab only once (on mouseup). This always leaves the InputHandler in a "grabbed" state and prevents calls to any other handler.
This patch prevents nested grabs in MouseModule.
Attachment #438592 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 4•15 years ago
|
||
6629e9516bb1 greatly complicated grab/ungrab by adding support for nested calls and event replay. Nine months later, we are still not using either of those features, so most of this code has never been used or tested. Maybe we should just remove it?
On the other hand, bug 558320 might actually use these features.
Updated•15 years ago
|
Attachment #438588 -
Flags: review?(mark.finkle) → review+
Updated•15 years ago
|
Attachment #438590 -
Flags: review?(mark.finkle) → review+
Comment 5•15 years ago
|
||
Comment on attachment 438594 [details] [diff] [review]
patch 3 (alternate): remove nested grab code
Lets try to remove this cruft
Attachment #438594 -
Flags: review+
Comment 6•15 years ago
|
||
pushed:
http://hg.mozilla.org/mobile-browser/rev/24feb65ec1f3
http://hg.mozilla.org/mobile-browser/rev/eee1ca00a56a
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Attachment #438592 -
Attachment is obsolete: true
Attachment #438592 -
Flags: review?(mark.finkle)
Comment 7•15 years ago
|
||
Ungrabbing with replay events can actually be useful. I'm using it in my experimental gesture support. The "too much grabbing" issue needs to be fixed in MouseModule (that probably only should grab when panning) but the nested feature was actually needed.
Comment 8•15 years ago
|
||
verified FIXED on build:
Mozilla/5.0 (Macintosh; U; Intel Mac OSX 10.5; en-US; rv:1.9.2.4) Gecko/20100413 Namoroka/3.6.4pre Fennec/1.1a2pre
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•