Closed
Bug 1038002
Opened 10 years ago
Closed 10 years ago
Holding your finger down and then trying to pan gets stuck until the next touch
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1009733
People
(Reporter: drs, Unassigned)
References
Details
Attachments
(1 file)
153 bytes,
text/html
|
Details |
STR: 1) Open attached test case. 2) Place finger down for a few hundred ms. 3) Try panning. Expected: Document pans. Actual: Document is locked in place. I think this behavior makes sense if the contextmenu event is preventDefaulted, but otherwise the document should always be pannable. There are additional side-effects to this behavior. For example, the box in the test case goes red when active, but doesn't get set inactive until the user places a finger down again. This is causing problems in Gaia, such as in bug 1033937.
Comment 1•10 years ago
|
||
Just to clarify, based on what you showed me in person: "getting stuck" doesn't mean that *subsequent* touch blocks are ignored, only that *this* touch block (which began with the long tap) doesn't result in panning, right?
Reporter | ||
Comment 2•10 years ago
|
||
(In reply to Botond Ballo [:botond] from comment #1) > Just to clarify, based on what you showed me in person: "getting stuck" > doesn't mean that *subsequent* touch blocks are ignored, only that *this* > touch block (which began with the long tap) doesn't result in panning, right? Yes.
Summary: Holding your finger down and then trying to pan gets us stuck → Holding your finger down and then trying to pan gets stuck until the next touch
Comment 3•10 years ago
|
||
I believe my patch on bug 1009733 fixes this. When I tested locally it also fixed the :active highlight issue, but marking this as blocking bug 1014322 anyway to make sure we end up being consistent with other CSS :active behaviour.
Comment 4•10 years ago
|
||
Reopen if you still see this
Status: NEW → RESOLVED
Closed: 10 years ago
No longer depends on: apz-state
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•