Closed Bug 331616 Opened 19 years ago Closed 18 years ago

XML Parsing Error popup when dbl-click on line copied from web

Categories

(Thunderbird :: Message Compose Window, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: vbaddict, Assigned: mscott)

References

()

Details

(Keywords: fixed1.8.1.3)

Attachments

(2 files, 1 obsolete file)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060214 Camino/1.0 Copied text from above url [using Camino] into email, then dbl-clicked on the green dashed line. Got popup XML Parsing Error: undefined entity Location: chrome://editor/content/EdFormProps.xul Line number 44, column 1: <dialog title="&windowTitle.label;" ^ Reproducible: Always Steps to Reproduce: 1. copy first 2 paragraphs of text from above url into a html email 2. dbl-click on green dashed line 3. Actual Results: could not do any more editing with that email window. could not close it. could minimize it and move it around. could not quit Thunderbird. had to Force Quit. Expected Results: at least let me trash that email and start a new one. at least Quit when told to. I have no add-ons, just out-of-the box TBird. Green line did not appear on the web page but did appear when text copied to email. As long as I didn't mess with the green lines everything was fine.
.tiff file
Attachment #216124 - Attachment mime type: image/gif → image/tiff
This is because form elements are not supported in Thunderbird's fork of Editor. The XUL files link to non-existent DTDs. Simpler steps to reproduce: 1. From the menu: Insert > HTML 2. Enter: "<textarea></textarea>" or "<form method='get'><input value='foo'/></form>" 3. Double-click the textarea or the input box Actual results: 1. XML Parsing error Expected results: 1. Either don't show anything (fail silently), or display a non-broken version of EdTextAreaProps.xul or EdInputProps.xul.
Status: UNCONFIRMED → NEW
Ever confirmed: true
For Tb 2, the only solution not breaking the l10n freeze, is to make form elements just do nothing when double-clicked. I'm just commenting out the respective doCommand functions in ComposerCommands.js.
Attachment #257229 - Flags: review?(mscott)
Attachment #257229 - Attachment is patch: true
Attachment #257229 - Attachment mime type: text/x-patch → text/plain
OS: Mac OS X → All
Hardware: Macintosh → All
Actually, we have the DTD files in CVS, they're just not shipped with Tb. After adding them manually to comm.jar, this works. So we have an alternative solution - just ship these DTDs with Thunderbird (localizers should have already translated them, at least we did that for 'pl') EditorButtonProperties.dtd EditorFieldSetProperties.dtd EditorFormProperties.dtd EditorInputProperties.dtd EditorLabelProperties.dtd EditorTextAreaProperties.dtd EditorSelectProperties.dtd
This is the better solution - ship the missing DTDs.
Attachment #257229 - Attachment is obsolete: true
Attachment #257237 - Flags: review?(mscott)
Attachment #257229 - Flags: review?(mscott)
Pike, what do you think about comment 4 and comment 5?
blocking‑thunderbird2=?
Flags: blocking-thunderbird2?
Yeah, we should package those existing localized files in Thunderbird. I'm not sure why they are currently treated as suite only. I'll land this on the trunk and the branch. Thanks for the patch Marek!
Flags: blocking-thunderbird2? → blocking-thunderbird2+
Comment on attachment 257237 [details] [diff] [review] Ship the form-related DTDs with Tb I did a quick search through lxr on one of the files and verified that it existed in all of the locales we have for Thunderbird.
Attachment #257237 - Flags: review?(mscott) → review+
Status: NEW → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.1.3
Resolution: --- → FIXED
I'd call adding non-used strings to the build at least semi-string-freeze-breaking. A short glance at EditorFormProperties.dtd looks like most of them are translated, but we should get an announcement of this. Having some sorts of QA howto for the exposed strings would be great, so that localizers can actually test their strings.
I just checked the tinderboxen and I can verify that no locale has been broken because of this check-in. I'll post to .l10n shortly about how to QA this.
Verified with 2.0pre (20070304)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: