W3C home > Mailing lists > Public > public-html-diffs@w3.org > June 2009

markup fixes (whatwg r3326)

From: poot <cvsmail@w3.org>
Date: Fri, 26 Jun 2009 17:52:18 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090626085218.D93B02BBF2@toro.w3.mag.keio.ac.jp>
markup fixes (whatwg r3326)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2465&r2=1.2466&f=h
http://html5.org/tools/web-apps-tracker?from=3325&to=3326

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2465
retrieving revision 1.2466
diff -u -d -r1.2465 -r1.2466
--- Overview.html	26 Jun 2009 08:43:02 -0000	1.2465
+++ Overview.html	26 Jun 2009 08:52:00 -0000	1.2466
@@ -7526,12 +7526,20 @@
    </dd>
 
 
-  </dl><h3 id="interactions-with-xpath-and-xslt"><span class="secno">3.7 </span>Interactions with XPath and XSLT</h3><p>Implementations of XPath 1.0 that operate on HTML documents
-  parsed or created in the manners described in this specification
-  (e.g. as part of the <code title="">document.evaluate()</code> API)
-  are affected as follows:<p>In addition to the cases where a name expression would match a
+  </dl><div class="impl">
+
+  <h3 id="interactions-with-xpath-and-xslt"><span class="secno">3.7 </span>Interactions with XPath and XSLT</h3>
+
+  <p id="xpath-1.0-processors">Implementations of XPath 1.0 that
+  operate on HTML documents parsed or created in the manners described
+  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:<ul class="brief"><li>The name expression has no namespace.</li>
+  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>
@@ -7541,22 +7549,30 @@
   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="#references">[XPATH10]</a></p><!-- note: version matters for
-  this ref --><hr><p id="dom-based-xslt-1.0-processors">XSLT 1.0 processors outputting
+  HTML regarding which namespace is used for HTML elements. <a href="#references">[XPATH10]</a></p> <!-- note: version matters for
+  this ref -->
+
+  <hr><p id="dom-based-xslt-1.0-processors">XSLT 1.0 processors outputting
   to a DOM when the output method is "html" (either explicitly or via
-  the defaulting rule in XSLT 1.0) are affected as follows:<p>If the transformation program outputs an element in no namespace,
+  the defaulting rule in XSLT 1.0) are affected as follows:</p>
+
+  <p>If the transformation program outputs an element in no namespace,
   the processor must, prior to constructing the corresponding DOM
   element node, change the namespace of the element to the <a href="#html-namespace-0">HTML
   namespace</a>, <a href="#converted-to-ascii-lowercase" title="converted to ASCII
   lowercase">ASCII-lowercase</a> the element's local name, and
   <a href="#converted-to-ascii-lowercase" title="converted to ASCII lowercase">ASCII-lowercase</a>
-  the names of any non-namespaced attributes on the element.<p class="note">This requirement is a <a href="#willful-violation">willful violation</a>
+  the names of any non-namespaced attributes on the element.</p>
+
+  <p class="note">This requirement is a <a href="#willful-violation">willful violation</a>
   of the XSLT 1.0 specification, required because this specification
   changes the namespaces and case-sensitivity rules of HTML in a
   manner that would otherwise be incompatible with DOM-based XSLT
   transformations. (Processors that serialize the output are
-  unaffected.) <a href="#references">[XSLT10]</a></p><!-- note:
-  version matters for this ref --><h3 id="dynamic-markup-insertion"><span class="secno">3.8 </span><dfn>Dynamic markup insertion</dfn></h3><p class="note">APIs for dynamically inserting markup into the
+  unaffected.) <a href="#references">[XSLT10]</a></p> <!-- note:
+  version matters for this ref -->
+
+  </div><h3 id="dynamic-markup-insertion"><span class="secno">3.8 </span><dfn>Dynamic markup insertion</dfn></h3><p class="note">APIs for dynamically inserting markup into the
   document interact with the parser, and thus their behavior, varies
   depending on whether they are used with <a href="#html-documents">HTML documents</a>
   (and the <a href="#html-parser">HTML parser</a>) or XHTML in <a href="#xml-documents">XML
Received on Friday, 26 June 2009 08:52:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:08:57 UTC