I don't see a reason to prevent this, and it's needed to properly initialize things like DOMParser to allow it to parse XUL in XPCOM components, I think.
Created attachment 471486 [details] [diff] [review] Proposed patch This is needed to handle parsing XUL from XPCOM components after sicking's changes.
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #471486 - Flags: review?(jst)
Comment on attachment 471486 [details] [diff] [review] Proposed patch Requesting approval for 2.0 for this simple change.
Attachment #471486 - Flags: approval2.0?
Attachment #471486 - Flags: approval2.0? → approval2.0+
Whiteboard: [need approval] → [need landing]
I assume that a UUID rev is not needed here, is that the case?
That's correct; this is a binary-compatible change, and from script it's easy to tell apart the two versions of the interface by using "in". (All assuming no one is implementing nsIScriptSecurityManager in JS, but if they are they're already So Broken.)
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Whiteboard: [need landing]
Target Milestone: --- → mozilla2.0b6
You need to log in before you can comment on or make changes to this bug.