Closed
Bug 96762
Opened 23 years ago
Closed 23 years ago
personal toolbars disappear and can't be used after shutting down
Categories
(Core :: XUL, defect)
Tracking
()
People
(Reporter: tever, Assigned: bugs)
References
Details
Overview Description: Can not access the personal toolbars after minimizing them and shutting down the program. On re-starting the program, they will be gone and there is no way to get them back. Steps to Reproduce: 1.) close the sidebar using View | My Sidebar 2.) minimize the toolbars by clicking the 3 small arrows in the far upper left 3.) exit the program 4.) restart Build Date & Platform Bug Found: Win NT4 2001082303 Additional Builds and Platforms Tested On: fails on mac os 9 Additional Information: had to delete localstore.rdf to get around this
Comment 3•23 years ago
|
||
JS error in console: Error: aToolbar.findNodeByAttribute is not a function Source File: chrome://global/content/bindings/toolbar.xml#toolbox.createCollapsedGrippy() Line: 3
editing localstore.rdf will do: Replace all Toolbar statments to end with: moz-collapsed="false" /> (instead of ="true" />) This is very similar to bug 95000 - hyatt fixed that one.
Similar: bug 96224, where reporter observes that handles return visibly in new windows, but are absent in the first window after startup.
Comment 7•23 years ago
|
||
Actually, this only seems to apply to Modern, not Classic. And, yes, opening a new browser window will produce the missing toolbars.
Comment 9•23 years ago
|
||
This is a dup of bug 73064, which was fixed right before 0.9.2 went out but then backed out due to a nasty UI regression. It looks like a different patch has since been checked into the branch... [note both bugs are modern only, comments from jag re: findNodeByAttribute, dups like bug 88071 marked against 73064, etc] *** This bug has been marked as a duplicate of 73064 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•