Closed Bug 753819 Opened 13 years ago Closed 11 years ago

Lag in links being clickable after Google Search

Categories

(Firefox for Android Graveyard :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-fennec1.0 soft)

RESOLVED INCOMPLETE
Tracking Status
blocking-fennec1.0 --- soft

People

(Reporter: ccollins, Unassigned)

References

Details

(Whiteboard: [Engagement][User Engagement])

Web page or screen you were on when you saw the issue: This has happened to me twice now. First search was with the term "Jacksonville Jaguars" and the second search was "Caesars Palace Las Vegas". This doesn't happen with every search. But two searches in 10 minutes had the experience, so I thought I'd report it. Steps to reproduce: 1. search for "Caesars Palace Las Vegas" 2. Search results loaded instantly (yay!) 3. However, I couldn't tap to open any of the links for a good 10-15 seconds. 4. Then, I finally got a link to select, but it didn't open 5. THEN it opened. The whole process took about 15 seconds 6. The exact same experience happened when I searched for Jacksonville Jaguars 7. Perhaps the text is loading quickly, and the links are lagging behind? 8. On a Samsung Galaxy Nexus What you expected: Should be able to click on links as soon as the page loads Crash report ID (if applicable):
Noming for soft blocker. I think this should cover the class of errors where touch events get queued behind a bunch of other things (draw events, etc.).
blocking-fennec1.0: --- → ?
Assignee: nobody → bugmail.mozilla
blocking-fennec1.0: ? → soft
Unassigning from myself since I'm not actively working on this and other people might want to. I wasn't able to reproduce this although my hypothesis for the cause is in comment #1 (touch events get stuck behind other slow events in the native event queue in nsAppShell.cpp),
Assignee: bugmail.mozilla → nobody
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Resolution: WONTFIX → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.