Closed
Bug 222854
Opened 21 years ago
Closed 19 years ago
Menu selections, File Bookmark and Manager Bookmark produce xml parsing errors.
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: rperry4, Assigned: p_ch)
Details
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4.1) Gecko/20031018 Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4.1) Gecko/20031018 Click File Bookmark ==> XML Parsing Error: Syntax error Location: chrome://communicator/content/bookmarks/addBookmark.xul Line Number 1, Column 1 Click Manager Bookmark ==> XML Parsing Error: not well formed Location: chrome://communicator/content/bookmarksManager.xul Line Number 1, Column 11 Reproducible: Always Steps to Reproduce: 1.Click on menu items. 2. 3. Actual Results: See Details above. Using "Modern" theme.
Reporter | ||
Comment 1•21 years ago
|
||
OS FreeBSD 4.7 RELEASE Errors occur using Modern or Classic themes.
Comment 2•21 years ago
|
||
I got this bug a while back while testing Mozilla 1.5b on Solaris. It was caused by some old chrome settings which were there since Netscape 7.0 for Solaris. I was able to fix it by closing the users Mozilla and removing the files 'XUL.mfasl' and 'localstore.rdf' from their profile. I'm not sure whether you have exactly the same problem as i had but they look far too similar.
Comment 3•21 years ago
|
||
I'm getting the same error, but I'v getting it when I use a "file://" URL to look at a directory, double click on a image to view it, and then use the back button. I'm using the very latest nightly build on an x86 Linux machine.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 4•19 years ago
|
||
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/
Comment 5•19 years ago
|
||
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.
Description
•