Short URL: http://html5.org/r/2760
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 2760 | Filling in the rendering section: Fill in more sections -- br, tool bars, ruby... | 2009-02-05 09:50 |
Index: source
===================================================================
--- source (revision 2759)
+++ source (revision 2760)
@@ -13228,7 +13228,7 @@
not present.</p>
<div class="example">
- <p>If a site uses a consistent navigation toolbar on every page,
+ <p>If a site uses a consistent navigation tool bar on every page,
then the link that would normally link to the page itself could be
marked up using an <code>a</code> element:</p>
<pre><nav>
@@ -34541,24 +34541,8 @@
attribute must <span>reflect</span> the <code
title="attr-details-open">open</code> content attribute.</p>
- <p class="XXX">Rendering will be described in the Rendering
- section in due course. Basically CSS :open and :closed match the
- element, it's a block-level element by default, and when it matches
- :closed it renders as if it had an XBL binding attached to it whose
- template was just <code><template>▶<content
- includes="legend:first-child">Details</content></template></code>,
- and when it's :open it acts as if it had an XBL binding attached to
- it whose template was just <code><template>▼<content
- includes="legend:first-child">Details</content><content/></template></code>
- or some such.</p>
-<!--
-Example ideas:
-http://mail.gnome.org/archives/usability/2006-June/msg00015.html
--->
-
-
<div class="bad">
<h4 id="datagrid">The <dfn><code>datagrid</code></dfn> element</h4>
@@ -37292,21 +37276,18 @@
title="attr-contextmenu">contextmenu</code> content attribute.</p>
- <h5>Toolbars</h5>
+ <h5><dfn>Tool bars</dfn></h5>
- <p><dfn>Toolbars</dfn> are a kind of menu that is always visible.</p>
-
<p>When a <code>menu</code> element has a <code
- title="attr-menu-type">type</code> attribute with the value <code
- title="">toolbar</code>, then the user agent must <span
- title="building menus and tool bars">build</span> the menu for that
- <code>menu</code> element and <span
- title="render-toolbar">render</span><!-- XXX xref --> it in the
- document in a position appropriate for that <code>menu</code>
- element.</p>
+ title="attr-menu-type">type</code> attribute in the <span
+ title="tool bar state">tool bar</span> state, then the user agent
+ must <span title="building menus and tool bars">build</span> the
+ menu for that <code>menu</code> element, and use the result in the
+ rendering.</p>
<p>The user agent must reflect changes made to the
- <code>menu</code>'s DOM immediately in the UI.</p>
+ <code>menu</code>'s DOM, by immediately <span title="building menus
+ and tool bars">rebuilding</span> the menu.</p>
@@ -61314,7 +61295,7 @@
address, article, aside, blockquote, body, center, dd, dialog, dir,
div, dl, dt, figure, footer, form, h1, h2, h3, h4, h5, h6, header, hr,
html, layer, legend, listing, menu, multicol, nav, ol, p, plaintext,
-pre, section, ul, xmp { display: block; }
+pre, rp, section, ul, xmp { display: block; }
table { display: table; }
caption { display: table-caption; }
@@ -61326,8 +61307,12 @@
tr { display: table-row; }
td, th { display: table-cell; }
-li { display: list-item; }</pre>
+li { display: list-item; }
+ruby { display: ruby; }
+rt { display: ruby-text; }
+</pre>
+
<!-- del, ins, and map are inline. -->
<p>For the purposes of the CSS table model, the <code>col</code>
@@ -61350,7 +61335,16 @@
<i>special knowledge</i> regarding cells spanning rows and
columns.</p>
+ <p>For the purposes of the CSS ruby model, runs of descendants of
+ <code>ruby</code> elements that are not <code>rt</code> or
+ <code>rp</code> elements are expected to be wrapped in anonymous
+ boxes whose 'display' property has the value 'ruby-base'.</p>
+ <p>User agents that do not support correct ruby rendering are
+ expected to render parentheses around the text of <code>rt</code>
+ elements in the absence of <code>rp</code> elements.</p>
+
+
<h4>Margins and padding</h4>
<pre class="css">@namespace url(http://www.w3.org/1999/xhtml);
@@ -62069,6 +62063,10 @@
td[nowrap], th[nowrap] { white-space: nowrap; }
pre[wrap] { white-space: pre-wrap; }
+br[clear=left] { clear: left; }
+br[clear=right] { clear: right; }
+br[clear=all], br[clear=both] { clear: both; }
+
ol[type=1], li[type=1] { list-style-type: decimal; }
ol[type=a], li[type=a] { list-style-type: lower-alpha; }
ol[type=A], li[type=A] { list-style-type: upper-alpha; }
@@ -62176,6 +62174,10 @@
to use the ordinal value of the <code>li</code> element to render
the counter in the list item marker.</p>
+ <p>The <code>br</code> element is expected to render as if its
+ contents were a single U+000A LINE FEED (LF) character and its
+ 'white-space' property was 'pre'.</p>
+
<p>The <code>table</code> element's <code
title="attr-table-border">border</code> attribute <span title="maps
to the pixel length property">maps to the pixel length
@@ -62756,70 +62758,75 @@
- <h4>Ruby annotations</h4>
+ <h4>Tool bars</h4>
- <p class="XXX">...</p>
+ <p>When a <code>menu</code> element's <code
+ title="attr-menu-type">type</code> attribute is in the <span
+ title="tool bar state">tool bar</span> state, the element is
+ expected to be treated as a replaced element with a height about two
+ lines high and a width derived from the contents of the element.</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.
- -->
+ <p>The element is expected to have, by default, the appearance of a
+ tool bar on the user agent's platform. It is expected to contain the
+ menu that is <span title="building menus and tool bars">built</span>
+ from the element.</p>
+ <p class="example XXX">...example with screenshot...</p>
- <h4>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>bb</code> element</h4>
- <p class="XXX">...</p>
+ <p>When the <code>bb</code> element <span>represents</span> a
+ browser button, it is expected to render as a replaced element
+ consisting of a regular one-line-high button, with a width based on
+ the text in the button, which is itself based on its <code
+ title="attr-bb-type">type</code> attribute in a user-agent-defined
+ (and probably locale-specific) fashion. When it does not, it is
+ expected to render as per the regular CSS rules.</p>
- <h4>The <code>br</code> element</h4>
-
- <p class="XXX">...</p>
- <!-- clear="left|right|all|both" -->
-
-
-
<h4>The <code>button</code> element</h4>
- <p class="XXX">...</p>
+ <p>The <code>button</code> element is expected to render as a
+ replaced element whose contents are styled as per the regular CSS
+ rules. Its intrinisic dimensions are the shrink-wrap dimensions of
+ its contents.</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
+ <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>
+ concert with CSS. Implementation experience is desired before this
+ section is filled in.</p>
<h4>The <code>details</code> element</h4>
- <p class="XXX">...</p>
+ <p class="XXX">The <code>details</code> element, ...</p>
+ <p class="XXX">Basically CSS :open and :closed match the
+ element, it's a block-level element by default, and when it matches
+ :closed it renders as if it had an XBL binding attached to it whose
+ template was just <code><template>▶<content
+ includes="legend:first-child">Details</content></template></code>,
+ and when it's :open it acts as if it had an XBL binding attached to
+ it whose template was just <code><template>▼<content
+ includes="legend:first-child">Details</content><content/></template></code>
+ or some such.</p>
+<!--
+Example ideas:
+http://mail.gnome.org/archives/usability/2006-June/msg00015.html
+-->
+
+
<h4>The <code>fieldset</code> element</h4>
<p class="XXX">...</p>