DOM XPath - Revision history

Philipj at 08:59, 30 August 2019

2019-08-30T08:59:43Z

@@ Line 1: / Line 1: @@
 If someone ever decides to write down DOM XPath (i.e. a proper version of the [https://www.w3.org/TR/DOM-Level-3-XPath/xpath.html DOM3XPath note]), take this into account:
@@ Line 6: / Line 8: @@
 * Simplifications: https://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0310.html
 * Exceptions: https://bugzilla.mozilla.org/show_bug.cgi?id=743888
 [[Category:Spec coordination]]

Gsnedders: delete trailing whitespace

2019-05-29T12:58:44Z

delete trailing whitespace

← Older revision		Revision as of 12:58, 29 May 2019
Line 49:		Line 49:
	optional XPathNSResolver? resolver);		optional XPathNSResolver? resolver);
	XPathNSResolver createNSResolver(Node nodeResolver);		XPathNSResolver createNSResolver(Node nodeResolver);
	XPathResult evaluate(DOMString expression,		XPathResult evaluate(DOMString expression,
	Node contextNode,		Node contextNode,
	optional XPathNSResolver? resolver,		optional XPathNSResolver? resolver,
	optional unsigned short type,		optional unsigned short type,
	optional XPathResult? result);		optional XPathResult? result);
	};		};

Saschanaz: /* WebIDL interfaces */ Add [NewObject]

2019-05-29T12:11:07Z

WebIDL interfaces: Add [NewObject]

← Older revision		Revision as of 12:11, 29 May 2019
Line 46:		Line 46:

	interface mixin XPathEvaluatorBase {		interface mixin XPathEvaluatorBase {
	XPathExpression createExpression(DOMString expression,		[NewObject] XPathExpression createExpression(DOMString expression,
	optional XPathNSResolver? resolver);		optional XPathNSResolver? resolver);
	XPathNSResolver createNSResolver(Node nodeResolver);		XPathNSResolver createNSResolver(Node nodeResolver);
	XPathResult evaluate(DOMString expression,		XPathResult evaluate(DOMString expression,

Gsnedders: update links

2019-05-29T11:49:27Z

update links

← Older revision		Revision as of 11:49, 29 May 2019
Line 1:		Line 1:
	If someone ever decides to write down DOM XPath (i.e. a proper version of the [~~http~~://www.w3.org/TR/DOM-Level-3-XPath/xpath.html DOM3XPath note]), take this into account:		If someone ever decides to write down DOM XPath (i.e. a proper version of the [https://www.w3.org/TR/DOM-Level-3-XPath/xpath.html DOM3XPath note]), take this into account:

	* Integrate the XPath part of the section [~~http~~://~~www~~.whatwg.org/C#interactions-with-xpath-and-xslt ~~Interactions~~ with XPath and XSLT] from HTML.		* Integrate the XPath part of the section [https://html.spec.whatwg.org/multipage/infrastructure.html#interactions-with-xpath-and-xslt with XPath and XSLT] from HTML.
	* Make it clear that contrary to [https://www.w3.org/TR/1999/REC-xpath-19991116/ XPath 1.0] multiple Text nodes can indeed be returned, even if they are siblings. The DOM is not the XML InfoSet. (As is the case in WebKit and Gecko today.)		* Make it clear that contrary to [https://www.w3.org/TR/1999/REC-xpath-19991116/ XPath 1.0] multiple Text nodes can indeed be returned, even if they are siblings. The DOM is not the XML InfoSet. (As is the case in WebKit and Gecko today.)
	* Make it clear that contrary to [https://www.w3.org/TR/1999/REC-xpath-19991116/ XPath 1.0] the root of the tree is the Document (and not the root element). This means you can return the parent of the root element (can you get all types of siblings? comments, PIs, doctypes? probably, but untested).		* Make it clear that contrary to [https://www.w3.org/TR/1999/REC-xpath-19991116/ XPath 1.0] the root of the tree is the Document (and not the root element). This means you can return the parent of the root element (can you get all types of siblings? comments, PIs, doctypes? probably, but untested).
	* Simplifications: ~~http~~://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0310.html		* Simplifications: https://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0310.html
	* Exceptions: https://bugzilla.mozilla.org/show_bug.cgi?id=743888		* Exceptions: https://bugzilla.mozilla.org/show_bug.cgi?id=743888

Gsnedders: Add link to XPath 1.0

2019-05-29T11:48:14Z

Add link to XPath 1.0

← Older revision		Revision as of 11:48, 29 May 2019
Line 2:		Line 2:

	* Integrate the XPath part of the section [http://www.whatwg.org/C#interactions-with-xpath-and-xslt Interactions with XPath and XSLT] from HTML.		* Integrate the XPath part of the section [http://www.whatwg.org/C#interactions-with-xpath-and-xslt Interactions with XPath and XSLT] from HTML.
	* Make it clear that contrary to XPath 1.0 multiple Text nodes can indeed be returned, even if they are siblings. The DOM is not the XML InfoSet. (As is the case in WebKit and Gecko today.)		* Make it clear that contrary to [https://www.w3.org/TR/1999/REC-xpath-19991116/ XPath 1.0] multiple Text nodes can indeed be returned, even if they are siblings. The DOM is not the XML InfoSet. (As is the case in WebKit and Gecko today.)
	* Make it clear that contrary to XPath 1.0 the root of the tree is the Document (and not the root element). This means you can return the parent of the root element (can you get all types of siblings? comments, PIs, doctypes? probably, but untested).		* Make it clear that contrary to [https://www.w3.org/TR/1999/REC-xpath-19991116/ XPath 1.0] the root of the tree is the Document (and not the root element). This means you can return the parent of the root element (can you get all types of siblings? comments, PIs, doctypes? probably, but untested).
	* Simplifications: http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0310.html		* Simplifications: http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0310.html
	* Exceptions: https://bugzilla.mozilla.org/show_bug.cgi?id=743888		* Exceptions: https://bugzilla.mozilla.org/show_bug.cgi?id=743888

Saschanaz: XPathExpression.prototype.evaluate also accepts an XPathResult object

2019-03-04T14:08:03Z

XPathExpression.prototype.evaluate also accepts an XPathResult object

← Older revision		Revision as of 14:08, 4 March 2019
Line 38:		Line 38:
	XPathResult evaluate(Node contextNode,		XPathResult evaluate(Node contextNode,
	optional unsigned short type,		optional unsigned short type,
	optional ~~object~~? result);		optional XPathResult? result);
	};		};

Saschanaz: evaluate() accepts XPathResult object

2019-03-04T14:04:58Z

evaluate() accepts XPathResult object

← Older revision		Revision as of 14:04, 4 March 2019
Line 53:		Line 53:
	optional XPathNSResolver? resolver,		optional XPathNSResolver? resolver,
	optional unsigned short type,		optional unsigned short type,
	optional ~~object~~? result);		optional XPathResult? result);
	};		};

Saschanaz: singleNodeValue is nullable per the spec and actual browser behavior

2019-03-04T12:53:55Z

singleNodeValue is nullable per the spec and actual browser behavior

← Older revision		Revision as of 12:53, 4 March 2019
Line 27:		Line 27:
	readonly attribute DOMString stringValue;		readonly attribute DOMString stringValue;
	readonly attribute boolean booleanValue;		readonly attribute boolean booleanValue;
	readonly attribute Node singleNodeValue;		readonly attribute Node? singleNodeValue;
	readonly attribute boolean invalidIteratorState;		readonly attribute boolean invalidIteratorState;
	readonly attribute unsigned long snapshotLength;		readonly attribute unsigned long snapshotLength;

Saschanaz: add class="idl" to allow IDL crawlers crawl this

2019-02-01T16:15:09Z

add class="idl" to allow IDL crawlers crawl this

← Older revision		Revision as of 16:15, 1 February 2019
Line 8:		Line 8:

	== WebIDL interfaces ==		== WebIDL interfaces ==
	<pre>		<pre class="idl">
	[Exposed=Window]		[Exposed=Window]
	interface XPathResult {		interface XPathResult {

Saschanaz: adding one more missing [Exposed]

2019-01-30T04:11:42Z

adding one more missing [Exposed]

← Older revision		Revision as of 04:11, 30 January 2019
Line 34:		Line 34:
	};		};

			[Exposed=Window]
	interface XPathExpression {		interface XPathExpression {
	XPathResult evaluate(Node contextNode,		XPathResult evaluate(Node contextNode,