Closed
Bug 89451
Opened 24 years ago
Closed 24 years ago
Default sidebar tabs not included under "Available Tabs" in customize sidebar menu
Categories
(SeaMonkey :: Sidebar, defect)
Tracking
(Not tracked)
People
(Reporter: vanbalen, Assigned: matt)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2+) Gecko/20010703
BuildID: 2001070309
I tried to step someone through the workaround for the "no bookmarks in sidebar"
bug (bug 71685) and, upon trying to add the bookmarks tab back into the sidebar,
I realized that it was now _permanently_ gone!
I looked at everything under the "available tabs" menu and the "find more tabs"
thing but none of the default tabs are in there and so they cannot be added back
once they're removed.
Saw this on 0.9.2 and confirmed again on my own 2001070309 nightly build.
Reproducible: Always
Steps to Reproduce:
1. Under sidebar, choose Tabs->Customize Sidebar...
2. Under "Tabs in my sidebar" click on one of the default tabs (try bookmarks)
and then click on the "remove" button.
3. Now decide that you don't want to remove that tab after all and attempt to
add it back.
4. If you are successful in doing this, feel free to resolve this bug... after
letting me know how the heck you did it.
Actual Results: My bookmarks tab now appears to be gone from my sidebar forever...
Expected Results: Mozilla should assume that I'll do something stupid like
remove my bookmarks tab and then want to add it back... especially with
workarounds like the one for bug 71685
Workaround for re-adding deleted default tabs is to rename
$HOME/.mozilla/<profile>/<whateverelse>/panels.rdf and restart mozilla. The
default panels.rdf should be recreated upon restart.
Dave, sounds like this is a DUP of 87002? If so please mark this
RESOLVED-DUPLICATE.
thanks.
Yep... looked for that but didn't find it.
Thanks.
*** This bug has been marked as a duplicate of 87002 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•