Closed Bug 191865 Opened 22 years ago Closed 19 years ago

panels.rdf sequence processed incorrectly by Sidebar

Categories

(SeaMonkey :: Sidebar, defect)

x86
Linux
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: Martijn.Ras, Assigned: shliang)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 The Sidebar's Tabs pull-down-menu correctly processes the sequence in panels.rdf correctly. The Sidebar's Tabs themselves, on the other hand however, are INCORRECTLY sequenced! Reproducible: Always Steps to Reproduce: 1. Make the Sidebar visible (Press F9) 2. Close all Mozilla windows. 3. Make a backup of your panels.rdf (cp panels.rdf panels.rdf.BACKUP) 4. Create a new panels.rdf file with the following content: <?xml version="1.0"?> <RDF:RDF xmlns:NC="http://home.netscape.com/NC-rdf#" xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <RDF:Description about="urn:sidebar:current-panel-list" NC:version="0.1"> <NC:panel-list resource="rdf:#$XJNOq3"/> </RDF:Description> <RDF:Seq about="rdf:#$XJNOq3"> <RDF:li resource="urn:sidebar:panel:bookmarks"/> <RDF:li resource="urn:sidebar:panel:history"/> </RDF:Seq> <RDF:Description about="urn:sidebar:panel:history" NC:title="History" NC:content="chrome://communicator/content/history/history-panel.xul" /> <RDF:Description about="urn:sidebar:panel:bookmarks" NC:title="Bookmarks" NC:content="chrome://communicator/content/bookmarks/bm-panel.xul" /> <RDF:Description about="" NC:exclude="navigator:browser" /> </RDF:RDF> 5. Open a new Mozilla Navigator window. Actual Results: The Sidebar's Tabs pull-down-menu shows: Customize Sidebar Sidebar Directory ----------------- Bookmarks History The Tabs themselves on the other hand are shown INCORRECTLY sequenced: History Bookmarks Expected Results: The Tabs themselves should have been shown sequenced like this: Bookmarks History To make everything appear as expected, you've to give the tabs themselves in the same order as the sequence: <?xml version="1.0"?> <RDF:RDF xmlns:NC="http://home.netscape.com/NC-rdf#" xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <RDF:Description about="urn:sidebar:current-panel-list" NC:version="0.1"> <NC:panel-list resource="rdf:#$XJNOq3"/> </RDF:Description> <RDF:Seq about="rdf:#$XJNOq3"> <RDF:li resource="urn:sidebar:panel:bookmarks"/> <RDF:li resource="urn:sidebar:panel:history"/> </RDF:Seq> <RDF:Description about="urn:sidebar:panel:bookmarks" NC:title="Bookmarks" NC:content="chrome://communicator/content/bookmarks/bm-panel.xul" /> <RDF:Description about="urn:sidebar:panel:history" NC:title="History" NC:content="chrome://communicator/content/history/history-panel.xul" /> <RDF:Description about="" NC:exclude="navigator:browser" /> </RDF:RDF>
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.