Confirm
146
edits
Changes
no edit summary
It would probably be a good idea to include a addNamespace(namespaceURI, prefix) method to the IDL, to point into the resolver's namespace map. -- Alex Vincent
== [[XPath: Content Boundaries]] (non-normative) ==
Mozilla's XPath implementation doesn't currently support crossing boundaries between framed content and the container frame element, or between real content and its anonymous children. Our XPath and XPathGenerator can be reasonably expected to support this in the future, so now's the best time to come up with a function syntax for doing this.
Suggested new XPath functions:
* From element in framed document to the container iframe:
** XPath 1: "frameElement(.)" (Alex Vincent)
** XPath 2: "./frameElement()" (Alex Vincent)
* From container iframe to element in the framed document:
** XPath 1: "contentDocument(.)" (Alex Vincent)
** XPath 2: "./contentDocument()" (Alex Vincent)
* From anonymous content to the XBL-bound parent:
** XPath 1: "bindingParent(.)" (Alex Vincent)
** XPath 2: "./bindingParent()" (Alex Vincent)
* From XBL-bound parent to first anonymous child:
** XPath 1: "anonymousChild(.)[1]" (Alex Vincent)
** XPath 2: "./anonymousChild()[1]" (Alex Vincent)
<pre><sicking> we do not want a different syntax in xpath2
<sicking> at least i think not. at the very least we do not want to commit to it</pre>
Please, whatever you think is a better syntax, please suggest it here. All suggestions are welcome.
