W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2009

html5/spec Overview.html,1.3503,1.3504

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 27 Oct 2009 20:42:14 +0000
To: public-html-commits@w3.org
Message-Id: <E1N2sru-0000hl-Jv@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv2681

Modified Files:
	Overview.html 
Log Message:
validation fix (whatwg r4371)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3503
retrieving revision 1.3504
diff -u -d -r1.3503 -r1.3504
--- Overview.html	27 Oct 2009 20:40:52 -0000	1.3503
+++ Overview.html	27 Oct 2009 20:42:11 -0000	1.3504
@@ -10545,20 +10545,16 @@
   match the <code title="">style</code> production in the following
   ABNF, the character set for which is Unicode. <a href="#refsABNF">[ABNF]</a><pre>style         = no-c-start *( c-start no-c-end c-end no-c-start )
 no-c-start    = &lt;any string that doesn't contain a substring that matches c-start &gt;
-c-start       = "<!--"
-no-c-end      = &lt;any string that doesn't contain a substring that matches c-end ></pre>
-c-end         = "-->"
-
-  <!-- Unmatched comment-like syntax is invalid on a temporary basis,
+c-start       = "&lt;!--"
+no-c-end      = &lt;any string that doesn't contain a substring that matches c-end &gt;
+c-end         = "--&gt;"</pre><!-- Unmatched comment-like syntax is invalid on a temporary basis,
        waiting for IE, WebKit, and Opera to fix their parsing bug
        whereby such comments trigger a weird escape in which </style>
        is ignored. Otherwise, parsing behaviour in those browsers
        could differ substantially from the parsing behaviour of HTML5.
        Once everyone follows the HTML5 spec, we can drop this
        requirement.
-  -->
-
-  <div class="impl">
+  --><div class="impl">
 
   <p>All descendant elements must be processed, according to their
   semantics, before the <code><a href="#the-style-element">style</a></code> element itself is
@@ -10604,28 +10600,18 @@
   relevant specification. For CSS resources, only <code title="">@import</code> rules introduce critical subresources; other
   resources, e.g. fonts or backgrounds, are not.</p>
 
-  </div>
-
-  <p class="note">This specification does not specify a style system,
-  but CSS is expected to be supported by most Web browsers. <a href="#refsCSS">[CSS]</a></p>
-
-  <div class="impl">
+  </div><p class="note">This specification does not specify a style system,
+  but CSS is expected to be supported by most Web browsers. <a href="#refsCSS">[CSS]</a><div class="impl">
 
   <p>The <dfn id="dom-style-media" title="dom-style-media"><code>media</code></dfn>, <dfn id="dom-style-type" title="dom-style-type"><code>type</code></dfn> and <dfn id="dom-style-scoped" title="dom-style-scoped"><code>scoped</code></dfn> IDL attributes
   must <a href="#reflect">reflect</a> the respective content attributes of the
   same name.</p>
 
-  </div>
-
-  <p>The DOM <dfn id="dom-style-disabled" title="dom-style-disabled"><code>disabled</code></dfn> attribute
+  </div><p>The DOM <dfn id="dom-style-disabled" title="dom-style-disabled"><code>disabled</code></dfn> attribute
   behaves as defined <a href="#dom-linkstyle-disabled" title="dom-linkstyle-disabled">for the
-  alternative style sheets DOM</a>.</p>
-
-  <p>The <code>LinkStyle</code> interface is also implemented by
+  alternative style sheets DOM</a>.<p>The <code>LinkStyle</code> interface is also implemented by
   this element; the <a href="#styling">styling processing model</a> defines
-  how. <a href="#refsCSSOM">[CSSOM]</a></p>
-
-  <div class="example">
+  how. <a href="#refsCSSOM">[CSSOM]</a><div class="example">
 
    <p>The following document has its emphasis styled as bright red
    text rather than italics text, while leaving titles of works and
@@ -10648,23 +10634,12 @@
  &lt;/body&gt;
 &lt;/html&gt;</pre>
 
-  </div>
-
-
-
-
-  <h4 id="styling"><span class="secno">4.2.7 </span><dfn title="styling processing model">Styling</dfn></h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
-
-  <p>The <code><a href="#the-link-element">link</a></code> and <code><a href="#the-style-element">style</a></code> elements can provide
+  </div><h4 id="styling"><span class="secno">4.2.7 </span><dfn title="styling processing model">Styling</dfn></h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>The <code><a href="#the-link-element">link</a></code> and <code><a href="#the-style-element">style</a></code> elements can provide
   styling information for the user agent to use when rendering the
   document. The DOM Styling specification specifies what styling
   information is to be used by the user agent and how it is to be
-  used. <a href="#refsCSSOM">[CSSOM]</a></p>
-
-  <p>The <code><a href="#the-style-element">style</a></code> and <code><a href="#the-link-element">link</a></code> elements implement
-  the <code>LinkStyle</code> interface. <a href="#refsCSSOM">[CSSOM]</a></p>
-
-  <div class="impl">
+  used. <a href="#refsCSSOM">[CSSOM]</a><p>The <code><a href="#the-style-element">style</a></code> and <code><a href="#the-link-element">link</a></code> elements implement
+  the <code>LinkStyle</code> interface. <a href="#refsCSSOM">[CSSOM]</a><div class="impl">
 
   <p>For <code><a href="#the-style-element">style</a></code> elements, if the user agent does not
   support the specified styling language, then the <code title="dom-LinkStyle-sheet">sheet</code> attribute of the element's
@@ -10771,38 +10746,19 @@
   <a href="#in-a-document" title="in a document">in that
   <code>Document</code></a>.</p>
 
-  </div>
-
-
-
-  <h3 id="scripting-1"><span class="secno">4.3 </span>Scripting</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
-
-  <p>Scripts allow authors to add interactivity to their documents.</p>
-
-  <p>Authors are encouraged to use declarative alternatives to
+  </div><h3 id="scripting-1"><span class="secno">4.3 </span>Scripting</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>Scripts allow authors to add interactivity to their documents.<p>Authors are encouraged to use declarative alternatives to
   scripting where possible, as declarative mechanisms are often more
-  maintainable, and many users disable scripting.</p>
-
-  <div class="example">
+  maintainable, and many users disable scripting.<div class="example">
    <p>For example, instead of using script to show or hide a section
    to show more details, the <code><a href="#the-details-element">details</a></code> element could be
    used.</p>
-  </div>
-
-  <p>Authors are also encouraged to make their applications degrade
-  gracefully in the absence of scripting support.</p>
-
-  <div class="example">
+  </div><p>Authors are also encouraged to make their applications degrade
+  gracefully in the absence of scripting support.<div class="example">
    <p>For example, if an author provides a link in a table header to
    dynamically resort the table, the link could also be made to
    function without scripts by requesting the sorted table from the
    server.</p>
-  </div>
-
-
-  <h4 id="script"><span class="secno">4.3.1 </span>The <dfn><code>script</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
-
-  </pre><dl class="element"><dt>Categories</dt>
+  </div><h4 id="script"><span class="secno">4.3.1 </span>The <dfn><code>script</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
    <dd><a href="#metadata-content">Metadata content</a>.</dd>
    <dd><a href="#flow-content">Flow content</a>.</dd>
    <dd><a href="#phrasing-content">Phrasing content</a>.</dd>
Received on Tuesday, 27 October 2009 20:42:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 20:42:23 GMT