W3C home > Mailing lists > Public > public-html-diffs@w3.org > March 2010

hixie: w3c continues to insist on using html4 apparently.

From: poot <cvsmail@w3.org>
Date: Thu, 4 Mar 2010 16:07:26 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100304070727.29ADC2BBED@toro.w3.mag.keio.ac.jp>
hixie: w3c continues to insist on using html4 apparently.

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3867&r2=1.3868&f=h

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3867
retrieving revision 1.3868
diff -u -d -r1.3867 -r1.3868
--- Overview.html	3 Mar 2010 23:55:07 -0000	1.3867
+++ Overview.html	4 Mar 2010 07:07:07 -0000	1.3868
@@ -236,7 +236,7 @@
 
    .details-example img { vertical-align: top; }
 
-  </style><style>
+  </style><style type="text/css">
    .domintro:before { display: table; margin: -1em -0.5em -0.5em auto; width: auto; content: 'This box is non-normative. Implementation requirements are given below this box.'; color: red; border: solid 2px; background: white; padding: 0 0.25em; }
   </style><link href="data:text/css," id="complete" rel="stylesheet" title="Complete specification"><link href="data:text/css,.impl%20{%20display:%20none;%20}%0Ahtml%20{%20border:%20solid%20yellow;%20}%20.domintro:before%20{%20display:%20none;%20}" id="author" rel="alternate stylesheet" title="Author documentation only"><link href="data:text/css,.impl%20{%20background:%20%23FFEEEE;%20}" id="highlight" rel="alternate stylesheet" title="Highlight implementation requirements"><script type="text/javascript">
    function getCookie(name) {
@@ -9513,7 +9513,7 @@
   followed and 404 responses will cause the external resource to not
   be applied.)</p>
 
-  <!-- the next few paragraph are similar to text in the <style> section -->
+  <!-- the next few paragraph are similar to text in the <style type="text/css"> section -->
   <p>Once the attempts to obtain the resource and its critical
   subresources are complete, the user agent must, if the loads were
   successful, <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple
@@ -9585,13 +9585,13 @@
   <a href="#view">view</a> when the <code title="attr-link-media"><a href="#attr-link-media">media</a></code> attribute's value <a href="#matches-the-environment">matches
   the environment</a> of that view and the other relevant
   conditions apply, and must not apply it otherwise.</p><!-- note
-  similar text in <style> section -->
+  similar text in <style type="text/css"> section -->
 
   <p class="note">The external resource might have further
   restrictions defined within that limit its applicability. For
   example, a CSS style sheet might have some <code title="">@media</code> blocks. This specification does not override
   such further restrictions or requirements.</p><!-- note similar text
-  in <style> section -->
+  in <style type="text/css"> section -->
 
   </div><p id="default-media">The default, if the <code title="attr-link-media"><a href="#attr-link-media">media</a></code> attribute is omitted, is "<code title="">all</code>", meaning that by default links apply to all
   media.<p>The <dfn id="attr-link-hreflang" title="attr-link-hreflang"><code>hreflang</code></dfn>
@@ -10576,7 +10576,7 @@
   when the processor is invoked.<!-- so dynamic changes to the base
   URL don't affect the CSS --></p>
 
-  <!-- the next few paragraph are similar to text in the <style> section -->
+  <!-- the next few paragraph are similar to text in the <style type="text/css"> section -->
   <p>Once the attempts to obtain the style sheet's critical
   subresources, if any, are complete, or, if the style sheet has no
   critical subresources, once the style sheet has been parsed and
@@ -11351,7 +11351,7 @@
   <p>User agents may support other <a href="#mime-type" title="MIME type">MIME
   types</a> and other languages.</p>
 
-  <!-- this paragraph is also present in the <style> section -->
+  <!-- this paragraph is also present in the <style type="text/css"> section -->
   <p>When examining types to determine if they support the language,
   user agents must not ignore unknown MIME parameters &mdash; types
   with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown
@@ -50867,7 +50867,7 @@
   element is not a <a href="#space-character">space character</a> or a <a href="#syntax-comments" title="syntax-comments">comment</a>, except if the first thing
   inside the <code><a href="#the-body-element-0">body</a></code> element is a <code><a href="#script">script</a></code> or
   <code><a href="#the-style-element">style</a></code> element. <!-- Note that even if the </head> end
-  tag is present, the parser makes <style> and <script type="text/javascript"> elements
+  tag is present, the parser makes <style type="text/css"> and <script type="text/javascript"> elements
   between </head> and <body> end up in the <head> instead of implying
   the <body> --></p><!-- </body> --><p>A <code><a href="#the-body-element-0">body</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
   tag</a> may be omitted if the <code><a href="#the-body-element-0">body</a></code> element is not
@@ -52030,7 +52030,7 @@
    all intentional. The only thing it doesn't handle is the
    scripting-disabled fragment parsing case for a <head> element
    containing a <noscript> which itself contains something other than
-   a <link> or a <style> element; you'd expect that to break out of
+   a <link> or a <style type="text/css"> element; you'd expect that to break out of
    the <noscript> but it doesn't. This is an edge case that doesn't
    affect the spec, since the algorithm for fragment parsing is only
    used for innerHTML/outerHTML/insertAdjacentHTML(), where we know
Received on Thursday, 4 March 2010 07:07:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:18 GMT