Closed Bug 998738 Opened 6 years ago Closed 6 years ago

Consider removing nsIDOMXPathNamespace (and window.XPathNamespace)

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla31

People

(Reporter: ehsan, Assigned: ehsan)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-complete, site-compat)

Attachments

(1 file)

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.
Flags: needinfo?(bzbarsky)
(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
Flags: needinfo?(peterv)
Flags: needinfo?(jonas)
WebKit killed this interface far back.
Killing this sounds good to me.
Flags: needinfo?(jonas)
OK, then.  /me prepares his chainsaw.
Flags: needinfo?(peterv)
Flags: needinfo?(bzbarsky)
Assignee: nobody → ehsan
Attachment #8409989 - Flags: review?(bzbarsky)
Attachment #8409989 - Flags: review?(bzbarsky) → review?(bugs)
Attachment #8409989 - Flags: review?(bugs) → review+
https://hg.mozilla.org/mozilla-central/rev/5db1b6599736
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.