Closed
Bug 346362
Opened 18 years ago
Closed 18 years ago
document.evaluate(.., contextNode, ...) should raise an exception if document != contextNode.ownerDocument
Categories
(Core :: XSLT, defect)
Core
XSLT
Tracking
()
RESOLVED
FIXED
People
(Reporter: sylvain.pasche, Assigned: peterv)
References
()
Details
(Keywords: testcase)
Attachments
(3 files)
727 bytes,
text/html
|
Details | |
3.58 KB,
patch
|
sicking
:
review+
sicking
:
superreview+
|
Details | Diff | Splinter Review |
1.09 KB,
patch
|
bzbarsky
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1b1) Gecko/20060727 BonEcho/2.0b1 Build Identifier: The spec says: "contextNode of type Node: ... If the XPathEvaluator was obtained by casting the Document then this must be owned by the same document ..." Reproducible: Always
Reporter | ||
Comment 1•18 years ago
|
||
Assignee | ||
Comment 2•18 years ago
|
||
Assignee: xslt → peterv
Status: UNCONFIRMED → ASSIGNED
Attachment #232325 -
Flags: superreview?(bugmail)
Attachment #232325 -
Flags: review?(bugmail)
Comment 3•18 years ago
|
||
This is causing compat issues with other UAs; we should really get this fixed for 1.9.
Flags: blocking1.9?
Attachment #232325 -
Flags: superreview?(bugmail)
Attachment #232325 -
Flags: superreview+
Attachment #232325 -
Flags: review?(bugmail)
Attachment #232325 -
Flags: review+
Assignee | ||
Updated•18 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 4•18 years ago
|
||
document.evaluate(..., document, ...) throws an exception now. It doesn't own itself. Was this intended?
Assignee | ||
Comment 5•18 years ago
|
||
Not really, though the spec wording should probably be improved a bit.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Assignee | ||
Updated•18 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee | ||
Comment 6•18 years ago
|
||
Attachment #233214 -
Flags: superreview?(bugmail)
Attachment #233214 -
Flags: review?(bugmail)
Comment 7•18 years ago
|
||
I believe this caused bug 348466. Is that just a dupe of this bug, now?
Comment 8•18 years ago
|
||
*** Bug 348466 has been marked as a duplicate of this bug. ***
Comment 9•18 years ago
|
||
Comment on attachment 233214 [details] [diff] [review] Document fix v1 r+sr=bzbarsky
Attachment #233214 -
Flags: superreview?(bugmail)
Attachment #233214 -
Flags: superreview+
Attachment #233214 -
Flags: review?(bugmail)
Attachment #233214 -
Flags: review+
Assignee | ||
Updated•18 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
Comment 10•17 years ago
|
||
Can we test this in the XSLT test suite? Or do we need to add some XSLT mochitests?
Flags: blocking1.9? → in-testsuite?
Assignee | ||
Comment 11•17 years ago
|
||
Or we could integrate the w3c DOM Level 3 XPath testsuite (see http://dev.w3.org/cvsweb/2001/DOM-Test-Suite/tests/level3/xpath/XPathExpression_evaluate_WRONG_DOCUMENT_ERR.xml?rev=1.3&content-type=text/x-cvsweb-markup).
Comment 12•17 years ago
|
||
That sounds ideal, in some ways.
You need to log in
before you can comment on or make changes to this bug.
Description
•