URL autocomplete shows double entries

RESOLVED FIXED

Status

()

Core
XBL
--
major
RESOLVED FIXED
10 years ago
9 years ago

People

(Reporter: Andrew Schultz, Assigned: bz)

Tracking

({regression, verified1.8.1.12})

1.8 Branch
x86
Linux
regression, verified1.8.1.12
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.8.1.12 +
blocking1.8.0.next -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
Current SeaMonkey from the 1.8 branch shows double entries for the URL autocomplete dropdown.  This regressed due to bug 398006.  Trunk does not have this problem.

1. Visit www.mozilla.org
2. Type "m" in the URL bar.

result:
"http://www.mozilla.org/ - Mozilla.org - H... http://www.mozilla.org - Mozilla.org - H..."

should be
"http://www.mozilla.org/ - Mozilla.org - H..."
Flags: blocking1.8.1.12?
Doesn't happen with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12pre) Gecko/20080102 BonEcho/2.0.0.12pre
Looks like I can make the bug go away by simply dropping on the floor ctors that would run from PostCreate when we're in frame construction (e.g. ctors triggered by fields) instead of adding them to the attached queue.  At the same time, it doesn't look like any ctor runs twice here...  So I'm not sure why the doubling happens.
Blocks: 410666
Blocks: 398006
Flags: blocking1.8.1.12? → blocking1.8.1.12+
(Reporter)

Updated

10 years ago
Duplicate of this bug: 412482
backout of bug 398006 approved for 1.8.1.12, a=dveditz for release-drivers
I backed out the patch for bug 398006.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Keywords: fixed1.8.1.12
Resolution: --- → FIXED
Not seeing this with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12pre) Gecko/20080128 SeaMonkey/1.1.8pre; verified.

Replacing fixed1.8.1.12 keyword with verified1.8.1.12.
Keywords: fixed1.8.1.12 → verified1.8.1.12

Comment 8

9 years ago
needs to be verified for 1.8.0.15 after bug #398006 has landed.
Flags: blocking1.8.0.15+

Comment 9

9 years ago
bug #398006 won't land on branches.
Flags: blocking1.8.0.15+ → blocking1.8.0.15-
You need to log in before you can comment on or make changes to this bug.