Closed Bug 237124 Opened 20 years ago Closed 20 years ago

Make XULDocument.evaluate work from JS

Categories

(Core :: XSLT, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla1.7beta

People

(Reporter: peterv, Assigned: peterv)

Details

Attachments

(1 file, 1 obsolete file)

nsXULDocument already QIs to nsIDOMXPathEvaluator through nsXMLDocument and
nsDocument, it just isn't exposed through DOMCI.
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.7beta
Attached patch Fix (obsolete) — Splinter Review
Attached patch FixSplinter Review
Attachment #143596 - Flags: superreview?(jst)
Attachment #143596 - Flags: review?(jst)
Attachment #143595 - Attachment is obsolete: true
Comment on attachment 143596 [details] [diff] [review]
Fix

Duh, r+sr=jst
Attachment #143596 - Flags: superreview?(jst)
Attachment #143596 - Flags: superreview+
Attachment #143596 - Flags: review?(jst)
Attachment #143596 - Flags: review+
Comment on attachment 143596 [details] [diff] [review]
Fix

Simple one-liner to expose the DOM XPath functions on XULDocuments in JS, they
are already exposed on all other documents (HTML, XML, SVG). Very low risk.
Attachment #143596 - Flags: approval1.7b?
Comment on attachment 143596 [details] [diff] [review]
Fix

a=chofmann for 1.7b
Attachment #143596 - Flags: approval1.7b? → approval1.7b+
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: