Closed Bug 769566 Opened 12 years ago Closed 12 years ago

Form autocomplete suggestions pops up for a fraction of a second then disappears

Categories

(Firefox for Android Graveyard :: General, defect)

14 Branch
ARM
Android
defect
Not set
normal

Tracking

(firefox14- fixed, blocking-fennec1.0 .N+)

RESOLVED DUPLICATE of bug 752759
Tracking Status
firefox14 - fixed
blocking-fennec1.0 --- .N+

People

(Reporter: csuciu, Assigned: Margaret)

References

Details

(Keywords: regression, Whiteboard: [Firefox beta 14.0b10])

Attachments

(1 file)

Firefox Beta 14.0b10 Build 2
Samsung Galaxy SII (Android 2.3.4)

Steps:
1. Go to Gmail login page (Make sure you have some form fields saved before)
2. Tap on "Username" field

Expected:
Form autocomplete suggestions should pop up and stay there until it is dismissed by user

Actual:
Form autocomplete suggestions pops up for a fraction of a second then disappears

Note: Not reproducible on Nightly 16.0a1 (2012-06-28)
Adding qawanted to get a regression window here, and preemptively tracking since this may be a regression since FN14.0 release.
Assignee: nobody → margaret.leibovic
blocking-fennec1.0: --- → ?
The issue _is not_ reproducible on Firefox Mobile 14b8 build 4 but _is_ reproducible on Firefox Mobile 14b10 build 1 on Samsung Google Nexus running Android 4.0.2. Issue is not reproducible on the latest Aurora 15.0a2 2012-07-03.
blocking-fennec1.0: ? → .N+
Keywords: regression
I'm making a beta build to track this down.

For the record, I can't reproduce this on Aurora or on my build of mozilla-central, so it seems like some bad uplift interaction (maybe missing something?).
I used tinderbox builds to bisect, and I found the bad changset is:
http://hg.mozilla.org/releases/mozilla-beta/rev/7945471fc07f

Matt or Kats, any idea why this might cause a problem on beta, but not on central or aurora? Maybe we need to uplift bug 752759. I'm still waiting on my beta build to finish, but I can try out that idea when it finishes.
(In reply to Margaret Leibovic [:margaret] from comment #4)
> Matt or Kats, any idea why this might cause a problem on beta, but not on
> central or aurora?

Nothing obvious I can think of.  Bug 756474 touched that code, but it's only on central (not aurora)...
I just applied the patch in bug 752759, and that appears to fix the problem. There's probably just some weird mix of unexpected logic due to only some patches being uplifted. That patch is pretty low-risk, so I'll nom that.
I just pushed the patch for bug 752759 to beta, so we can check the tinderbox build to confirm that this bug is fixed by that uplift.
Works for me with the latest tinderbox build. Marking as a dupe since the patch for bug 752759 fixed this.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
marking status firefox 14 fixed since the duped bug was landed on beta
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: