Closed Bug 847392 Opened 11 years ago Closed 10 years ago

Remove ~300ms delay on tap more agressively for fixed viewports

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 941995

People

(Reporter: jhugman, Unassigned)

Details

For fixed viewports, for example: 

<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no" />

Double taps are taking a long time to reach javascript as a double tap. 
Similarly, taps are taking a long time to be ignored as a not-scroll/fling event. 

(for longtime, read ~300ms)

This mirrors the bug in Chromium: https://code.google.com/p/chromium/issues/detail?id=169642
Could you attach a test case that demonstrates how you are measuring the delay? I don't think we should really be having any significant delay between the second tap in the double-tap and the event being delivered to JS but I'd need to know how you're measuring it to check the relevant code paths.
But | user-scalable=no | should disable the 300ms delay. There is a movement to also disable the delay for simply | width=device-width | which is happening in bug 941995.
Status: NEW → RESOLVED
Closed: 10 years ago
No longer depends on: 941995
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.