Closed Bug 286074 Opened 20 years ago Closed 9 years ago

Add charset to XML declaration

Categories

(Core Graveyard :: Profile: Roaming, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: annevk, Unassigned)

References

Details

Attachments

(1 file)

Per bug 247024 comment 12 filing a separate bug so the issue can be tracked separately. See RFC 3023 section 8.4 for the reason why we should avoid text/xml. I'm going to attach a patch that replaces text/xml with application/xml. Can someone tell me whether that is a good thing or not and from who I should get review? Thanks.
Attached patch patch #1 (deleted) — Splinter Review
Attachment #177368 - Flags: review?(ben.bucksch)
That link doesn't work, but I should've said 8.5. Sorry about that. Anyway, I'm no longer driving this patch.
Comment on attachment 177368 [details] [diff] [review] patch #1 I don't think RFC 3023 section 8.5 is a good reason to avoid text/xml. It just says that if the documents *omits* the charset in the XML declaration, then it needs to be treated as ASCII. That is a good reason to add a charset to the declaration, not to avoid text/xml. WONTFIX.
Attachment #177368 - Flags: review?(ben.bucksch) → review-
filesList.js, function createListingFile()
Summary: avoid usage of text/xml → Add charset to XML declaration
This bug is filed in a bugzilla component related to pre-Firefox code which no longer exists. I believe it is no longer relevant and I am therefore closing it INCOMPLETE. If you believe that this bug is still valid and needs to be fixed, please reopen it and move it to the Toolkit:Startup and Profile System product/component.
No longer blocks: 1243899
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: