Open Bug 592912 Opened 15 years ago Updated 3 years ago

Trunk nightly doesn't remember display changes between sessions

Categories

(Firefox :: Toolbars and Customization, defect)

defect

Tracking

()

People

(Reporter: gaby2300, Unassigned)

Details

(Whiteboard: [4b5])

User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b6pre) Gecko/20100901 Firefox/4.0b6pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b6pre) Gecko/20100901 Firefox/4.0b6pre Since Tab Candy landed in trunk I opened the browser and its button showed to the right of the bookmarks button. I dragged the Home, the Bookmarks and the Stop buttons to the Customize Toolbar. Whenever I started or restarted the browser it opened the same way. It worked fine till some updates ago. Since then every time I start or restart the browser I have to drag the Tab Candy button from the Customize Toolbar because it does not show, and perform the above changes too. Reproducible: Always Steps to Reproduce: 1. Start a trunk browser. 2. The Tab Candy button does not show. 3. Open the Customize Toolbar. 4. Drag the Tab Candy button from it to its usual place. 5. Drag the Home, the Bookmarks and the Stop buttons to the Customize Toolbar. 6. Restart the browser. Actual Results: Every time I start or restart the browser I have to drag the Tab Candy button from the Customize Toolbar again because it does not show, and perform the above changes again too. Expected Results: The browser should remember the changes between sessions.
Whiteboard: [4b5]
I see this too on OSX. It was working for a while but stopped pretty recently. I tried deleting my localstore.rdf and the problem still persisted. localstore.rdf isn't updated with the right stuff when I quit, so we're either not purging that or we're hitting an error somewhere.
Status: UNCONFIRMED → NEW
Component: Session Restore → Toolbars
Ever confirmed: true
OS: Windows 7 → All
QA Contact: session.restore → toolbars
Hardware: x86 → All
Version: unspecified → Trunk
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.