[html5] r2739 - [e] (0) Filling in the rendering section: adding placeholders for future text.
whatwg at whatwg.org
whatwg at whatwg.org
Mon Feb 2 03:42:50 PST 2009
Author: ianh
Date: 2009-02-02 03:42:50 -0800 (Mon, 02 Feb 2009)
New Revision: 2739
Modified:
index
source
Log:
[e] (0) Filling in the rendering section: adding placeholders for future text.
Modified: index
===================================================================
--- index 2009-02-02 11:25:28 UTC (rev 2738)
+++ index 2009-02-02 11:42:50 UTC (rev 2739)
@@ -1042,13 +1042,15 @@
<ol>
<li><a href=#the-title-attribute-0><span class=secno>10.4.1 </span>The <code title=attr-title>title</code> attribute</a></li>
<li><a href=#form-controls-and-widgets><span class=secno>10.4.2 </span>Form controls and widgets</a></li>
- <li><a href=#the-marquee-element><span class=secno>10.4.3 </span>The <code>marquee</code> element</a></li>
- <li><a href=#the-hr-element-0><span class=secno>10.4.4 </span>The <code>hr</code> element</a></li>
- <li><a href=#frames><span class=secno>10.4.5 </span>Frames</a></ol></li>
- <li><a href=#other><span class=secno>10.5 </span>Other</a></li>
- <li><a href=#rendering-and-menus/toolbars><span class=secno>10.6 </span>Rendering and menus/toolbars</a>
- <ol>
- <li><a href="#the-'icon'-property"><span class=secno>10.6.1 </span>The 'icon' property</a></ol></ol></li>
+ <li><a href=#the-datagrid-element><span class=secno>10.4.3 </span>The <code>datagrid</code> element</a></li>
+ <li><a href=#rendering-and-menus/toolbars><span class=secno>10.4.4 </span>Rendering and menus/toolbars</a>
+ <ol>
+ <li><a href="#the-'icon'-property"><span class=secno>10.4.4.1 </span>The 'icon' property</a></ol></li>
+ <li><a href=#the-marquee-element><span class=secno>10.4.5 </span>The <code>marquee</code> element</a></li>
+ <li><a href=#the-hr-element-0><span class=secno>10.4.6 </span>The <code>hr</code> element</a></li>
+ <li><a href=#the-br-element-0><span class=secno>10.4.7 </span>The <code>br</code> element</a></li>
+ <li><a href=#frames><span class=secno>10.4.8 </span>Frames</a></ol></li>
+ <li><a href=#other><span class=secno>10.5 </span>Other</a></ol></li>
<li><a href=#obsolete-features><span class=secno>11 </span>Obsolete features</a>
<ol>
<li><a href=#self-contained-features-0><span class=secno>11.1 </span>Self-contained features</a>
@@ -55788,6 +55790,8 @@
li { display: list-item; }</pre>
+ <!-- XXX ruby, rt, rp -->
+
<!-- del, ins, and map are inline. -->
<p>For the purposes of the CSS table model, the <code><a href=#the-col-element>col</a></code>
@@ -55891,16 +55895,19 @@
:link { color: blue; }
:visited { color: purple; }
body { color: black; background: white; }
+mark { background: yellow; color: black; }
table { border-color: gray; }
thead, tbody, tfoot, tr { border-color: inherit; }</pre>
- <p>The <code><a href=#the-article-element>article</a></code>, <code><a href=#the-aside-element>aside</a></code>, <code><a href=#the-nav-element>nav</a></code>,
+ <hr><p>The <code><a href=#the-article-element>article</a></code>, <code><a href=#the-aside-element>aside</a></code>, <code><a href=#the-nav-element>nav</a></code>,
and <code><a href=#the-section-element>section</a></code> elements are expected to affect the styling
of <code><a href=#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements>h1</a></code> elements, based on the nesting depth. If <var title="">x</var> is a selector that matches elements that are either
<code><a href=#the-article-element>article</a></code>, <code><a href=#the-aside-element>aside</a></code>, <code><a href=#the-nav-element>nav</a></code>, or
<code><a href=#the-section-element>section</a></code> elements, then the following rules capture what
is expected:</p>
+ <!-- XXX this is better than http://damowmow.com/temp/sectioning.css
+ but it's still not optimal... -->
<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
<var title="">x</var> h1 { font-size: 1.05em; }
<var title="">x</var> <var title="">x</var> h1 { font-size: 1.17em; }
@@ -55908,8 +55915,11 @@
<var title="">x</var> <var title="">x</var> <var title="">x</var> <var title="">x</var> h1 { font-size: 0.83em; }
<var title="">x</var> <var title="">x</var> <var title="">x</var> <var title="">x</var> <var title="">x</var> h1 { font-size: 0.67em; }</pre>
+ <hr><p class=XXX>Need to define the content attributes of BODY in
+ terms of CSS or something.</p>
+
<h4 id=punctuation-and-decorations><span class=secno>10.3.6 </span>Punctuation and decorations</h4>
<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
@@ -56010,35 +56020,114 @@
<h4 id=form-controls-and-widgets><span class=secno>10.4.2 </span>Form controls and widgets</h4>
+ <p>User agents are expected to style form controls and widgets
+ exposed by <a href=#html-elements>HTML elements</a> in line with platform
+ conventions. However, to enable pages to be rendered in a somewhat
+ consistent manner across different platforms, this section describes
+ some characteristics that these elements are expected to share
+ regardless of the platform.</p>
+
+ <dl><dt><code><a href=#the-details-element>details</a></code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code><a href=#the-fieldset-element>fieldset</a></code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code><a href=#the-input-element>input</a></code> ...</dt> <!-- XXX types; size attribute -->
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code><a href=#the-meter-element>meter</a></code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code><a href=#the-progress-element>progress</a></code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <!-- XXX button, select, textarea, bb -->
+
+
+ </dl><p class=XXX>...</p>
+
+
+
+ <h4 id=the-datagrid-element><span class=secno>10.4.3 </span>The <code><a href=#datagrid>datagrid</a></code> element</h4>
+
<p class=XXX>...</p>
- <h4 id=the-marquee-element><span class=secno>10.4.3 </span>The <code><a href=#the-marquee-element-0>marquee</a></code> element</h4>
+ <h4 id=rendering-and-menus/toolbars><span class=secno>10.4.4 </span>Rendering and menus/toolbars</h4>
+ <h5 id="the-'icon'-property"><span class=secno>10.4.4.1 </span>The 'icon' property</h5>
+
+ <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.</p>
+
+
+
+ <h4 id=the-marquee-element><span class=secno>10.4.5 </span>The <code><a href=#the-marquee-element-0>marquee</a></code> element</h4>
+
<p class=XXX>...</p>
- <h4 id=the-hr-element-0><span class=secno>10.4.4 </span>The <code><a href=#the-hr-element>hr</a></code> element</h4>
+ <h4 id=the-hr-element-0><span class=secno>10.4.6 </span>The <code><a href=#the-hr-element>hr</a></code> element</h4>
<p class=XXX>...</p>
- <h4 id=frames><span class=secno>10.4.5 </span>Frames</h4>
+ <h4 id=the-br-element-0><span class=secno>10.4.7 </span>The <code><a href=#the-br-element>br</a></code> element</h4>
<p class=XXX>...</p>
+ <h4 id=frames><span class=secno>10.4.8 </span>Frames</h4>
+
+ <p class=XXX>...</p>
+
+
+
<h3 id=other><span class=secno>10.5 </span>Other</h3>
<!-- XXX
- section { }
- mark { }
- /* ... */
+ figure/legend
+ iframe, embed, object, applet, video, audio, canvas
Default UI
link: click
@@ -56175,24 +56264,8 @@
are case-insensitive, as well as saying which attribute values must
be compared case-insensitively.</p>
- <p class=XXX>Need to define the content attributes of BODY in
- terms of CSS or something.</p>
-
- <h3 id=rendering-and-menus/toolbars><span class=secno>10.6 </span>Rendering and menus/toolbars</h3>
-
- <h4 id="the-'icon'-property"><span class=secno>10.6.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.</p>
-
-
-
<h2 id=obsolete-features><span class=secno>11 </span>Obsolete features</h2>
<p>Authors and documents must not use the features listed in this
Modified: source
===================================================================
--- source 2009-02-02 11:25:28 UTC (rev 2738)
+++ source 2009-02-02 11:42:50 UTC (rev 2739)
@@ -61005,6 +61005,8 @@
li { display: list-item; }</pre>
+ <!-- XXX ruby, rt, rp -->
+
<!-- del, ins, and map are inline. -->
<p>For the purposes of the CSS table model, the <code>col</code>
@@ -61111,9 +61113,12 @@
:link { color: blue; }
:visited { color: purple; }
body { color: black; background: white; }
+mark { background: yellow; color: black; }
table { border-color: gray; }
thead, tbody, tfoot, tr { border-color: inherit; }</pre>
+ <hr>
+
<p>The <code>article</code>, <code>aside</code>, <code>nav</code>,
and <code>section</code> elements are expected to affect the styling
of <code>h1</code> elements, based on the nesting depth. If <var
@@ -61122,6 +61127,8 @@
<code>section</code> elements, then the following rules capture what
is expected:</p>
+ <!-- XXX this is better than http://damowmow.com/temp/sectioning.css
+ but it's still not optimal... -->
<pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
<var title="">x</var> h1 { font-size: 1.05em; }
<var title="">x</var> <var title="">x</var> h1 { font-size: 1.17em; }
@@ -61129,8 +61136,13 @@
<var title="">x</var> <var title="">x</var> <var title="">x</var> <var title="">x</var> h1 { font-size: 0.83em; }
<var title="">x</var> <var title="">x</var> <var title="">x</var> <var title="">x</var> <var title="">x</var> h1 { font-size: 0.67em; }</pre>
+ <hr>
+ <p class="XXX">Need to define the content attributes of BODY in
+ terms of CSS or something.</p>
+
+
<h4>Punctuation and decorations</h4>
<pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
@@ -61232,10 +61244,89 @@
<h4>Form controls and widgets</h4>
+ <p>User agents are expected to style form controls and widgets
+ exposed by <span>HTML elements</span> in line with platform
+ conventions. However, to enable pages to be rendered in a somewhat
+ consistent manner across different platforms, this section describes
+ some characteristics that these elements are expected to share
+ regardless of the platform.</p>
+
+ <dl>
+
+
+ <dt><code>details</code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code>fieldset</code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code>input</code> ...</dt> <!-- XXX types; size attribute -->
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code>meter</code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <dt><code>progress</code></dt>
+
+ <dd>
+
+ <p></p>
+
+ </dd>
+
+
+ <!-- XXX button, select, textarea, bb -->
+
+
+ </dl>
+
<p class="XXX">...</p>
+ <h4>The <code>datagrid</code> element</h4>
+
+ <p class="XXX">...</p>
+
+
+
+ <h4>Rendering and menus/toolbars</h4>
+
+ <h5>The 'icon' property</h5>
+
+ <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.</p>
+
+
+
<h4>The <code>marquee</code> element</h4>
<p class="XXX">...</p>
@@ -61248,6 +61339,12 @@
+ <h4>The <code>br</code> element</h4>
+
+ <p class="XXX">...</p>
+
+
+
<h4>Frames</h4>
<p class="XXX">...</p>
@@ -61258,9 +61355,8 @@
<!-- XXX
- section { }
- mark { }
- /* ... */
+ figure/legend
+ iframe, embed, object, applet, video, audio, canvas
Default UI
link: click
@@ -61397,24 +61493,8 @@
are case-insensitive, as well as saying which attribute values must
be compared case-insensitively.</p>
- <p class="XXX">Need to define the content attributes of BODY in
- terms of CSS or something.</p>
-
- <h3>Rendering and menus/toolbars</h3>
-
- <h4>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.</p>
-
-
-
<h2>Obsolete features</h2>
<p>Authors and documents must not use the features listed in this
More information about the Commit-Watchers
mailing list