[html5] r2743 - [e] (0) Filling in the rendering section: more placeholder sections.
whatwg at whatwg.org
whatwg at whatwg.org
Mon Feb 2 22:10:30 PST 2009
Author: ianh
Date: 2009-02-02 22:10:29 -0800 (Mon, 02 Feb 2009)
New Revision: 2743
Modified:
index
source
Log:
[e] (0) Filling in the rendering section: more placeholder sections.
Modified: index
===================================================================
--- index 2009-02-03 02:43:54 UTC (rev 2742)
+++ index 2009-02-03 06:10:29 UTC (rev 2743)
@@ -1040,20 +1040,35 @@
<li><a href=#resetting-rules-for-inherited-properties><span class=secno>10.3.7 </span>Resetting rules for inherited properties</a></ol></li>
<li><a href=#self-contained-features><span class=secno>10.4 </span>Self-contained features</a>
<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-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>
+ <li><a href=#the-bb-element-0><span class=secno>10.4.1 </span>The <code>bb</code> element</a></li>
+ <li><a href=#the-br-element-0><span class=secno>10.4.2 </span>The <code>br</code> element</a></li>
+ <li><a href=#the-button-element-0><span class=secno>10.4.3 </span>The <code>button</code> element</a></li>
+ <li><a href=#the-datagrid-element><span class=secno>10.4.4 </span>The <code>datagrid</code> element</a></li>
+ <li><a href=#the-details-element-0><span class=secno>10.4.5 </span>The <code>details</code> element</a></li>
+ <li><a href=#the-fieldset-element-0><span class=secno>10.4.6 </span>The <code>fieldset</code> element</a></li>
+ <li><a href=#the-figure-element-0><span class=secno>10.4.7 </span>The <code>figure</code> element</a></li>
+ <li><a href=#the-hr-element-0><span class=secno>10.4.8 </span>The <code>hr</code> element</a></li>
+ <li><a href=#the-input-element-as-a-text-entry-widget><span class=secno>10.4.9 </span>The <code>input</code> element as a text entry widget</a></li>
+ <li><a href=#the-input-element-as-date-widgets><span class=secno>10.4.10 </span>The <code>input</code> element as date widgets</a></li>
+ <li><a href=#the-input-element-as-a-range-control><span class=secno>10.4.11 </span>The <code>input</code> element as a range control</a></li>
+ <li><a href=#the-input-element-as-a-color-well><span class=secno>10.4.12 </span>The <code>input</code> element as a color well</a></li>
+ <li><a href=#the-input-element-as-a-check-box-widget><span class=secno>10.4.13 </span>The <code>input</code> element as a check box widget</a></li>
+ <li><a href=#the-input-element-as-a-radio-button-widget><span class=secno>10.4.14 </span>The <code>input</code> element as a radio button widget</a></li>
+ <li><a href=#the-input-element-as-a-file-upload-control><span class=secno>10.4.15 </span>The <code>input</code> element as a file upload control</a></li>
+ <li><a href=#the-input-element-as-a-button><span class=secno>10.4.16 </span>The <code>input</code> element as a button</a></li>
+ <li><a href=#the-marquee-element><span class=secno>10.4.17 </span>The <code>marquee</code> element</a></li>
+ <li><a href=#the-meter-element-0><span class=secno>10.4.18 </span>The <code>meter</code> element</a></li>
+ <li><a href=#the-progress-element-0><span class=secno>10.4.19 </span>The <code>progress</code> element</a></li>
+ <li><a href=#the-select-element-0><span class=secno>10.4.20 </span>The <code>select</code> element</a></li>
+ <li><a href=#the-textarea-element-0><span class=secno>10.4.21 </span>The <code>textarea</code> element</a></li>
+ <li><a href=#embedded-content-1><span class=secno>10.4.22 </span>Embedded content</a></li>
+ <li><a href=#fragment-identifiers><span class=secno>10.4.23 </span>Fragment identifiers</a></li>
+ <li><a href=#frames><span class=secno>10.4.24 </span>Frames</a></li>
+ <li><a href=#rendering-and-menus/toolbars><span class=secno>10.4.25 </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=#the-figure-element-0><span class=secno>10.4.8 </span>The <code>figure</code> element</a></li>
- <li><a href=#ruby-annotations><span class=secno>10.4.9 </span>Ruby annotations</a></li>
- <li><a href=#frames><span class=secno>10.4.10 </span>Frames</a></li>
- <li><a href=#embedded-content-1><span class=secno>10.4.11 </span>Embedded content</a></li>
- <li><a href=#fragment-identifiers><span class=secno>10.4.12 </span>Fragment identifiers</a></ol></li>
+ <li><a href="#the-'icon'-property"><span class=secno>10.4.25.1 </span>The 'icon' property</a></ol></li>
+ <li><a href=#ruby-annotations><span class=secno>10.4.26 </span>Ruby annotations</a></li>
+ <li><a href=#the-title-attribute-0><span class=secno>10.4.27 </span>The <code title=attr-title>title</code> attribute</a></ol></li>
<li><a href=#interactive-media><span class=secno>10.5 </span>Interactive media</a>
<ol>
<li><a href=#links-0><span class=secno>10.5.1 </span>Links</a></li>
@@ -15125,7 +15140,7 @@
the document.</li>
<li><p>If the <code><a href=#the-img-element>img</a></code> element did not end up associated
- with a heading in theoutline, or if there are any other images
+ with a heading in the outline, or if there are any other images
that are lacking an <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code>
attribute and that are associated with the same heading in the
outline as the <code><a href=#the-img-element>img</a></code> element in question, then there
@@ -55883,7 +55898,9 @@
tables within them, as their descendants had their horizontal
margins set to 'auto'.</p>
+ <!-- XXX <div/h1-h6/p align="left|right|center/middle|justify"> -->
+
<h4 id=fonts-and-colors><span class=secno>10.3.5 </span>Fonts and colors</h4>
<pre class=css>@namespace url(http://www.w3.org/1999/xhtml);
@@ -55927,6 +55944,7 @@
<hr><p class=XXX>Need to define the content attributes of BODY in
terms of CSS or something.</p>
+xxxxx
<h4 id=punctuation-and-decorations><span class=secno>10.3.6 </span>Punctuation and decorations</h4>
@@ -55986,8 +56004,10 @@
for the locales and languages understood by the user are expected to
be present.</p>
+ <!-- XXX <li> type, value -->
+
<h4 id=resetting-rules-for-inherited-properties><span class=secno>10.3.7 </span>Resetting rules for inherited properties</h4>
<p>The following rules are also expected to be in play, resetting
@@ -56014,155 +56034,146 @@
<h3 id=self-contained-features><span class=secno>10.4 </span>Self-contained features</h3>
- <h4 id=the-title-attribute-0><span class=secno>10.4.1 </span>The <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute</h4>
- <p>Given an element (e.g. the element designated by the mouse
- cursor), if the element, or one of its ancestors, has a <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute, and the nearest such
- attribute has a value that is not the empty string, it is expected
- that the user agent will expose the contents of that attribute as a
- tooltip.</p>
+ <h4 id=the-bb-element-0><span class=secno>10.4.1 </span>The <code><a href=#the-bb-element>bb</a></code> element</h4>
- <p>U+000A LINE FEED (LF) characters are expected to cause line
- breaks in the tooltip.</p>
+ <p class=XXX>...</p>
- <h4 id=form-controls-and-widgets><span class=secno>10.4.2 </span>Form controls and widgets</h4>
+ <h4 id=the-br-element-0><span class=secno>10.4.2 </span>The <code><a href=#the-br-element>br</a></code> element</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>
+ <p class=XXX>...</p>
+ <!-- clear="left|right|all|both" -->
- <dl><dt><code><a href=#the-details-element>details</a></code></dt>
- <dd>
- <p></p>
+ <h4 id=the-button-element-0><span class=secno>10.4.3 </span>The <code><a href=#the-button-element>button</a></code> element</h4>
- </dd>
+ <p class=XXX>...</p>
- <dt><code><a href=#the-fieldset-element>fieldset</a></code></dt>
- <dd>
+ <h4 id=the-datagrid-element><span class=secno>10.4.4 </span>The <code><a href=#datagrid>datagrid</a></code> element</h4>
- <p></p>
+ <p class=XXX>This section will probably include details on
+ how to render DATAGRID (including <span id=datagridPseudos>its
+ pseudo-elements</span>), drag-and-drop, etc, in a visual medium, in
+ concert with CSS.</p>
- </dd>
- <dt><code><a href=#the-input-element>input</a></code> ...</dt> <!-- XXX types; size attribute -->
+ <h4 id=the-details-element-0><span class=secno>10.4.5 </span>The <code><a href=#the-details-element>details</a></code> element</h4>
- <dd>
+ <p class=XXX>...</p>
- <p></p>
- </dd>
+ <h4 id=the-fieldset-element-0><span class=secno>10.4.6 </span>The <code><a href=#the-fieldset-element>fieldset</a></code> element</h4>
- <dt><code><a href=#the-meter-element>meter</a></code></dt>
+ <p class=XXX>...</p>
+ <!-- XXX <legend align="left|right|center|bottom|top"> -->
- <dd>
- <p></p>
- </dd>
+ <h4 id=the-figure-element-0><span class=secno>10.4.7 </span>The <code><a href=#the-figure-element>figure</a></code> element</h4>
+ <p class=XXX>...</p>
- <dt><code><a href=#the-progress-element>progress</a></code></dt>
- <dd>
- <p></p>
+ <h4 id=the-hr-element-0><span class=secno>10.4.8 </span>The <code><a href=#the-hr-element>hr</a></code> element</h4>
- </dd>
+ <p class=XXX>...</p>
- <!-- XXX button, select, textarea, bb -->
+ <h4 id=the-input-element-as-a-text-entry-widget><span class=secno>10.4.9 </span>The <code><a href=#the-input-element>input</a></code> element as a text entry widget</h4>
- </dl><p class=XXX>...</p>
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#text-state-and-search-state title=attr-input-type-text>Text</a>, <a href=#text-state-and-search-state title=attr-input-type-search>Search</a>, <a href=#url-state title=attr-input-type-url>URL</a>, <a href=#e-mail-state title=attr-input-type-email>E-mail</a>, <a href=#password-state title=attr-input-type-password>Password</a>, or <a href=#number-state title=attr-input-type-number>Number</a> state, ...</p>
- <h4 id=the-datagrid-element><span class=secno>10.4.3 </span>The <code><a href=#datagrid>datagrid</a></code> element</h4>
+ <h4 id=the-input-element-as-date-widgets><span class=secno>10.4.10 </span>The <code><a href=#the-input-element>input</a></code> element as date widgets</h4>
- <p class=XXX>This section will probably include details on
- how to render DATAGRID (including <span id=datagridPseudos>its
- pseudo-elements</span>), drag-and-drop, etc, in a visual medium, in
- concert with CSS.</p>
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#date-and-time-state title=attr-input-type-datetime>Date and Time</a>, <a href=#date-state title=attr-input-type-date>Date</a>, <a href=#month-state title=attr-input-type-month>Month</a>, <a href=#week-state title=attr-input-type-week>Week</a>, <a href=#time-state title=attr-input-type-time>Time</a>, or <a href=#local-date-and-time-state title=attr-input-type-datetime-local>Local Date and Time</a>
+ state, ...</p>
+ <h4 id=the-input-element-as-a-range-control><span class=secno>10.4.11 </span>The <code><a href=#the-input-element>input</a></code> element as a range control</h4>
- <h4 id=rendering-and-menus/toolbars><span class=secno>10.4.4 </span>Rendering and menus/toolbars</h4>
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#range-state title=attr-input-type-range>Range</a> state, ...</p>
- <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-input-element-as-a-color-well><span class=secno>10.4.12 </span>The <code><a href=#the-input-element>input</a></code> element as a color well</h4>
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#color-state title=attr-input-type-color>Color</a> state, ...</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-input-element-as-a-check-box-widget><span class=secno>10.4.13 </span>The <code><a href=#the-input-element>input</a></code> element as a check box widget</h4>
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#checkbox-state title=attr-input-type-checkbox>Checkbox</a> state, ...</p>
- <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>
+
+ <h4 id=the-input-element-as-a-radio-button-widget><span class=secno>10.4.14 </span>The <code><a href=#the-input-element>input</a></code> element as a radio button widget</h4>
+
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#radio-button-state title=attr-input-type-radio>Radio Button</a> state, ...</p>
+
+
+
+ <h4 id=the-input-element-as-a-file-upload-control><span class=secno>10.4.15 </span>The <code><a href=#the-input-element>input</a></code> element as a file upload control</h4>
+
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#file-upload-state title=attr-input-type-file>File Upload</a> state, ...</p>
+
+
+
+ <h4 id=the-input-element-as-a-button><span class=secno>10.4.16 </span>The <code><a href=#the-input-element>input</a></code> element as a button</h4>
+
+ <p class=XXX>When an <code><a href=#the-input-element>input</a></code> element's <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#submit-button-state title=attr-input-type-submit>Submit Button</a> <a href=#reset-button-state title=attr-input-type-reset>Reset Button</a>, or <a href=#button-state title=attr-input-type-button>Button</a> state, ...</p>
+
+
+
+ <h4 id=the-marquee-element><span class=secno>10.4.17 </span>The <code><a href=#the-marquee-element-0>marquee</a></code> element</h4>
+
<p class=XXX>...</p>
+ <!-- XXX attributes: height/width; direction is case insensitive; bgcolor; hspace/vspace -->
- <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>
+ <h4 id=the-meter-element-0><span class=secno>10.4.18 </span>The <code><a href=#the-meter-element>meter</a></code> element</h4>
<p class=XXX>...</p>
- <h4 id=the-figure-element-0><span class=secno>10.4.8 </span>The <code><a href=#the-figure-element>figure</a></code> element</h4>
+ <h4 id=the-progress-element-0><span class=secno>10.4.19 </span>The <code><a href=#the-progress-element>progress</a></code> element</h4>
<p class=XXX>...</p>
- <h4 id=ruby-annotations><span class=secno>10.4.9 </span>Ruby annotations</h4>
+ <h4 id=the-select-element-0><span class=secno>10.4.20 </span>The <code><a href=#the-select-element>select</a></code> element</h4>
<p class=XXX>...</p>
- <!-- XXX ruby, rt, rp
- > * note on rt rendering
- >
- > Since there are a number of documents with ruby but without rp, when you
- > write the rendering section, please include an advice for user agents
- > that do not support "correct" ruby rendering to render something like
- > "(" and ")" before and after ruby text (using, e.g., CSS ::before and
- > ::after) even when there are no rp elements. Otherwise, reading Web
- > pages without rp is very annoying.
- -->
+ <h4 id=the-textarea-element-0><span class=secno>10.4.21 </span>The <code><a href=#the-textarea-element>textarea</a></code> element</h4>
- <h4 id=frames><span class=secno>10.4.10 </span>Frames</h4>
-
<p class=XXX>...</p>
- <h4 id=embedded-content-1><span class=secno>10.4.11 </span>Embedded content</h4>
+ <h4 id=embedded-content-1><span class=secno>10.4.22 </span>Embedded content</h4>
<p class=XXX>...</p>
<!-- img, iframe, embed, object, applet, video, audio, canvas -->
+ <!-- <code>input</code> elements whose <code title="attr-input-type">type</code> attribute is in the <span title="attr-input-type-image">Image Button</span> state -->
<!--
img - how to handle alt text, img in link (no border)... Define
@@ -56174,9 +56185,8 @@
of embedded content</dfn></p>
+ <h4 id=fragment-identifiers><span class=secno>10.4.23 </span>Fragment identifiers</h4>
- <h4 id=fragment-identifiers><span class=secno>10.4.12 </span>Fragment identifiers</h4>
-
<p class=XXX>(need to remove "must" and reword) CSS UAs in visual
media must, when scrolling a page to a fragment identifier, align
the top of the viewport with the target element's top border
@@ -56184,6 +56194,57 @@
required to? -->
+
+ <h4 id=frames><span class=secno>10.4.24 </span>Frames</h4>
+
+ <p class=XXX>...</p>
+
+
+
+ <h4 id=rendering-and-menus/toolbars><span class=secno>10.4.25 </span>Rendering and menus/toolbars</h4>
+
+ <h5 id="the-'icon'-property"><span class=secno>10.4.25.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=ruby-annotations><span class=secno>10.4.26 </span>Ruby annotations</h4>
+
+ <p class=XXX>...</p>
+
+ <!-- XXX ruby, rt, rp
+ > * note on rt rendering
+ >
+ > Since there are a number of documents with ruby but without rp, when you
+ > write the rendering section, please include an advice for user agents
+ > that do not support "correct" ruby rendering to render something like
+ > "(" and ")" before and after ruby text (using, e.g., CSS ::before and
+ > ::after) even when there are no rp elements. Otherwise, reading Web
+ > pages without rp is very annoying.
+ -->
+
+
+
+ <h4 id=the-title-attribute-0><span class=secno>10.4.27 </span>The <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute</h4>
+
+ <p>Given an element (e.g. the element designated by the mouse
+ cursor), if the element, or one of its ancestors, has a <code title=attr-title><a href=#the-title-attribute>title</a></code> attribute, and the nearest such
+ attribute has a value that is not the empty string, it is expected
+ that the user agent will expose the contents of that attribute as a
+ tooltip.</p>
+
+ <p>U+000A LINE FEED (LF) characters are expected to cause line
+ breaks in the tooltip.</p>
+
+
+
+
<h3 id=interactive-media><span class=secno>10.5 </span>Interactive media</h3>
<h4 id=links-0><span class=secno>10.5.1 </span>Links</h4>
Modified: source
===================================================================
--- source 2009-02-03 02:43:54 UTC (rev 2742)
+++ source 2009-02-03 06:10:29 UTC (rev 2743)
@@ -16077,7 +16077,7 @@
the document.</p></li>
<li><p>If the <code>img</code> element did not end up associated
- with a heading in theoutline, or if there are any other images
+ with a heading in the outline, or if there are any other images
that are lacking an <code title="attr-img-alt">alt</code>
attribute and that are associated with the same heading in the
outline as the <code>img</code> element in question, then there
@@ -61091,7 +61091,9 @@
tables within them, as their descendants had their horizontal
margins set to 'auto'.</p>
+ <!-- XXX <div/h1-h6/p align="left|right|center/middle|justify"> -->
+
<h4>Fonts and colors</h4>
<pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
@@ -61140,6 +61142,7 @@
<p class="XXX">Need to define the content attributes of BODY in
terms of CSS or something.</p>
+xxxxx
<h4>Punctuation and decorations</h4>
@@ -61199,8 +61202,10 @@
for the locales and languages understood by the user are expected to
be present.</p>
+ <!-- XXX <li> type, value -->
+
<h4>Resetting rules for inherited properties</h4>
<p>The following rules are also expected to be in play, resetting
@@ -61227,152 +61232,164 @@
<h3>Self-contained features</h3>
- <h4>The <code title="attr-title">title</code> attribute</h4>
- <p>Given an element (e.g. the element designated by the mouse
- cursor), if the element, or one of its ancestors, has a <code
- title="attr-title">title</code> attribute, and the nearest such
- attribute has a value that is not the empty string, it is expected
- that the user agent will expose the contents of that attribute as a
- tooltip.</p>
+ <h4>The <code>bb</code> element</h4>
- <p>U+000A LINE FEED (LF) characters are expected to cause line
- breaks in the tooltip.</p>
+ <p class="XXX">...</p>
- <h4>Form controls and widgets</h4>
+ <h4>The <code>br</code> element</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>
+ <p class="XXX">...</p>
+ <!-- clear="left|right|all|both" -->
- <dl>
- <dt><code>details</code></dt>
+ <h4>The <code>button</code> element</h4>
- <dd>
+ <p class="XXX">...</p>
- <p></p>
- </dd>
+ <h4>The <code>datagrid</code> element</h4>
- <dt><code>fieldset</code></dt>
+ <p class="XXX">This section will probably include details on
+ how to render DATAGRID (including <span id="datagridPseudos">its
+ pseudo-elements</span>), drag-and-drop, etc, in a visual medium, in
+ concert with CSS.</p>
- <dd>
- <p></p>
- </dd>
+ <h4>The <code>details</code> element</h4>
+ <p class="XXX">...</p>
- <dt><code>input</code> ...</dt> <!-- XXX types; size attribute -->
- <dd>
- <p></p>
+ <h4>The <code>fieldset</code> element</h4>
- </dd>
+ <p class="XXX">...</p>
+ <!-- XXX <legend align="left|right|center|bottom|top"> -->
- <dt><code>meter</code></dt>
- <dd>
+ <h4>The <code>figure</code> element</h4>
- <p></p>
+ <p class="XXX">...</p>
- </dd>
- <dt><code>progress</code></dt>
+ <h4>The <code>hr</code> element</h4>
- <dd>
+ <p class="XXX">...</p>
- <p></p>
- </dd>
+ <h4>The <code>input</code> element as a text entry widget</h4>
- <!-- XXX button, select, textarea, bb -->
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-text">Text</span>, <span
+ title="attr-input-type-search">Search</span>, <span
+ title="attr-input-type-url">URL</span>, <span
+ title="attr-input-type-email">E-mail</span>, <span
+ title="attr-input-type-password">Password</span>, or <span
+ title="attr-input-type-number">Number</span> state, ...</p>
- </dl>
- <p class="XXX">...</p>
+ <h4>The <code>input</code> element as date widgets</h4>
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-datetime">Date and Time</span>, <span
+ title="attr-input-type-date">Date</span>, <span
+ title="attr-input-type-month">Month</span>, <span
+ title="attr-input-type-week">Week</span>, <span
+ title="attr-input-type-time">Time</span>, or <span
+ title="attr-input-type-datetime-local">Local Date and Time</span>
+ state, ...</p>
- <h4>The <code>datagrid</code> element</h4>
- <p class="XXX">This section will probably include details on
- how to render DATAGRID (including <span id="datagridPseudos">its
- pseudo-elements</span>), drag-and-drop, etc, in a visual medium, in
- concert with CSS.</p>
+ <h4>The <code>input</code> element as a range control</h4>
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-range">Range</span> state, ...</p>
- <h4>Rendering and menus/toolbars</h4>
+ <h4>The <code>input</code> element as a color well</h4>
- <h5>The 'icon' property</h5>
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-color">Color</span> state, ...</p>
- <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>input</code> element as a check box widget</h4>
- <h4>The <code>marquee</code> element</h4>
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-checkbox">Checkbox</span> state, ...</p>
- <p class="XXX">...</p>
+ <h4>The <code>input</code> element as a radio button widget</h4>
- <h4>The <code>hr</code> element</h4>
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-radio">Radio Button</span> state, ...</p>
+
+
+ <h4>The <code>input</code> element as a file upload control</h4>
+
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-file">File Upload</span> state, ...</p>
+
+
+
+ <h4>The <code>input</code> element as a button</h4>
+
+ <p class="XXX">When an <code>input</code> element's <code
+ title="attr-input-type">type</code> attribute is in the <span
+ title="attr-input-type-submit">Submit Button</span> <span
+ title="attr-input-type-reset">Reset Button</span>, or <span
+ title="attr-input-type-button">Button</span> state, ...</p>
+
+
+
+ <h4>The <code>marquee</code> element</h4>
+
<p class="XXX">...</p>
+ <!-- XXX attributes: height/width; direction is case insensitive; bgcolor; hspace/vspace -->
- <h4>The <code>br</code> element</h4>
+ <h4>The <code>meter</code> element</h4>
<p class="XXX">...</p>
- <h4>The <code>figure</code> element</h4>
+ <h4>The <code>progress</code> element</h4>
<p class="XXX">...</p>
- <h4>Ruby annotations</h4>
+ <h4>The <code>select</code> element</h4>
<p class="XXX">...</p>
- <!-- XXX ruby, rt, rp
- > * note on rt rendering
- >
- > Since there are a number of documents with ruby but without rp, when you
- > write the rendering section, please include an advice for user agents
- > that do not support "correct" ruby rendering to render something like
- > "(" and ")" before and after ruby text (using, e.g., CSS ::before and
- > ::after) even when there are no rp elements. Otherwise, reading Web
- > pages without rp is very annoying.
- -->
+ <h4>The <code>textarea</code> element</h4>
- <h4>Frames</h4>
-
<p class="XXX">...</p>
@@ -61382,6 +61399,7 @@
<p class="XXX">...</p>
<!-- img, iframe, embed, object, applet, video, audio, canvas -->
+ <!-- <code>input</code> elements whose <code title="attr-input-type">type</code> attribute is in the <span title="attr-input-type-image">Image Button</span> state -->
<!--
img - how to handle alt text, img in link (no border)... Define
@@ -61393,7 +61411,6 @@
of embedded content</dfn></p>
-
<h4>Fragment identifiers</h4>
<p class="XXX">(need to remove "must" and reword) CSS UAs in visual
@@ -61403,6 +61420,58 @@
required to? -->
+
+ <h4>Frames</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>Ruby annotations</h4>
+
+ <p class="XXX">...</p>
+
+ <!-- XXX ruby, rt, rp
+ > * note on rt rendering
+ >
+ > Since there are a number of documents with ruby but without rp, when you
+ > write the rendering section, please include an advice for user agents
+ > that do not support "correct" ruby rendering to render something like
+ > "(" and ")" before and after ruby text (using, e.g., CSS ::before and
+ > ::after) even when there are no rp elements. Otherwise, reading Web
+ > pages without rp is very annoying.
+ -->
+
+
+
+ <h4>The <code title="attr-title">title</code> attribute</h4>
+
+ <p>Given an element (e.g. the element designated by the mouse
+ cursor), if the element, or one of its ancestors, has a <code
+ title="attr-title">title</code> attribute, and the nearest such
+ attribute has a value that is not the empty string, it is expected
+ that the user agent will expose the contents of that attribute as a
+ tooltip.</p>
+
+ <p>U+000A LINE FEED (LF) characters are expected to cause line
+ breaks in the tooltip.</p>
+
+
+
+
<h3>Interactive media</h3>
<h4>Links</h4>
More information about the Commit-Watchers
mailing list