[] (0) New text for XPath hack.

git-svn-id: http://svn.whatwg.org/webapps@3800 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -71,7 +71,7 @@
   <div class=head>
    <p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <h1>HTML5</h1>
-   <h2 class="no-num no-toc" id=draft-standard-&mdash;-10-september-2009>Draft Standard &mdash; 10 September 2009</h2>
+   <h2 class="no-num no-toc" id=draft-standard-&mdash;-11-september-2009>Draft Standard &mdash; 11 September 2009</h2>
    <p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -9290,29 +9290,18 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   in this specification (e.g. as part of the <code title="">document.evaluate()</code> API) are affected as
   follows:</p>
 
-  <p>In addition to the cases where a name expression would match a
-  node per XPath 1.0, a name expression must evaluate to matching a
-  node when all the following conditions are also met:</p>
-
-  <ul class=brief><li>The name expression has no namespace.</li>
-   <li>The name expression has local name that is a match for <var title="">local</var>.</li>
-   <li>The expression is being tested against an element node.</li>
-   <li>The element has local name <var title="">local</var>.</li>
-   <li>The element is in the <a href=#html-namespace-0>HTML namespace</a>.</li>
-   <li>The element's document is an <a href=#html-documents title="HTML documents">HTML document</a>.</li>
-  </ul><p>Irrespective of the requirements defined in XPath 1.0, a name
-  expression must not evaluate to matching a node when the following
-  conditions are all met:</p>
-
-  <ul class=brief><li>The name expression has no namespace.</li>
-   <li>The expression is being tested against an element node.</li>
-   <li>The element is in no namespace.</li>
-   <li>The element's document is an <a href=#html-documents title="HTML documents">HTML document</a>.</li>
-  </ul><p class=note>These requirements are a <a href=#willful-violation>willful
-  violation</a> of the XPath 1.0 specification, motivated by desire
-  to have implementations be compatible with legacy content while
-  still supporting the changes that this specification introduces to
-  HTML regarding which namespace is used for HTML elements. <a href=#refsXPATH10>[XPATH10]</a></p> <!-- note: version matters for
+  <p>A node test consisting of a <a href=http://www.w3.org/TR/REC-xml-names/#NT-QName>QName</a>
+  with no prefix (i.e. that matches the <a href=http://www.w3.org/TR/REC-xml-names/#NT-UnprefixedName>UnprefixedName</a>
+  production) must be treated as if it instead had the namespace URI
+  equal to <a href=#html-namespace-0>HTML namespace</a> when the node is an element
+  whose document is an <a href=#html-documents title="HTML documents">HTML
+  document</a>. <a href=#refsXPATH10>[XPATH10]</a> <a href=#refsXMLNS>[XMLNS]</a></p>
+
+  <p class=note>This requirement is a <a href=#willful-violation>willful violation</a>
+  of the XPath 1.0 specification, motivated by desire to have
+  implementations be compatible with legacy content while still
+  supporting the changes that this specification introduces to HTML
+  regarding which namespace is used for HTML elements. <a href=#refsXPATH10>[XPATH10]</a></p> <!-- note: version matters for
   this ref -->
 
   <hr><p id=dom-based-xslt-1.0-processors>XSLT 1.0 processors outputting

source

@@ -9637,35 +9637,21 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   title="">document.evaluate()</code> API) are affected as
   follows:</p>
 
-  <p>In addition to the cases where a name expression would match a
-  node per XPath 1.0, a name expression must evaluate to matching a
-  node when all the following conditions are also met:</p>
-
-  <ul class="brief">
-   <li>The name expression has no namespace.</li>
-   <li>The name expression has local name that is a match for <var title="">local</var>.</li>
-   <li>The expression is being tested against an element node.</li>
-   <li>The element has local name <var title="">local</var>.</li>
-   <li>The element is in the <span>HTML namespace</span>.</li>
-   <li>The element's document is an <span title="HTML documents">HTML document</span>.</li>
-  </ul>
-
-  <p>Irrespective of the requirements defined in XPath 1.0, a name
-  expression must not evaluate to matching a node when the following
-  conditions are all met:</p>
-
-  <ul class="brief">
-   <li>The name expression has no namespace.</li>
-   <li>The expression is being tested against an element node.</li>
-   <li>The element is in no namespace.</li>
-   <li>The element's document is an <span title="HTML documents">HTML document</span>.</li>
-  </ul>
+  <p>A node test consisting of a <a
+  href="http://www.w3.org/TR/REC-xml-names/#NT-QName">QName</a>
+  with no prefix (i.e. that matches the <a
+  href="http://www.w3.org/TR/REC-xml-names/#NT-UnprefixedName">UnprefixedName</a>
+  production) must be treated as if it instead had the namespace URI
+  equal to <span>HTML namespace</span> when the node is an element
+  whose document is an <span title="HTML documents">HTML
+  document</span>. <a href="#refsXPATH10">[XPATH10]</a> <a
+  href="#refsXMLNS">[XMLNS]</a></p>
 
-  <p class="note">These requirements are a <span>willful
-  violation</span> of the XPath 1.0 specification, motivated by desire
-  to have implementations be compatible with legacy content while
-  still supporting the changes that this specification introduces to
-  HTML regarding which namespace is used for HTML elements. <a
+  <p class="note">This requirement is a <span>willful violation</span>
+  of the XPath 1.0 specification, motivated by desire to have
+  implementations be compatible with legacy content while still
+  supporting the changes that this specification introduces to HTML
+  regarding which namespace is used for HTML elements. <a
   href="#refsXPATH10">[XPATH10]</a></p> <!-- note: version matters for
   this ref -->