Closed Bug 626055 Opened 15 years ago Closed 15 years ago

Customized toolbar in older beta releases puts Firefox button on top right

Categories

(Firefox :: Menus, defect)

All
Linux
defect
Not set
normal

Tracking

()

VERIFIED WONTFIX

People

(Reporter: glandium, Unassigned)

References

Details

I've been using the betas for a while and when I enabled the Firefox button recently, it ended up being on the top right of the UI. Which is not the default, as a fresh profile makes it appear on the top left, and an annoyance because the button is not moveable. I could reproduce the issue with the following scenario: - Start an older beta (tried 4.0b1) - Reorder the buttons on the right of the tabbar - Upgrade to 4.0b9 - Enable Firefox button (disable menu bar) -> Firefox button is on top right. I think it happened on my old profile because I moved the panorama button a while ago.
Component: General → Menus
QA Contact: general → menus
Can you please give exact steps of which buttons you have reordered? That would help a lot. Thanks.
See bug 585370 comment 326, affects beta users only.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Thanks Dao. Good to know.
Status: RESOLVED → VERIFIED
Summary: Firefox button on top right under some circumstances → Customized toolbar in older beta releases puts Firefox button on top right
(In reply to comment #1) > Can you please give exact steps of which buttons you have reordered? That > would help a lot. Thanks. Whichever, having a set previously defined in the localstore is enough. (In reply to comment #2) > See bug 585370 comment 326, affects beta users only. Yeah, fortunately, the tabbar didn't have a set before 4.0.
For those who'd find this bug, and for whom "Restore Default Set" would mean having to customize all toolbars again: you can edit the localstore.rdf file in your user profile, search the RDF:Description with RDF:about="chrome://browser/content/browser.xul#TabsToolbar" and change the currentset so that it starts with appmenu-toolbar-button.
You need to log in before you can comment on or make changes to this bug.