Closed
Bug 284183
Opened 19 years ago
Closed 19 years ago
XML Parse Error on opening an attachment
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird1.1
People
(Reporter: wsheets, Assigned: zbraniecki)
Details
Attachments
(1 file)
1.27 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050227 Firefox/1.0+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050227 Firefox/1.0+ In Thunderbird(head) when I 'open' an attachment I get this error message: XML Parsing Error: undefined entity Location: chrome://global/content/nsProgressDialog.xul Line Number 62, Column 1:<window xmlns:html="http://www.w3.org/1999/xhtml" ^ This error does not prevent the attachment from opening, however. Reproducible: Always Steps to Reproduce: 1.Read an email with an attachment in thunderbird 2.Rightclick on the name of the attachment and select 'Open'. 3.Look for the popup window with the XML Parsing Error message. The type of attachment does not seem to matter. I suspect the attachment should be large enough to invoke a progress dialog.
Comment 1•19 years ago
|
||
This regression was caused by Bug #279768. Thunderbird is no longer finding nsProgressDialog.dtd
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Thunderbird1.1
Comment 2•19 years ago
|
||
Bug #279768 added an ifdef so only NON XUL apps actually package the progress dialog's DTD files. That seems pretty wrong: http://lxr.mozilla.org/mozilla/source/embedding/components/ui/jar.mn#5
Assignee | ||
Comment 3•19 years ago
|
||
taking. Ben regressed on toolkit/locales/jar.mn
Assignee: mscott → gandalf
Status: ASSIGNED → NEW
Assignee | ||
Updated•19 years ago
|
Attachment #176025 -
Flags: review?(axel) → review?(benjamin)
Updated•19 years ago
|
Attachment #176025 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 5•19 years ago
|
||
checked in.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•