Expose sanitizer flags to extensions/XULRunner apps that wish to use sanitized fragment parsing

RESOLVED FIXED in mozilla14

Status

()

Core
HTML: Parser
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: hsivonen, Assigned: hsivonen)

Tracking

({dev-doc-needed})

Trunk
mozilla14
dev-doc-needed
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

5 years ago
Add nsIDOMDocumentFragment nsIParserUtils::parseFragment(in AString fragment, in boolean isXML, in nsIURI baseURI, in nsIDOMElement element, in unsigned long flags); that's like nsIDOMDocumentFragment nsIScriptableUnescapeHTML::parseFragment(in AString fragment, in boolean isXML, in nsIURI baseURI, in nsIDOMElement element); but exposes the sanitizer flags.
(Assignee)

Comment 1

5 years ago
Created attachment 607178 [details] [diff] [review]
Expose a new method, migrate callers
(Assignee)

Comment 2

5 years ago
Created attachment 607564 [details] [diff] [review]
Expose a new method, migrate callers, with IDL that actually compiles
Attachment #607178 - Attachment is obsolete: true
(Assignee)

Comment 3

5 years ago
Comment on attachment 607564 [details] [diff] [review]
Expose a new method, migrate callers, with IDL that actually compiles

Let's believe the sanitizer flags work based on the test case landed for bug 650776.
Attachment #607564 - Flags: review?(bugs)

Updated

5 years ago
Attachment #607564 - Flags: review?(bugs) → review+
(Assignee)

Comment 4

5 years ago
Thanks for the r+.

https://hg.mozilla.org/integration/mozilla-inbound/rev/eb7570cdfb9e
Status: NEW → ASSIGNED
(Assignee)

Updated

5 years ago
Keywords: dev-doc-needed
https://hg.mozilla.org/mozilla-central/rev/eb7570cdfb9e
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla14
You need to log in before you can comment on or make changes to this bug.