Closed
Bug 295499
Opened 20 years ago
Closed 20 years ago
XUL/XML Parsing error shown on startup
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 242436
People
(Reporter: mcow, Assigned: mscott)
Details
TB 1.0+0525, Win2K
On startup, the message pane is a light yellow window with this text:
XML Parsing Error: undefined entity
Location: jar:file:///C:/Moz/TB/chrome/toolkit.jar!/content/global/about.xhtml
Line Number 82, Column 1:<a id="mozlink" href="&releaseURL;">
&brandShortName; 1.0+</a>
No apparent side effects. The About dialog displays as expected when asked for.
FWIW, I don't have "Remember last selected message" checked, if that's not
already obvious.
PS: Last time I saw an error like this, I couldn't select the error text for
copying -- now I can! Very nice!| Reporter | ||
Comment 1•20 years ago
|
||
Also: no error in the JavaScript Console.
Flags: blocking-aviary1.1?
| Reporter | ||
Comment 2•20 years ago
|
||
Whoops -- I figured this out, and it's an older bug that was apparently quiescent for a while...? *** This bug has been marked as a duplicate of 242436 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.1?
Resolution: --- → DUPLICATE
Comment 3•20 years ago
|
||
Personally i think this bug here should be reopened, since it shows something went wrong with some checkin (since it only started to occour since today (again?)).
| Assignee | ||
Comment 4•20 years ago
|
||
Hmmm I just installed the windows 05/25 build this morning and it ran just fine (installer)
Comment 5•20 years ago
|
||
BTW: This bug here was "exposed" by Bug 295040, before the wrapper prevented displaying the page afaik.
| Assignee | ||
Comment 6•20 years ago
|
||
what's your start page mike?
| Reporter | ||
Comment 7•20 years ago
|
||
As noted at the dupe: my start page was set to "about:" which is what that bug is about. I wasn't seeing anything for a long time, so I'd simply forgotten about it; but the recent build
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•