The default bug view has changed. See this FAQ.

Allow DOMParser to make SVGDocuments

RESOLVED FIXED in mozilla10

Status

()

Core
DOM
--
enhancement
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: Jesse Ruderman, Assigned: smaug)

Tracking

({dev-doc-complete})

Trunk
mozilla10
dev-doc-complete
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Would be useful for fuzzing.
Assignee: nobody → Olli.Pettay
Created attachment 566600 [details] [diff] [review]
patch

Do it in a simple way.
Once we need to be able to force different doc types, we can change aSVGDocument
parameter to an enum.
Attachment #566600 - Flags: review?(jst)

Comment 2

6 years ago
This should really be fixed by fixing 512688.
This is orthogonal to bug 512688.

Updated

6 years ago
Attachment #566600 - Flags: review?(jst) → review+
https://hg.mozilla.org/mozilla-central/rev/85a61d68b152
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Comment 5

6 years ago
Since http://mxr.mozilla.org/mozilla-central/source/content/base/public/nsIDOMParser.idl#80 lists the supported content types, it should probably be updated too.

dev-doc-needed for: https://developer.mozilla.org/en/DOMParser
Keywords: dev-doc-needed
OS: Mac OS X → All
Hardware: x86_64 → All
Target Milestone: --- → mozilla10
I've updated (and created that ยง)
https://developer.mozilla.org/en/DOM/DOMParser#Parsing_a_SVG_document

It would need another update when bug 512688 will be fixed (I've added dev-doc-needed to that bug).
Keywords: dev-doc-needed → dev-doc-complete
You need to log in before you can comment on or make changes to this bug.