- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 29 Nov 2008 21:59:36 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv20485
Modified Files:
Overview.html
Log Message:
Split the rendering and obsolete features sections from each other. (whatwg r2475)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1645
retrieving revision 1.1646
diff -u -d -r1.1645 -r1.1646
--- Overview.html 29 Nov 2008 21:48:30 -0000 1.1645
+++ Overview.html 29 Nov 2008 21:59:33 -0000 1.1646
@@ -903,24 +903,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>
@@ -43694,7 +43696,7 @@
> (character U+2082) and &sub3; (character U+2083). They
> would are the equivalent to ¹, ², and ³.
See also: http://www.w3.org/2003/entities/
- --></div><h2 id=rendering><span class=secno>9 </span>Rendering and user-agent behavior</h2><!-- XXX
+ --></div><h2 id=rendering><span class=secno>9 </span>Rendering</h2><!-- XXX
Rendering
@@ -43836,28 +43838,15 @@
creating a new view for the print media.<p class=XXX>Must define that in CSS, tag and attribute
names in HTML documents, and class names in quirks mode documents,
are case-insensitive, as well as saying which attribute values must
- be compared case-insensitively.<h3 id=rendering-and-the-dom><span class=secno>9.1 </span>Rendering and the DOM</h3><p class=XXX>This section is wrong. mediaMode will end up on
- Window, I think. All views implement Window.<p>Any object implement the <code>AbstractView</code> interface must
- also implement the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface.<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=#references>[CSS21]</a><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
+ be compared case-insensitively.<p class=XXX>Need to define the content attributes of BODY in
+ terms of CSS or something.<h3 id=rendering-and-menus-toolbars><span class=secno>9.1 </span>Rendering and menus/toolbars</h3><h4 id=the-icon-property><span class=secno>9.1.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
using the <code title=command-attribute>command</code> attribute,
but when the property computes to an actual image, it should use
- that image instead.<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><p class=XXX>Need to define the content attributes in terms
- of CSS or something.<pre class=idl>[XXX] interface <a href=#htmldocument>HTMLDocument</a> {
+ that image instead.<h2 id=obsolete-features><span class=secno>10 </span>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.<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>;
attribute DOMString <a href=#dom-document-linkcolor title=dom-document-linkColor>linkColor</a>;
@@ -43903,7 +43892,7 @@
attribute.<p>The <dfn id=dom-body-vlink title=dom-body-vLink><code>vLink</code></dfn> DOM
attribute of the <code><a href=#the-body-element>body</a></code> element must <a href=#reflect>reflect</a>
the element's <code title=attr-body-vlink>vlink</code> content
- attribute.<h4 id=the-applet-element><span class=secno>9.3.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
+ attribute.<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
is obsoleted so that all extension frameworks (Java, .NET, Flash,
etc) are handled in a consistent manner.<p id=sandboxPluginApplet>If the <a href=#sandboxed-plugins-browsing-context-flag>sandboxed plugins browsing
@@ -43916,17 +43905,17 @@
};</pre><p>The <dfn id=dom-document-applets title=dom-document-applets><code>applets</code></dfn>
attribute must return an <code><a href=#htmlcollection-0>HTMLCollection</a></code> rooted at the
<code>Document</code> node, whose filter matches only
- <code><a href=#the-applet-element>applet</a></code> elements.<h2 id=no><span class=secno>10 </span>Things that you can't do with this specification because
+ <code><a href=#the-applet-element>applet</a></code> elements.<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><p><em>This section is non-normative.</em><p>There are certain features that are not handled by this
specification because a client side markup language is not the right
level for them, or because the features exist in other languages
that can be integrated into this one. This section covers some of
- the more common requests.<h3 id=localization><span class=secno>10.1 </span>Localization</h3><p>If you wish to create localized versions of an HTML application,
+ the more common requests.<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
- use HTTP content negotiation to serve the appropriate language.</p><!-- <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><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><p>Embedding 3D imagery into XHTML documents is the domain of X3D,
- or technologies based on X3D that are namespace-aware.</p><!-- <p>XXX example here</p> --><h3 id=timers><span class=secno>10.4 </span>Timers</h3><p class=XXX>This section is expected to be moved to its own
+ use HTTP content negotiation to serve the appropriate language.</p><!-- <p>XXX example here</p> --><!--XXXSVG (remove next section)--><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>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><!-- <p>XXX example here</p> --><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
it into a semi-decent spec.<p>Objects that implement the <code><a href=#window>Window</a></code> interface must
also implement the <code><a href=#windowtimers>WindowTimers</a></code> interface:<pre class=idl>[NoInterfaceObject] interface <dfn id=windowtimers>WindowTimers</dfn> {
@@ -43976,7 +43965,23 @@
methods take one integer (the value returned by <code title=dom-windowtimers-setTimeout><a href=#dom-windowtimers-settimeout>setTimeout()</a></code> and <code title=dom-windowtimers-setInterval><a href=#dom-windowtimers-setinterval>setInterval()</a></code>
respectively) and must cancel the specified timeout. When called
with a value that does not correspond to an active timeout or
- interval, the methods must return without doing anything.<h2 class=no-num id=index>Index</h2><p><em>This section is non-normative.</em><p class=XXX>List of elements<p class=XXX>List of attributes<p class=XXX>List of interfaces<p class=XXX>List of events<h2 class=no-num id=references>References</h2><p class=XXX>This section will be written in a future draft.</p><!-- XXX check that #references is always for [RFC\1] --><h2 class=no-num id=acknowledgements>Acknowledgements</h2><!-- ACKS --><p>Thanks to Aankhen, Aaron Boodman, Aaron Leventhal, Adam Barth,
+ interval, the methods must return without doing anything.<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>Any object implement the <code>AbstractView</code> interface must
+ also implement the <code><a href=#mediamodeabstractview>MediaModeAbstractView</a></code> interface.<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=#references>[CSS21]</a><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 class=XXX>List of elements<p class=XXX>List of attributes<p class=XXX>List of interfaces<p class=XXX>List of events<h2 class=no-num id=references>References</h2><p class=XXX>This section will be written in a future draft.</p><!-- XXX check that #references is always for [RFC\1] --><h2 class=no-num id=acknowledgements>Acknowledgements</h2><!-- ACKS --><p>Thanks to Aankhen, Aaron Boodman, Aaron Leventhal, Adam Barth,
Adam Roben, Addison Phillips, Adele Peterson, Adrian Sutton,
Agustín Fernández, Ajai Tirumali, Alastair Campbell,
Alexey Feldgendler, Anders Carlsson, Andrew Gove, Andrew Sidwell,
Received on Saturday, 29 November 2008 21:59:49 UTC