Closed Bug 998738 Opened 8 years ago Closed 8 years ago
Consider removing ns
IDOMXPath Namespace (and window .XPath Namespace)
We don't implement this interface, and just expose it on the global object as XPathNamespace, and ship it in the Ci shim to content as well. Is there a good reason to keep it around? No add-ons seem to depend on it either.
(Note that the unused implementation of this interface was removed in bug 817273.)
(Also note that this will be the last blocker to making nsIDOMNode non-scriptable.)
Flagging other likely targets
WebKit killed this interface far back.
See Also: → https://bugs.webkit.org/show_bug.cgi?id=59381
Killing this sounds good to me.
OK, then. /me prepares his chainsaw.
Attachment #8409989 - Flags: review?(bzbarsky) → review?(bugs)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
Added this to the site compat doc: https://developer.mozilla.org/en-US/Firefox/Releases/31/Site_Compatibility
You need to log in before you can comment on or make changes to this bug.