Closed Bug 407916 Opened 17 years ago Closed 17 years ago

Identity Dropdown Location Screwed Up After Location Bar Customization

Categories

(Firefox :: Address Bar, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

VERIFIED DUPLICATE of bug 403720

People

(Reporter: brad, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1 After customizing the toolbars, the identity dropdown box doesn't show up in the right X, Y location. Reproducible: Always Steps to Reproduce: 1. Right click menu bar, click customize. 2. Remove Location bar from your toolbars. 3. Add Location bar to your toolbars. 4. Hit Done. Actual Results: Now, whenever the identity dropdown is selected, the identity dropdown is either above and off the screen, with a small white portion of the dropdown shown in the top left corner; or it is off the bottom of the window if your window is not maximized. Expected Results: The identity dropdown should be right below the location bar like usual. Just in case it has to do with my resolution/windowing settings, I have the window maximized on a 1024x1280 (portrait orientation) resolution monitor. Closing the window and reopening it resets the position with the new configuration settings.
Whiteboard: [DUPEME]
Ria, were you thinking of bug 398346? Brad, does this problem still occur using a recent nightly of Firefox? I can't reproduce using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2pre) Gecko/2007121108 Minefield/3.0b2pre
The most recent nightly has this bug fixed. I guess I learned my lesson. Sorry for wasting your time :/
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
(In reply to comment #1) > Ria, were you thinking of bug 398346? > I don't think so. I think this is basically the same as bug 403720.
Resolution: FIXED → DUPLICATE
Whiteboard: [DUPEME]
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.