Closed Bug 740005 Opened 12 years ago Closed 12 years ago

Sometimes, tapping on links or buttons don't work or causes tapping on the wrong spot

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(blocking-fennec1.0 beta+)

RESOLVED DUPLICATE of bug 732016
Tracking Status
blocking-fennec1.0 --- beta+

People

(Reporter: martijn.martijn, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [fixed by a blocker])

Steps to reproduce:
- Have these 2 tabs open:
1:: http://people.mozilla.com/~mwargers/tests/forms/autocomplete_forms/autofocus_input.html
2:: http://people.mozilla.com/~mwargers/tests/tapping/buttons.htm

- On the 1st tab, focus the text input
- Switch tabs, go to the 2nd tab
- Try to tap on the buttons

Expected result:
- Buttons can be tapped upon, you get tap feedback

Actual result:
- Buttons can't be tapped upon, you don't get any tap feedback

Tested on the Samsung Galaxy Nexus, Android 4.0.2.
I've seen this frequently on the about:firefox page, when tapping the "Check for Updates" button, Galaxy Nexus.   It would sometimes trigger the FAQ link directly below it, instead of the actual updates button.

i can not reproduce this 100%.
blocking-fennec1.0: --- → ?
I can reproduce this using the same STR in comment #0 -- Galaxy Nexus (Android 4.0.2) and Galaxy SII (Android 2.3.4) w/ Nightly (03/28).
I don't know if this is the same as bug 735539, it might be good to know if there is a specific regression range here.
(In reply to Aaron Train [:aaronmt] from comment #2)
> I can reproduce this using the same STR in comment #0 -- Galaxy Nexus
> (Android 4.0.2) and Galaxy SII (Android 2.3.4) w/ Nightly (03/28).

same here, reproduced for me.
blocking-fennec1.0: ? → ---
blocking-fennec1.0: --- → ?
blocking-fennec1.0: ? → beta+
Is this a dupe of bug 735539?
Whiteboard: [needs assignee]
I've seen this on a bunch of sites, the offset of where you tap (e.g, a link) is far out and beyond from where your finger makes contact on the device.
I disabled frameLoader.clampScrollPosition as described in https://bugzilla.mozilla.org/show_bug.cgi?id=736008#c7, and the problem went away.
Depends on: 732016
So this bug will be fixed by bug 732016. I feel like duping it.
Whiteboard: [needs assignee] → [fixed by a blocker]
noming so we can dupe, or we need to assign it.
blocking-fennec1.0: beta+ → ?
Status: NEW → RESOLVED
blocking-fennec1.0: ? → beta+
Closed: 12 years ago
Resolution: --- → DUPLICATE
Another testcase here: http://people.mozilla.org/~mwargers/tests/tapping/onclickscrollby2timestap.htm
Probably the same issu.
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.