[html5] r2475 - [e] (0) Split the rendering and obsolete features sections from each other.

whatwg at whatwg.org whatwg at whatwg.org
Sat Nov 29 13:59:30 PST 2008


Author: ianh
Date: 2008-11-29 13:59:29 -0800 (Sat, 29 Nov 2008)
New Revision: 2475

Modified:
   index
   source
Log:
[e] (0) Split the rendering and obsolete features sections from each other.

Modified: index
===================================================================
--- index	2008-11-29 21:48:26 UTC (rev 2474)
+++ index	2008-11-29 21:59:29 UTC (rev 2475)
@@ -965,24 +965,26 @@
    <li><a href=#serializing-html-fragments><span class=secno>8.4 </span>Serializing HTML fragments</a></li>
    <li><a href=#parsing-html-fragments><span class=secno>8.5 </span>Parsing HTML fragments</a></li>
    <li><a href=#named-character-references><span class=secno>8.6 </span>Named character references</a></ol></li>
- <li><a href=#rendering><span class=secno>9 </span>Rendering and user-agent behavior</a>
+ <li><a href=#rendering><span class=secno>9 </span>Rendering</a>
   <ol>
-   <li><a href=#rendering-and-the-dom><span class=secno>9.1 </span>Rendering and the DOM</a></li>
-   <li><a href=#rendering-and-menus/toolbars><span class=secno>9.2 </span>Rendering and menus/toolbars</a>
+   <li><a href=#rendering-and-menus/toolbars><span class=secno>9.1 </span>Rendering and menus/toolbars</a>
     <ol>
-     <li><a href="#the-'icon'-property"><span class=secno>9.2.1 </span>The 'icon' property</a></ol></li>
-   <li><a href=#obsolete-elements,-attributes,-and-apis><span class=secno>9.3 </span>Obsolete elements, attributes, and APIs</a>
+     <li><a href="#the-'icon'-property"><span class=secno>9.1.1 </span>The 'icon' property</a></ol></ol></li>
+ <li><a href=#obsolete-features><span class=secno>10 </span>Obsolete features</a>
+  <ol>
+   <li><a href=#obsolete-elements><span class=secno>10.1 </span>Obsolete elements</a>
     <ol>
-     <li><a href=#the-body-element-0><span class=secno>9.3.1 </span>The <code>body</code> element</a></li>
-     <li><a href=#the-applet-element><span class=secno>9.3.2 </span>The <code>applet</code> element</a></ol></ol></li>
- <li><a href=#no><span class=secno>10 </span>Things that you can't do with this specification because
+     <li><a href=#the-body-element-0><span class=secno>10.1.1 </span>The <code>body</code> element</a></li>
+     <li><a href=#the-applet-element><span class=secno>10.1.2 </span>The <code>applet</code> element</a></ol></ol></li>
+ <li><a href=#no><span class=secno>11 </span>Things that you can't do with this specification because
   they are better handled using other technologies that are further
   described herein</a>
   <ol>
-   <li><a href=#localization><span class=secno>10.1 </span>Localization</a></li>
-   <li><a href=#declarative-2d-vector-graphics-and-animation><span class=secno>10.2 </span>Declarative 2D vector graphics and animation</a></li>
-   <li><a href=#declarative-3d-scenes><span class=secno>10.3 </span>Declarative 3D scenes</a></li>
-   <li><a href=#timers><span class=secno>10.4 </span>Timers</a></ol></li>
+   <li><a href=#localization><span class=secno>11.1 </span>Localization</a></li>
+   <li><a href=#declarative-2d-vector-graphics-and-animation><span class=secno>11.2 </span>Declarative 2D vector graphics and animation</a></li>
+   <li><a href=#declarative-3d-scenes><span class=secno>11.3 </span>Declarative 3D scenes</a></li>
+   <li><a href=#timers><span class=secno>11.4 </span>Timers</a></li>
+   <li><a href=#rendering-and-the-dom><span class=secno>11.5 </span>Rendering and the DOM</a></ol></li>
  <li><a class=no-num href=#index>Index</a></li>
  <li><a class=no-num href=#references>References</a></li>
  <li><a class=no-num href=#acknowledgements>Acknowledgements</a></ol>
@@ -53289,7 +53291,7 @@
 
 
 
-  <h2 id=rendering><span class=secno>9 </span>Rendering and user-agent behavior</h2>
+  <h2 id=rendering><span class=secno>9 </span>Rendering</h2>
 
   <!-- XXX
 
@@ -53454,39 +53456,15 @@
   be compared case-insensitively.</p>
 
 
-  <h3 id=rendering-and-the-dom><span class=secno>9.1 </span>Rendering and the DOM</h3>
+  <p class=XXX>Need to define the content attributes of BODY in
+  terms of CSS or something.</p>
 
-  <p class=XXX>This section is wrong. mediaMode will end up on
-  Window, I think. All views implement Window.</p>
 
-  <p>Any object implement the <code>AbstractView</code> interface must
-  also implement the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface.</p>
 
-  <pre class=idl>interface <dfn id=mediamodeabstractview>MediaModeAbstractView</dfn> {
-  readonly attribute DOMString <a href=#mediamode>mediaMode</a>;
-};</pre>
+  <h3 id=rendering-and-menus/toolbars><span class=secno>9.1 </span>Rendering and menus/toolbars</h3>
 
-  <p>The <dfn id=mediamode><code>mediaMode</code></dfn> attribute on objects
-  implementing the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface must
-  return the string that represents the canvas' current rendering mode
-  (<code>screen</code>, <code>print</code>, etc). This is a lowercase
-  string, as <a href=http://www.w3.org/TR/CSS21/media.html#media-types>defined by
-  the CSS specification</a>. <a href=#refsCSS21>[CSS21]</a></p>
+  <h4 id="the-'icon'-property"><span class=secno>9.1.1 </span>The 'icon' property</h4>
 
-  <p>Some user agents may support multiple media, in which case there
-  will exist multiple objects implementing the
-  <code>AbstractView</code> interface. Only the default view
-  implements the <code><a href=#window>Window</a></code> interface. The other views can be
-  reached using the <code><a href=#view>view</a></code> attribute of the
-  <code>UIEvent</code> interface, during event propagation. There is no
-  way currently to enumerate all the views.</p>
-
-  <!-- XXX examples! -->
-
-  <h3 id=rendering-and-menus/toolbars><span class=secno>9.2 </span>Rendering and menus/toolbars</h3>
-
-  <h4 id="the-'icon'-property"><span class=secno>9.2.1 </span>The 'icon' property</h4>
-
   <p>UAs should use the command's Icon as the default generic icon
   provided by the user agent when the 'icon' property computes to
   'auto' on an element that either defines a command or refers to one
@@ -53495,13 +53473,17 @@
   that image instead.</p>
 
 
-  <h3 id=obsolete-elements,-attributes,-and-apis><span class=secno>9.3 </span>Obsolete elements, attributes, and APIs</h3>
 
-  <h4 id=the-body-element-0><span class=secno>9.3.1 </span>The <code><a href=#the-body-element>body</a></code> element</h4>
+  <h2 id=obsolete-features><span class=secno>10 </span>Obsolete features</h2>
 
-  <p class=XXX>Need to define the content attributes in terms
-  of CSS or something.</p>
+  <p>Authors and documents must not use the features listed in this
+  section. They are documented to enable user agents to support legacy
+  content in an interoperable fashion.</p>
 
+  <h3 id=obsolete-elements><span class=secno>10.1 </span>Obsolete elements</h3>
+
+  <h4 id=the-body-element-0><span class=secno>10.1.1 </span>The <code><a href=#the-body-element>body</a></code> element</h4>
+
   <pre class=idl>[XXX] interface <a href=#htmldocument>HTMLDocument</a> {
            attribute DOMString <a href=#dom-document-fgcolor title=dom-document-fgColor>fgColor</a>;
            attribute DOMString <a href=#dom-document-bgcolor title=dom-document-bgColor>bgColor</a>;
@@ -53576,7 +53558,7 @@
 
 
 
-  <h4 id=the-applet-element><span class=secno>9.3.2 </span>The <dfn><code>applet</code></dfn> element</h4>
+  <h4 id=the-applet-element><span class=secno>10.1.2 </span>The <dfn><code>applet</code></dfn> element</h4>
 
   <p>The <code><a href=#the-applet-element>applet</a></code> element is a Java-specific variant of the
   <code><a href=#the-embed-element>embed</a></code> element. In HTML5 the <code><a href=#the-applet-element>applet</a></code> element
@@ -53606,7 +53588,7 @@
 
 
 
-  <h2 id=no><span class=secno>10 </span>Things that you can't do with this specification because
+  <h2 id=no><span class=secno>11 </span>Things that you can't do with this specification because
   they are better handled using other technologies that are further
   described herein</h2>
 
@@ -53618,7 +53600,7 @@
   that can be integrated into this one. This section covers some of
   the more common requests.</p>
 
-  <h3 id=localization><span class=secno>10.1 </span>Localization</h3>
+  <h3 id=localization><span class=secno>11.1 </span>Localization</h3>
 
   <p>If you wish to create localized versions of an HTML application,
   the best solution is to preprocess the files on the server, and then
@@ -53627,13 +53609,13 @@
   <!-- <p>XXX example here</p> -->
 
 <!--XXXSVG (remove next section)-->
-  <h3 id=declarative-2d-vector-graphics-and-animation><span class=secno>10.2 </span>Declarative 2D vector graphics and animation</h3>
+  <h3 id=declarative-2d-vector-graphics-and-animation><span class=secno>11.2 </span>Declarative 2D vector graphics and animation</h3>
   <p>Embedding vector graphics into XHTML documents is the domain of
   SVG.</p>
 
   <!-- <p>XXX example here</p> -->
 
-  <h3 id=declarative-3d-scenes><span class=secno>10.3 </span>Declarative 3D scenes</h3>
+  <h3 id=declarative-3d-scenes><span class=secno>11.3 </span>Declarative 3D scenes</h3>
 
   <p>Embedding 3D imagery into XHTML documents is the domain of X3D,
   or technologies based on X3D that are namespace-aware.</p>
@@ -53642,7 +53624,7 @@
 
 
 
-  <h3 id=timers><span class=secno>10.4 </span>Timers</h3>
+  <h3 id=timers><span class=secno>11.4 </span>Timers</h3>
 
   <p class=XXX>This section is expected to be moved to its own
   specification in due course. It needs a lot of work to actually make
@@ -53714,7 +53696,39 @@
 
 
 
+  <h3 id=rendering-and-the-dom><span class=secno>11.5 </span>Rendering and the DOM</h3>
 
+  <p class=XXX>This section is expected to be moved to its own
+  specification in due course. It needs a lot of work to actually make
+  it into a semi-decent spec.</p>
+
+  <p>Any object implement the <code>AbstractView</code> interface must
+  also implement the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface.</p>
+
+  <pre class=idl>interface <dfn id=mediamodeabstractview>MediaModeAbstractView</dfn> {
+  readonly attribute DOMString <a href=#mediamode>mediaMode</a>;
+};</pre>
+
+  <p>The <dfn id=mediamode><code>mediaMode</code></dfn> attribute on objects
+  implementing the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface must
+  return the string that represents the canvas' current rendering mode
+  (<code>screen</code>, <code>print</code>, etc). This is a lowercase
+  string, as <a href=http://www.w3.org/TR/CSS21/media.html#media-types>defined by
+  the CSS specification</a>. <a href=#refsCSS21>[CSS21]</a></p>
+
+  <p>Some user agents may support multiple media, in which case there
+  will exist multiple objects implementing the
+  <code>AbstractView</code> interface. Only the default view
+  implements the <code><a href=#window>Window</a></code> interface. The other views can be
+  reached using the <code><a href=#view>view</a></code> attribute of the
+  <code>UIEvent</code> interface, during event propagation. There is no
+  way currently to enumerate all the views.</p>
+
+  <!-- XXX examples! -->
+
+
+
+
   <h2 class=no-num id=index>Index</h2>
 
   <p><em>This section is non-normative.</em></p>

Modified: source
===================================================================
--- source	2008-11-29 21:48:26 UTC (rev 2474)
+++ source	2008-11-29 21:59:29 UTC (rev 2475)
@@ -58193,7 +58193,7 @@
 
 
 
-  <h2 id="rendering">Rendering and user-agent behavior</h2>
+  <h2 id="rendering">Rendering</h2>
 
   <!-- XXX
 
@@ -58358,36 +58358,11 @@
   be compared case-insensitively.</p>
 
 
-  <h3>Rendering and the DOM</h3>
+  <p class="XXX">Need to define the content attributes of BODY in
+  terms of CSS or something.</p>
 
-  <p class="XXX">This section is wrong. mediaMode will end up on
-  Window, I think. All views implement Window.</p>
 
-  <p>Any object implement the <code>AbstractView</code> interface must
-  also implement the <code>MediaModeAbstractView</code> interface.</p>
 
-  <pre class="idl">interface <dfn>MediaModeAbstractView</dfn> {
-  readonly attribute DOMString <span>mediaMode</span>;
-};</pre>
-
-  <p>The <dfn><code>mediaMode</code></dfn> attribute on objects
-  implementing the <code>MediaModeAbstractView</code> interface must
-  return the string that represents the canvas' current rendering mode
-  (<code>screen</code>, <code>print</code>, etc). This is a lowercase
-  string, as <a
-  href="http://www.w3.org/TR/CSS21/media.html#media-types">defined by
-  the CSS specification</a>. <a href="#refsCSS21">[CSS21]</a></p>
-
-  <p>Some user agents may support multiple media, in which case there
-  will exist multiple objects implementing the
-  <code>AbstractView</code> interface. Only the default view
-  implements the <code>Window</code> interface. The other views can be
-  reached using the <code>view</code> attribute of the
-  <code>UIEvent</code> interface, during event propagation. There is no
-  way currently to enumerate all the views.</p>
-
-  <!-- XXX examples! -->
-
   <h3>Rendering and menus/toolbars</h3>
 
   <h4>The 'icon' property</h4>
@@ -58400,13 +58375,17 @@
   that image instead.</p>
 
 
-  <h3>Obsolete elements, attributes, and APIs</h3>
 
+  <h2>Obsolete features</h2>
+
+  <p>Authors and documents must not use the features listed in this
+  section. They are documented to enable user agents to support legacy
+  content in an interoperable fashion.</p>
+
+  <h3>Obsolete elements</h3>
+
   <h4>The <code>body</code> element</h4>
 
-  <p class="XXX">Need to define the content attributes in terms
-  of CSS or something.</p>
-
   <pre class="idl">[XXX] interface <span>HTMLDocument</span> {
            attribute DOMString <span title="dom-document-fgColor">fgColor</span>;
            attribute DOMString <span title="dom-document-bgColor">bgColor</span>;
@@ -58631,7 +58610,40 @@
 
 
 
+  <h3>Rendering and the DOM</h3>
 
+  <p class="XXX">This section is expected to be moved to its own
+  specification in due course. It needs a lot of work to actually make
+  it into a semi-decent spec.</p>
+
+  <p>Any object implement the <code>AbstractView</code> interface must
+  also implement the <code>MediaModeAbstractView</code> interface.</p>
+
+  <pre class="idl">interface <dfn>MediaModeAbstractView</dfn> {
+  readonly attribute DOMString <span>mediaMode</span>;
+};</pre>
+
+  <p>The <dfn><code>mediaMode</code></dfn> attribute on objects
+  implementing the <code>MediaModeAbstractView</code> interface must
+  return the string that represents the canvas' current rendering mode
+  (<code>screen</code>, <code>print</code>, etc). This is a lowercase
+  string, as <a
+  href="http://www.w3.org/TR/CSS21/media.html#media-types">defined by
+  the CSS specification</a>. <a href="#refsCSS21">[CSS21]</a></p>
+
+  <p>Some user agents may support multiple media, in which case there
+  will exist multiple objects implementing the
+  <code>AbstractView</code> interface. Only the default view
+  implements the <code>Window</code> interface. The other views can be
+  reached using the <code>view</code> attribute of the
+  <code>UIEvent</code> interface, during event propagation. There is no
+  way currently to enumerate all the views.</p>
+
+  <!-- XXX examples! -->
+
+
+
+
   <h2 class="no-num">Index</h2>
 
   <p><em>This section is non-normative.</em></p>




More information about the Commit-Watchers mailing list