[html5] r1511 - /
whatwg at whatwg.org
whatwg at whatwg.org
Tue Apr 29 05:23:29 PDT 2008
Author: ianh
Date: 2008-04-29 05:23:28 -0700 (Tue, 29 Apr 2008)
New Revision: 1511
Modified:
index
source
Log:
[] (0) <font> is gone; style='' is global.
Modified: index
===================================================================
--- index 2008-04-29 11:14:21 UTC (rev 1510)
+++ index 2008-04-29 12:23:28 UTC (rev 1511)
@@ -379,7 +379,10 @@
<li><a href="#the-irrelevant"><span class=secno>3.4.6 </span>The
<code>irrelevant</code> attribute</a>
- <li><a href="#embedding"><span class=secno>3.4.7 </span>Embedding
+ <li><a href="#the-style"><span class=secno>3.4.7 </span>The
+ <code>style</code> attribute</a>
+
+ <li><a href="#embedding"><span class=secno>3.4.8 </span>Embedding
custom non-visible data</a>
</ul>
@@ -439,7 +442,7 @@
the document's character encoding</a>
</ul>
- <li><a href="#the-style"><span class=secno>3.7.6 </span>The
+ <li><a href="#the-style0"><span class=secno>3.7.6 </span>The
<code>style</code> element</a>
<li><a href="#styling"><span class=secno>3.7.7 </span>Styling</a>
@@ -1758,57 +1761,44 @@
<li><a href="#entities"><span class=secno>8.6 </span>Entities</a>
</ul>
- <li><a href="#wysiwyg"><span class=secno>9. </span>WYSIWYG editors</a>
- <ul class=toc>
- <li><a href="#presentational"><span class=secno>9.1
- </span>Presentational markup</a>
- <ul class=toc>
- <li><a href="#wysiwyg0"><span class=secno>9.1.1 </span>WYSIWYG
- signature</a>
-
- <li><a href="#the-font"><span class=secno>9.1.2 </span>The
- <code>font</code> element</a>
- </ul>
- </ul>
-
- <li><a href="#rendering"><span class=secno>10. </span>Rendering and
+ <li><a href="#rendering"><span class=secno>9. </span>Rendering and
user-agent behavior</a>
<ul class=toc>
- <li><a href="#rendering0"><span class=secno>10.1 </span>Rendering and
- the DOM</a>
+ <li><a href="#rendering0"><span class=secno>9.1 </span>Rendering and the
+ DOM</a>
- <li><a href="#rendering1"><span class=secno>10.2 </span>Rendering and
+ <li><a href="#rendering1"><span class=secno>9.2 </span>Rendering and
menus/toolbars</a>
<ul class=toc>
- <li><a href="#the-icon"><span class=secno>10.2.1 </span>The 'icon'
+ <li><a href="#the-icon"><span class=secno>9.2.1 </span>The 'icon'
property</a>
</ul>
- <li><a href="#obsolete"><span class=secno>10.3 </span>Obsolete elements,
+ <li><a href="#obsolete"><span class=secno>9.3 </span>Obsolete elements,
attributes, and APIs</a>
<ul class=toc>
- <li><a href="#the-body0"><span class=secno>10.3.1 </span>The
+ <li><a href="#the-body0"><span class=secno>9.3.1 </span>The
<code>body</code> element</a>
- <li><a href="#the-applet"><span class=secno>10.3.2 </span>The
+ <li><a href="#the-applet"><span class=secno>9.3.2 </span>The
<code>applet</code> element</a>
</ul>
</ul>
- <li><a href="#no"><span class=secno>11. </span>Things that you can't do
+ <li><a href="#no"><span class=secno>10. </span>Things that you can't do
with this specification because they are better handled using other
technologies that are further described herein</a>
<ul class=toc>
- <li><a href="#localisation"><span class=secno>11.1
+ <li><a href="#localisation"><span class=secno>10.1
</span>Localisation</a>
- <li><a href="#declarative"><span class=secno>11.2 </span>Declarative 2D
+ <li><a href="#declarative"><span class=secno>10.2 </span>Declarative 2D
vector graphics and animation</a>
- <li><a href="#declarative0"><span class=secno>11.3 </span>Declarative 3D
+ <li><a href="#declarative0"><span class=secno>10.3 </span>Declarative 3D
scenes</a>
- <li><a href="#timers"><span class=secno>11.4 </span>Timers</a>
+ <li><a href="#timers"><span class=secno>10.4 </span>Timers</a>
</ul>
<li class=no-num><a href="#references">References</a>
@@ -2179,9 +2169,9 @@
informed choices regarding which HTML elements and attributes are most
appropriate.</p>
- <p>However, WYSIWYG tools are legitimate, and this specification <a
- href="#wysiwyg1" title="WYSIWYG editors">makes certain concessions to
- WYSIWYG editors</a>.</p>
+ <p>However, WYSIWYG tools are legitimate, and this specification <span
+ title="WYSIWYG editors">makes certain concessions to WYSIWYG
+ editors</span>.</p>
<p>All authoring tools, whether WYSIWYG or not, should make a best effort
attempt at enabling users to create well-structured, semantically rich,
@@ -2885,6 +2875,9 @@
attribute DOMString <a href="#contenteditable1" title=dom-contentEditable>contentEditable</a>;
readonly attribute DOMString <a href="#iscontenteditable" title=dom-isContentEditable>isContentEditable</a>;
+ // <span>styling</span>
+ readonly attribute <span>CSSStyleDeclaration</span> <a href="#style0" title=dom-style>style</a>;
+
// <span>data templates</span>
attribute DOMString <a href="#template0" title=dom-template>template</a>;
readonly attribute HTMLDataTemplateElement <a href="#templateelement" title=dom-templateElement>templateElement</a>;
@@ -6378,6 +6371,8 @@
<dd><code title=attr-registrationmark><a
href="#registrationmark">registrationmark</a></code>
+ <dd><code title=attr-style><a href="#style">style</a></code>
+
<dd><code title=attr-tabindex><a href="#tabindex">tabindex</a></code>
<dd><code title=attr-template><a href="#template">template</a></code>
@@ -6749,7 +6744,49 @@
title=dom-irrelevant><code>irrelevant</code></dfn> DOM attribute must <a
href="#reflect">reflect</a> the content attribute of the same name.
- <h4 id=embedding><span class=secno>3.4.7 </span><dfn
+ <h4 id=the-style><span class=secno>3.4.7 </span>The <dfn id=style
+ title=attr-style><code>style</code></dfn> attribute</h4>
+
+ <p>All elements may have the <code title=attr-style><a
+ href="#style">style</a></code> content attribute set. If specified, the
+ attribute must contain only a list of zero or more semicolon-separated (;)
+ CSS declarations. <a href="#refsCSS21">[CSS21]</a>
+
+ <p>The declarations specified must be parsed and treated as the body of a
+ declaration block whose selector matches just the element on which the
+ attribute is set. For the purposes of the CSS cascade, the attribute must
+ be considered to be a 'style' attribute at the author level.
+
+ <p>Documents that use <code title=attr-style><a
+ href="#style">style</a></code> attributes on any of their elements must
+ still be comprehensible and usable if those attributes were removed.
+
+ <p class=note>In particular, using the <code title=attr-style><a
+ href="#style">style</a></code> attribute to hide and show content, or to
+ convey meaning that is otherwise not included in the document, is
+ non-conforming.
+
+ <p>The <dfn id=style0 title=dom-style><code>style</code></dfn> DOM
+ attribute must return a <code>CSSStyleDeclaration</code> whose value
+ represents the declarations specified in the attribute, if present.
+ Mutating the <code>CSSStyleDeclaration</code> object must create a <code
+ title=attr-font-style>style</code> attribute on the element (if there
+ isn't one already) and then change its value to be a value representing
+ the serialised form of the <code>CSSStyleDeclaration</code> object. <a
+ href="#refsCSSOM">[CSSOM]</a>
+
+ <div class=example>
+ <p>In the following example, the words that refer to colors are marked up
+ using the <code><a href="#span">span</a></code> element and the <code
+ title=attr-style><a href="#style">style</a></code> attribute to make
+ those words show up in the relevant colors in visual media.</p>
+
+ <pre><p>My jump suit is <span style="color: green; background:
+transparent">green</span> and my eyes are <span style="color: blue;
+background: transparent">blue</span>.</p></pre>
+ </div>
+
+ <h4 id=embedding><span class=secno>3.4.8 </span><dfn
id=embedding0>Embedding custom non-visible data</dfn></h4>
<p>Every <a href="#html-elements" title="HTML elements">HTML element</a>
@@ -7672,7 +7709,7 @@
kinds of metadata that cannot be expressed using the <code><a
href="#title1">title</a></code>, <code><a href="#base">base</a></code>,
<code><a href="#link">link</a></code>, <code><a
- href="#style">style</a></code>, and <code><a
+ href="#style1">style</a></code>, and <code><a
href="#script0">script</a></code> elements.
<p>The <code><a href="#meta0">meta</a></code> element can represent
@@ -7759,9 +7796,8 @@
<dd>
<p>The value must be a free-form string that identifies the software used
to generate the document. This value must not be used on hand-authored
- pages. WYSIWYG editors have <a href="#wysiwyg2" title="WYSIWYG
- signature">additional constraints</a> on the value used with this
- metadata name.
+ pages. WYSIWYG editors have <span title="WYSIWYG signature">additional
+ constraints</span> on the value used with this metadata name.
<dt><dfn id=dns title=meta-dns>dns</dfn>
@@ -8227,8 +8263,8 @@
<p>In XHTML, the XML declaration should be used for inline character
encoding information, if necessary.
- <h4 id=the-style><span class=secno>3.7.6 </span>The <dfn
- id=style><code>style</code></dfn> element</h4>
+ <h4 id=the-style0><span class=secno>3.7.6 </span>The <dfn
+ id=style1><code>style</code></dfn> element</h4>
<dl class=element>
<dt>Categories
@@ -8253,7 +8289,7 @@
<dd>If the <code title=attr-style-scoped><a
href="#scoped">scoped</a></code> attribute is present: where <a
href="#flow-content0">flow content</a> is expected, but before any
- sibling elements other than <code><a href="#style">style</a></code>
+ sibling elements other than <code><a href="#style1">style</a></code>
elements and before any text nodes other than <a
href="#inter-element">inter-element whitespace</a>.
@@ -8290,9 +8326,9 @@
how. <a href="#refsCSSOM">[CSSOM]</a></p>
</dl>
- <p>The <code><a href="#style">style</a></code> element allows authors to
+ <p>The <code><a href="#style1">style</a></code> element allows authors to
embed style information in their documents. The <code><a
- href="#style">style</a></code> element is one of several inputs to the <a
+ href="#style1">style</a></code> element is one of several inputs to the <a
href="#styling0">styling processing model</a>.
<p>If the <dfn id=type1 title=attr-style-type><code>type</code></dfn>
@@ -8320,55 +8356,55 @@
<p>The <dfn id=scoped title=attr-style-scoped><code>scoped</code></dfn>
attribute is a <a href="#boolean0">boolean attribute</a>. If the attribute
is present, then the user agent must only apply the specified style
- information to the <code><a href="#style">style</a></code> element's
+ information to the <code><a href="#style1">style</a></code> element's
parent element (if any), and that element's child nodes. Otherwise, the
specified styles must, if applied, be applied to the entire document.
<p>If the <code title=attr-style-scoped><a href="#scoped">scoped</a></code>
- attribute is not specified, the <code><a href="#style">style</a></code>
+ attribute is not specified, the <code><a href="#style1">style</a></code>
element must be the child of a <code><a href="#head">head</a></code>
element or of a <code><a href="#noscript">noscript</a></code> element that
is a child of a <code><a href="#head">head</a></code> element.
<p>If the <code title=attr-style-scoped><a href="#scoped">scoped</a></code>
attribute <em>is</em> specified, then the <code><a
- href="#style">style</a></code> element must be the child of a <a
+ href="#style1">style</a></code> element must be the child of a <a
href="#flow-content0">flow content</a> element, before any text nodes
other than <a href="#inter-element">inter-element whitespace</a>, and
before any elements other than other <code><a
- href="#style">style</a></code> elements.
+ href="#style1">style</a></code> elements.
<p id=title-on-style>The <dfn id=title3
title=attr-style-title><code>title</code></dfn> attribute on <code><a
- href="#style">style</a></code> elements defines <a
+ href="#style1">style</a></code> elements defines <a
href="#alternative">alternative style sheet sets</a>. If the <code><a
- href="#style">style</a></code> element has no <code
+ href="#style1">style</a></code> element has no <code
title=attr-style-title><a href="#title3">title</a></code> attribute, then
it has no title; the <code title=attr-title><a
href="#title">title</a></code> attribute of ancestors does not apply to
- the <code><a href="#style">style</a></code> element.</p>
+ the <code><a href="#style1">style</a></code> element.</p>
<!--
XXX xref -->
<p class=note>The <code title=attr-style-title><a
href="#title3">title</a></code> attribute on <code><a
- href="#style">style</a></code> elements, like the <code
+ href="#style1">style</a></code> elements, like the <code
title=attr-link-title><a href="#title2">title</a></code> attribute on
<code><a href="#link">link</a></code> elements, differs from the global
<code title=attr-title><a href="#title">title</a></code> attribute in that
- a <code><a href="#style">style</a></code> block without a title does not
+ a <code><a href="#style1">style</a></code> block without a title does not
inherit the title of the parent element: it merely has no title.
<p>All descendant elements must be processed, according to their semantics,
- before the <code><a href="#style">style</a></code> element itself is
+ before the <code><a href="#style1">style</a></code> element itself is
evaluated. For styling languages that consist of pure text, user agents
- must evaluate <code><a href="#style">style</a></code> elements by passing
+ must evaluate <code><a href="#style1">style</a></code> elements by passing
the concatenation of the contents of all the <a href="#text-node"
title="text node">text nodes</a> that are direct children of the <code><a
- href="#style">style</a></code> element (not any other nodes such as
+ href="#style1">style</a></code> element (not any other nodes such as
comments or elements), in <a href="#tree-order">tree order</a>, to the
style system. For XML-based styling languages, user agents must pass all
- the children nodes of the <code><a href="#style">style</a></code> element
+ the children nodes of the <code><a href="#style1">style</a></code> element
to the style system.
<p class=note>This specification does not specify a style system, but CSS
@@ -8390,16 +8426,16 @@
title="styling processing model">Styling</dfn></h4>
<p>The <code><a href="#link">link</a></code> and <code><a
- href="#style">style</a></code> elements can provide styling information
+ href="#style1">style</a></code> elements can provide styling information
for the user agent to use when rendering the document. The DOM Styling
specification specifies what styling information is to be used by the user
agent and how it is to be used. <a href="#refsCSSOM">[CSSOM]</a>
- <p>The <code><a href="#style">style</a></code> and <code><a
+ <p>The <code><a href="#style1">style</a></code> and <code><a
href="#link">link</a></code> elements implement the <code>LinkStyle</code>
interface. <a href="#refsCSSOM">[CSSOM]</a>
- <p>For <code><a href="#style">style</a></code> elements, if the user agent
+ <p>For <code><a href="#style1">style</a></code> elements, if the user agent
does not support the specified styling language, then the <code
title=dom-LinkStyle-sheet>sheet</code> attribute of the element's
<code>LinkStyle</code> interface must return null. Similarly, <code><a
@@ -8424,7 +8460,7 @@
<dd>
<p>The content type must be the same as the style's specified type. For
- <code><a href="#style">style</a></code> elements, this is the same as
+ <code><a href="#style1">style</a></code> elements, this is the same as
the <code title=attr-style-type><a href="#type1">type</a></code> content
attribute's value, or <code title="">text/css</code> if that is omitted.
For <code><a href="#link">link</a></code> elements, this is the <a
@@ -8438,7 +8474,7 @@
<p>For <code><a href="#link">link</a></code> elements, the location must
be the URI given by the element's <code title=attr-link-href><a
href="#href1">href</a></code> content attribute. For <code><a
- href="#style">style</a></code> elements, there is no location.
+ href="#style1">style</a></code> elements, there is no location.
<dt>The intended destination media for style information (<code
title=dom-stylesheet-media>media</code> DOM attribute)
@@ -8460,7 +8496,7 @@
<p>The <dfn id=disabled1
title=dom-LinkStyle-disabled><code>disabled</code></dfn> DOM attribute on
<code><a href="#link">link</a></code> and <code><a
- href="#style">style</a></code> elements must return false and do nothing
+ href="#style1">style</a></code> elements must return false and do nothing
on setting, if the <code title=dom-linkstyle-sheet>sheet</code> attribute
of their <code>LinkStyle</code> interface is null. Otherwise, it must
return the value of the <code>StyleSheet</code> interface's <code
@@ -18447,7 +18483,7 @@
title=dom-context-2d-globalCompositeOperation>global composition
operators</a>. (Transformations affect the path when the path is created,
not when it is painted, though the stroke <em><a
- href="#style">style</a></em> is still affected by the transformation
+ href="#style1">style</a></em> is still affected by the transformation
during painting.)
<p>Zero-length line segments must be pruned before stroking a path. Empty
@@ -22078,7 +22114,7 @@
<dd>When <a href="#scripting1">scripting is disabled</a>, in a <code><a
href="#head">head</a></code> element: in any order, zero or more <code><a
href="#link">link</a></code> elements, zero or more <code><a
- href="#style">style</a></code> elements, and zero or more <code><a
+ href="#style1">style</a></code> elements, and zero or more <code><a
href="#meta0">meta</a></code> elements.
<dd>When <a href="#scripting1">scripting is disabled</a>, not in a
@@ -22120,17 +22156,17 @@
href="#scripting1">scripting is disabled</a>, then the content model of a
<code><a href="#noscript">noscript</a></code> element must contain only
<code><a href="#link">link</a></code>, <code><a
- href="#style">style</a></code>, and <code><a href="#meta0">meta</a></code>
- elements. If <a href="#scripting2">scripting is enabled</a>, then the
- content model of a <code><a href="#noscript">noscript</a></code> element
- is text, except that invoking the <a href="#html-fragment0">HTML fragment
- parsing algorithm</a> with the <code><a
- href="#noscript">noscript</a></code> element as the <var
+ href="#style1">style</a></code>, and <code><a
+ href="#meta0">meta</a></code> elements. If <a href="#scripting2">scripting
+ is enabled</a>, then the content model of a <code><a
+ href="#noscript">noscript</a></code> element is text, except that invoking
+ the <a href="#html-fragment0">HTML fragment parsing algorithm</a> with the
+ <code><a href="#noscript">noscript</a></code> element as the <var
title="">context</var> element and the text contents as the <var
title="">input</var> must result in a list of nodes that consists only of
<code><a href="#link">link</a></code>, <code><a
- href="#style">style</a></code>, and <code><a href="#meta0">meta</a></code>
- elements.
+ href="#style1">style</a></code>, and <code><a
+ href="#meta0">meta</a></code> elements.
<p>Outside of <code><a href="#head">head</a></code> elements, if <a
href="#scripting1">scripting is disabled</a>, then the content model of a
@@ -27400,7 +27436,7 @@
href="#the-javascript">javascript:</a></code> URIs (e.g. the <code
title=attr-img-src><a href="#src">src</a></code> attribute of <code><a
href="#img">img</a></code> elements, or an <code title="">@import</code>
- rule in a CSS <code><a href="#style">style</a></code> element block).
+ rule in a CSS <code><a href="#style1">style</a></code> element block).
<li>Event handlers, whether registered through the DOM using <code
title="">addEventListener()</code>, by explicit <a href="#event3">event
@@ -38873,7 +38909,7 @@
<dt>CDATA elements
- <dd><code><a href="#style">style</a></code>, <code><a
+ <dd><code><a href="#style1">style</a></code>, <code><a
href="#script0">script</a></code></dd>
<!-- iframe and
noscript don't count as CDATA for syntax purposes -->
@@ -39189,7 +39225,7 @@
title=syntax-comments>comment</a>, except if the first thing inside the
<code><a href="#body0">body</a></code> element is a <code><a
href="#script0">script</a></code> or <code><a
- href="#style">style</a></code>
+ href="#style1">style</a></code>
element<!-- and the node immediately preceding
the <code>body</code> element is a <code>head</code> element whose
end tag has been omitted (XXX this last bit is commented out for now
@@ -40438,7 +40474,7 @@
href="#p">p</a></code>, <code><a href="#param">param</a></code>,
<code>plaintext</code>, <code><a href="#pre">pre</a></code>, <code><a
href="#script0">script</a></code>, <code>select</code>,
- <code>spacer</code>, <code><a href="#style">style</a></code>, <code><a
+ <code>spacer</code>, <code><a href="#style1">style</a></code>, <code><a
href="#tbody">tbody</a></code>, <code>textarea</code>, <code><a
href="#tfoot0">tfoot</a></code>, <code><a
href="#thead0">thead</a></code>, <code><a
@@ -40463,10 +40499,9 @@
<p>The following HTML elements are those that end up in the <a
href="#list-of4">list of active formatting elements</a>: <code><a
href="#a">a</a></code>, <code><a href="#b">b</a></code>,
- <code>big</code>, <code><a href="#em">em</a></code>, <code><a
- href="#font">font</a></code>, <code><a href="#i">i</a></code>,
- <code>nobr</code>, <code>s</code>, <code><a
- href="#small">small</a></code>, <code>strike</code>, <code><a
+ <code>big</code>, <code><a href="#em">em</a></code>, <code>font</code>,
+ <code><a href="#i">i</a></code>, <code>nobr</code>, <code>s</code>,
+ <code><a href="#small">small</a></code>, <code>strike</code>, <code><a
href="#strong">strong</a></code>, <code>tt</code>, and <code>u</code>.
<dt><dfn id=phrasing1>Phrasing</dfn>
@@ -46260,7 +46295,7 @@
<dd>
<p>If one of the ancestors of <var title="">current node</var> is a
- <code><a href="#style">style</a></code>, <code><a
+ <code><a href="#style1">style</a></code>, <code><a
href="#script0">script</a></code>, <code>xmp</code>, <code><a
href="#iframe">iframe</a></code>, <code>noembed</code>,
<code>noframes</code>, <code><a
@@ -46395,7 +46430,7 @@
<dd>Set the <a href="#content2">content model flag</a> to
<em>RCDATA</em>.
- <dt>If it is a <code><a href="#style">style</a></code>, <code><a
+ <dt>If it is a <code><a href="#style1">style</a></code>, <code><a
href="#script0">script</a></code>, <code>xmp</code>, <code><a
href="#iframe">iframe</a></code>, <code>noembed</code>, or
<code>noframes</code> element
@@ -48623,143 +48658,7 @@
-->
</div>
- <h2 id=wysiwyg><span class=secno>9. </span>WYSIWYG editors</h2>
-
- <p><dfn id=wysiwyg1>WYSIWYG editors</dfn> are authoring tools with a
- predominantly presentation-driven user interface.
-
- <h3 id=presentational><span class=secno>9.1 </span>Presentational markup</h3>
-
- <h4 id=wysiwyg0><span class=secno>9.1.1 </span><dfn id=wysiwyg2>WYSIWYG
- signature</dfn></h4>
-
- <p>WYSIWYG editors must include a <code><a href="#meta0">meta</a></code>
- element in the <code><a href="#head">head</a></code> element whose <code
- title=attr-meta-name><a href="#name">name</a></code> attribute has the
- value <code title=meta-generator><a href="#generator">generator</a></code>
- and whose <code title=attr-meta-content><a
- href="#content0">content</a></code> attribute's value ends with the string
- "<code title="">(WYSIWYG editor)</code>". Non-WYSIWYG authoring tools must
- not include this string in their generator string.
-
- <p class=big-issue>This entire section will probably be dropped. The intent
- of this section was to allow a way for WYSIWYG editors, which aren't going
- to use semantic markup, to still write conforming documents, while not
- letting it be ok for hand-coding authors to not use semantic markup. We
- still need some sort of solution to this, but it's not clear what it is.
-
- <h4 id=the-font><span class=secno>9.1.2 </span>The <dfn
- id=font><code>font</code></dfn> element</h4>
-
- <dl class=element>
- <dt>Categories
-
- <dd><a href="#phrasing0">Phrasing content</a>.
-
- <dt>Contexts in which this element may be used:
-
- <dd>Where <a href="#phrasing0">phrasing content</a> is expected.
-
- <dt>Content model:
-
- <dd><a href="#transparent0">Transparent</a>.
-
- <dt>Element-specific attributes:</dt>
- <!--
- <dd><code title="attr-font-color">color</code></dd>
- <dd><code title="attr-font-face">face</code></dd>
- <dd><code title="attr-font-size">size</code></dd>-->
-
- <dd><code title=attr-font-style><a href="#style0">style</a></code>
-
- <dt>DOM interface:
-
- <dd>
- <pre
- class=idl>interface <dfn id=htmlfontelement>HTMLFontElement</dfn> : <a href="#htmlelement">HTMLElement</a> {<!--
- attribute DOMString <span title="dom-font-color">color</span>;
- attribute DOMString <span title="dom-font-face">face</span>;
- attribute DOMString <span title="dom-font-size">size</span>;-->
- readonly attribute CSSStyleDeclaration <a href="#style1" title=dom-font-style>style</a>;
-};</pre>
- </dl>
-
- <p class=big-issue>This entire section will probably be dropped. The intent
- of this section was to allow a way for WYSIWYG editors, which don't have
- enough information to use the "real" "semantic" elements, to still make
- HTML pages without abusing those semantic elements (since abusing elements
- is even worse than not using them in the first place). We have still got
- to find a solution to this, while not letting it be ok for hand-coding
- authors to abuse the style="" attribute.
-
- <p>The <code><a href="#font">font</a></code> element doesn't represent
- anything. It must not be used except by <a href="#wysiwyg1">WYSIWYG
- editors</a>, which may use it to achieve presentational affects. Even
- WYSIWYG editors, however, should make every effort to use appropriate
- semantic markup and avoid the use of media-specific presentational markup.
-
- <p>Conformance checkers must consider this element to be non-conforming if
- it is used on a page lacking the <a href="#wysiwyg2">WYSIWYG
- signature</a>.
-
- <div class=example>
- <p>The following would be syntactically legal (as the output from a
- WYSIWYG editor, though not anywhere else):</p>
-
- <pre><!DOCTYPE HTML>
-<html>
- <head>
- <title></title>
- <meta name="generator" content="Sample Editor 1.0 <em>(WYSIWYG editor)</em>">
- </head>
- <body>
- <font style="display: block; border: solid">
- <h1>Hello.</h1>
- </font>
- <p>
- <font style="color: orange; background: white">How</font>
- <font style="color: yellow; background: white">do</font>
- <font style="color: green; background: white"><em><em></em>you<em></em></em></font>
- <font style="color: blue; background: white">do?</font>
- </p>
- </body>
-</html></pre>
-
- <p>The first <code><a href="#font">font</a></code> element is conformant
- because <code><a href="#h1">h1</a></code> and <code><a
- href="#p">p</a></code> elements are both allowed in <code><a
- href="#body0">body</a></code> elements. the next four are allowed because
- text and <code><a href="#em">em</a></code> elements are allowed in
- <code><a href="#p">p</a></code> elements.</p>
- </div>
-
- <p>The <dfn id=style0 title=attr-font-style><code>style</code></dfn>
- attribute, if specified, must contain only a list of zero or more
- semicolon-separated (;) CSS declarations. <a href="#refsCSS21">[CSS21]</a>
-
- <p class=big-issue>We probably need to move this attribute to more
- elements, maybe even all of them, though if we do that we really should
- find a way to strongly discourage its use (and the use of its DOM
- attribute) for non-WYSIWYG authors.</p>
- <!-- XXX deal with each of the use cases in this:
- http://lists.w3.org/Archives/Public/www-html/2003Jan/0277.html -->
-
- <p>The declarations specified must be parsed and treated as the body of a
- declaration block whose selector matches just that <code><a
- href="#font">font</a></code> element. For the purposes of the CSS cascade,
- the attribute must be considered to be a 'style' attribute at the author
- level.
-
- <p>The <dfn id=style1 title=dom-font-style><code>style</code></dfn> DOM
- attribute must return a <code>CSSStyleDeclaration</code> whose value
- represents the declarations specified in the attribute, if present.
- Mutating the <code>CSSStyleDeclaration</code> object must create a <code
- title=attr-font-style><a href="#style0">style</a></code> attribute on the
- element (if there isn't one already) and then change its value to be a
- value representing the serialised form of the
- <code>CSSStyleDeclaration</code> object. <a href="#refsCSSOM">[CSSOM]</a>
-
- <h2 id=rendering><span class=secno>10. </span>Rendering and user-agent
+ <h2 id=rendering><span class=secno>9. </span>Rendering and user-agent
behavior</h2>
<!-- XXX
@@ -48852,7 +48751,7 @@
<p class=big-issue>Must define that in CSS, tag names in HTML documents,
and class names in quirks mode documents, are case-insensitive.
- <h3 id=rendering0><span class=secno>10.1 </span>Rendering and the DOM</h3>
+ <h3 id=rendering0><span class=secno>9.1 </span>Rendering and the DOM</h3>
<p class=big-issue>This section is wrong. mediaMode will end up on Window,
I think. All views implement Window.
@@ -48884,10 +48783,9 @@
currently to enumerate all the views.</p>
<!-- XXX examples! -->
- <h3 id=rendering1><span class=secno>10.2 </span>Rendering and
- menus/toolbars</h3>
+ <h3 id=rendering1><span class=secno>9.2 </span>Rendering and menus/toolbars</h3>
- <h4 id=the-icon><span class=secno>10.2.1 </span>The 'icon' property</h4>
+ <h4 id=the-icon><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
@@ -48895,10 +48793,10 @@
title=command-attribute>command</code> attribute, but when the property
computes to an actual image, it should use that image instead.
- <h3 id=obsolete><span class=secno>10.3 </span>Obsolete elements,
- attributes, and APIs</h3>
+ <h3 id=obsolete><span class=secno>9.3 </span>Obsolete elements, attributes,
+ and APIs</h3>
- <h4 id=the-body0><span class=secno>10.3.1 </span>The <code><a
+ <h4 id=the-body0><span class=secno>9.3.1 </span>The <code><a
href="#body0">body</a></code> element</h4>
<p class=big-issue>Need to define the content attributes in terms of CSS or
@@ -48983,7 +48881,7 @@
href="#reflect">reflect</a> the element's <code
title=attr-body-vlink>vlink</code> content attribute.
- <h4 id=the-applet><span class=secno>10.3.2 </span>The <dfn
+ <h4 id=the-applet><span class=secno>9.3.2 </span>The <dfn
id=applet><code>applet</code></dfn> element</h4>
<p>The <code><a href="#applet">applet</a></code> element is a Java-specific
@@ -49004,7 +48902,7 @@
rooted at the <code>Document</code> node, whose filter matches only
<code><a href="#applet">applet</a></code> elements.
- <h2 id=no><span class=secno>11. </span>Things that you can't do with this
+ <h2 id=no><span class=secno>10. </span>Things that you can't do with this
specification because they are better handled using other technologies
that are further described herein</h2>
@@ -49015,7 +48913,7 @@
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=localisation><span class=secno>11.1 </span>Localisation</h3>
+ <h3 id=localisation><span class=secno>10.1 </span>Localisation</h3>
<p>If you wish to create localised versions of an HTML application, the
best solution is to preprocess the files on the server, and then use HTTP
@@ -49023,19 +48921,19 @@
<!-- <p>XXX example here</p> -->
<!--XXXSVG (remove next section)-->
- <h3 id=declarative><span class=secno>11.2 </span>Declarative 2D vector
+ <h3 id=declarative><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=declarative0><span class=secno>11.3 </span>Declarative 3D scenes</h3>
+ <h3 id=declarative0><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>11.4 </span>Timers</h3>
+ <h3 id=timers><span class=secno>10.4 </span>Timers</h3>
<p>This section is expected to be moved to the Window Object specification
in due course.
@@ -49170,15 +49068,15 @@
Mike Smith, Mikko Rantalainen, Neil Deakin, Neil Soiffer, Olav Junker
Kjær, Oliver Hunt, Peter Kasting, Philip Taylor, Philip
TAYLOR<!-- a different one -->, Rachid Finge, Rajas Moonka, Ralf Stoltze,
- Ralph Giles, Raphael Champeimont, Richard Ishida, Rimantas Liubertas,
- Robert O'Callahan, Robert Sayre, Roman Ivanov, S. Mike Dierken, Sam Ruby,
- Sam Weinig, Scott Hess, Sean Knapp, Shaun Inman, Silvia Pfeiffer, Simon
- Pieters, Stefan Haustein, Stephen Ma, Steve Faulkner, Steve Runyon, Steven
- Garrity, Stewart Brodie, Stuart Parmenter, Sunava Dutta, Tantek
- Çelik, Terrence Wood, Thomas Broyer, Thomas O'Connor, Tim Altman,
- Tyler Close, Vladimir Vukićević, Wakaba, Wayne Pollock,
- William Swanson, and Øistein E. Andersen, for their useful and
- substantial comments.
+ Ralph Giles, Raphael Champeimont, Rene Saarsoo, Richard Ishida, Rimantas
+ Liubertas, Robert O'Callahan, Robert Sayre, Roman Ivanov, S. Mike Dierken,
+ Sam Ruby, Sam Weinig, Scott Hess, Sean Knapp, Shaun Inman, Silvia
+ Pfeiffer, Simon Pieters, Stefan Haustein, Stephen Ma, Steve Faulkner,
+ Steve Runyon, Steven Garrity, Stewart Brodie, Stuart Parmenter, Sunava
+ Dutta, Tantek Çelik, Terrence Wood, Thomas Broyer, Thomas O'Connor,
+ Tim Altman, Tyler Close, Vladimir Vukićević, Wakaba, Wayne
+ Pollock, William Swanson, and Øistein E. Andersen, for their useful
+ and substantial comments.
<p>Thanks also to everyone who has ever posted about HTML5 to their blogs,
public mailing lists, or forums, including the <a
Modified: source
===================================================================
--- source 2008-04-29 11:14:21 UTC (rev 1510)
+++ source 2008-04-29 12:23:28 UTC (rev 1511)
@@ -1183,6 +1183,9 @@
attribute DOMString <span title="dom-contentEditable">contentEditable</span>;
readonly attribute DOMString <span title="dom-isContentEditable">isContentEditable</span>;
+ // <span>styling</span>
+ readonly attribute <span>CSSStyleDeclaration</span> <span title="dom-style">style</span>;
+
// <span>data templates</span>
attribute DOMString <span title="dom-template">template</span>;
readonly attribute HTMLDataTemplateElement <span title="dom-templateElement">templateElement</span>;
@@ -4856,6 +4859,7 @@
<dd><code title="attr-lang">lang</code></dd>
<dd><code title="attr-ref">ref</code></dd>
<dd><code title="attr-registrationmark">registrationmark</code></dd>
+ <dd><code title="attr-style">style</code></dd>
<dd><code title="attr-tabindex">tabindex</code></dd>
<dd><code title="attr-template">template</code></dd>
<dd><code title="attr-title">title</code></dd>
@@ -5180,6 +5184,53 @@
same name.</p>
+ <h4>The <dfn title="attr-style"><code>style</code></dfn> attribute</h4>
+
+ <p>All elements may have the <code title="attr-style">style</code>
+ content attribute set. If specified, the attribute must contain only
+ a list of zero or more semicolon-separated (;) CSS declarations. <a
+ href="#refsCSS21">[CSS21]</a></p>
+
+ <p>The declarations specified must be parsed and treated as the body
+ of a declaration block whose selector matches just the element on
+ which the attribute is set. For the purposes of the CSS cascade, the
+ attribute must be considered to be a 'style' attribute at the author
+ level.</p>
+
+ <p>Documents that use <code title="attr-style">style</code>
+ attributes on any of their elements must still be comprehensible and
+ usable if those attributes were removed.</p>
+
+ <p class="note">In particular, using the <code
+ title="attr-style">style</code> attribute to hide and show content,
+ or to convey meaning that is otherwise not included in the document,
+ is non-conforming.</p>
+
+ <p>The <dfn title="dom-style"><code>style</code></dfn> DOM attribute
+ must return a <code>CSSStyleDeclaration</code> whose value
+ represents the declarations specified in the attribute, if
+ present. Mutating the <code>CSSStyleDeclaration</code> object must
+ create a <code title="attr-font-style">style</code> attribute on the
+ element (if there isn't one already) and then change its value to be
+ a value representing the serialised form of the
+ <code>CSSStyleDeclaration</code> object. <a
+ href="#refsCSSOM">[CSSOM]</a>
+
+ <div class="example">
+
+ <p>In the following example, the words that refer to colors are
+ marked up using the <code>span</code> element and the <code
+ title="attr-style">style</code> attribute to make those words show
+ up in the relevant colors in visual media.</p>
+
+ <pre><p>My jump suit is <span style="color: green; background:
+transparent">green</span> and my eyes are <span style="color: blue;
+background: transparent">blue</span>.</p></pre>
+
+ </div>
+
+
+
<h4><dfn>Embedding custom non-visible data</dfn></h4>
<p>Every <span title="HTML elements">HTML element</span> may have
@@ -43852,140 +43903,8 @@
</div>
- <h2 id="wysiwyg">WYSIWYG editors</h2>
- <p><dfn>WYSIWYG editors</dfn> are authoring tools with a
- predominantly presentation-driven user interface.</p>
-
- <h3>Presentational markup</h3>
-
-
- <h4><dfn>WYSIWYG signature</dfn></h4>
-
- <p>WYSIWYG editors must include a <code>meta</code> element in the
- <code>head</code> element whose <code
- title="attr-meta-name">name</code> attribute has the value <code
- title="meta-generator">generator</code> and whose <code
- title="attr-meta-content">content</code> attribute's value ends with
- the string "<code title="">(WYSIWYG editor)</code>". Non-WYSIWYG
- authoring tools must not include this string in their generator
- string.</p>
-
- <p class="big-issue">This entire section will probably be
- dropped. The intent of this section was to allow a way for WYSIWYG
- editors, which aren't going to use semantic markup, to still write
- conforming documents, while not letting it be ok for hand-coding
- authors to not use semantic markup. We still need some sort of
- solution to this, but it's not clear what it is.</p>
-
- <h4>The <dfn><code>font</code></dfn> element</h4>
-
- <dl class="element">
- <dt>Categories</dt>
- <dd><span>Phrasing content</span>.</dd>
- <dt>Contexts in which this element may be used:</dt>
- <dd>Where <span>phrasing content</span> is expected.</dd>
- <dt>Content model:</dt>
- <dd><span>Transparent</span>.</dd>
- <dt>Element-specific attributes:</dt><!--
- <dd><code title="attr-font-color">color</code></dd>
- <dd><code title="attr-font-face">face</code></dd>
- <dd><code title="attr-font-size">size</code></dd>-->
- <dd><code title="attr-font-style">style</code></dd>
- <dt>DOM interface:</dt>
- <dd>
-<pre class="idl">interface <dfn>HTMLFontElement</dfn> : <span>HTMLElement</span> {<!--
- attribute DOMString <span title="dom-font-color">color</span>;
- attribute DOMString <span title="dom-font-face">face</span>;
- attribute DOMString <span title="dom-font-size">size</span>;-->
- readonly attribute CSSStyleDeclaration <span title="dom-font-style">style</span>;
-};</pre>
- </dd>
- </dl>
-
- <p class="big-issue">This entire section will probably be
- dropped. The intent of this section was to allow a way for WYSIWYG
- editors, which don't have enough information to use the "real"
- "semantic" elements, to still make HTML pages without abusing those
- semantic elements (since abusing elements is even worse than not
- using them in the first place). We have still got to find a solution
- to this, while not letting it be ok for hand-coding authors to abuse
- the style="" attribute.</p>
-
- <p>The <code>font</code> element doesn't represent anything. It must
- not be used except by <span>WYSIWYG editors</span>, which may use it
- to achieve presentational affects. Even WYSIWYG editors, however,
- should make every effort to use appropriate semantic markup and
- avoid the use of media-specific presentational markup.</p>
-
- <p>Conformance checkers must consider this element to be
- non-conforming if it is used on a page lacking the <span>WYSIWYG
- signature</span>.</p>
-
- <div class="example">
-
- <p>The following would be syntactically legal (as the output from a
- WYSIWYG editor, though not anywhere else):</p>
-
- <pre><!DOCTYPE HTML>
-<html>
- <head>
- <title></title>
- <meta name="generator" content="Sample Editor 1.0 <em>(WYSIWYG editor)</em>">
- </head>
- <body>
- <font style="display: block; border: solid">
- <h1>Hello.</h1>
- </font>
- <p>
- <font style="color: orange; background: white">How</font>
- <font style="color: yellow; background: white">do</font>
- <font style="color: green; background: white"><em><em></em>you<em></em></em></font>
- <font style="color: blue; background: white">do?</font>
- </p>
- </body>
-</html></pre>
-
- <p>The first <code>font</code> element is conformant because
- <code>h1</code> and <code>p</code> elements are both allowed in
- <code>body</code> elements. the next four are allowed because text
- and <code>em</code> elements are allowed in <code>p</code>
- elements.</p>
-
- </div>
-
- <p>The <dfn title="attr-font-style"><code>style</code></dfn>
- attribute, if specified, must contain only a list of zero or more
- semicolon-separated (;) CSS declarations. <a
- href="#refsCSS21">[CSS21]</a></p>
-
- <p class="big-issue">We probably need to move this attribute to more
- elements, maybe even all of them, though if we do that we really
- should find a way to strongly discourage its use (and the use of its
- DOM attribute) for non-WYSIWYG authors.</p>
-
- <!-- XXX deal with each of the use cases in this:
- http://lists.w3.org/Archives/Public/www-html/2003Jan/0277.html -->
-
- <p>The declarations specified must be parsed and treated as the body
- of a declaration block whose selector matches just that
- <code>font</code> element. For the purposes of the CSS cascade, the
- attribute must be considered to be a 'style' attribute at the author
- level.</p>
-
- <p>The <dfn title="dom-font-style"><code>style</code></dfn> DOM
- attribute must return a <code>CSSStyleDeclaration</code> whose value
- represents the declarations specified in the attribute, if
- present. Mutating the <code>CSSStyleDeclaration</code> object must
- create a <code title="attr-font-style">style</code> attribute on the
- element (if there isn't one already) and then change its value to be
- a value representing the serialised form of the
- <code>CSSStyleDeclaration</code> object. <a
- href="#refsCSSOM">[CSSOM]</a>
-
-
-
<h2 id="rendering">Rendering and user-agent behavior</h2>
<!-- XXX
@@ -44408,16 +44327,16 @@
Mike Shaver, Mike Smith, Mikko Rantalainen, Neil Deakin, Neil
Soiffer, Olav Junker Kjær, Oliver Hunt, Peter Kasting, Philip
Taylor, Philip TAYLOR<!-- a different one -->, Rachid Finge, Rajas
- Moonka, Ralf Stoltze, Ralph Giles, Raphael Champeimont, Richard
- Ishida, Rimantas Liubertas, Robert O'Callahan, Robert Sayre, Roman
- Ivanov, S. Mike Dierken, Sam Ruby, Sam Weinig, Scott Hess, Sean
- Knapp, Shaun Inman, Silvia Pfeiffer, Simon Pieters, Stefan Haustein,
- Stephen Ma, Steve Faulkner, Steve Runyon, Steven Garrity, Stewart
- Brodie, Stuart Parmenter, Sunava Dutta, Tantek Çelik,
- Terrence Wood, Thomas Broyer, Thomas O'Connor, Tim Altman, Tyler
- Close, Vladimir Vukićević, Wakaba, Wayne Pollock,
- William Swanson, and Øistein E. Andersen, for their useful
- and substantial comments.</p>
+ Moonka, Ralf Stoltze, Ralph Giles, Raphael Champeimont, Rene
+ Saarsoo, Richard Ishida, Rimantas Liubertas, Robert O'Callahan,
+ Robert Sayre, Roman Ivanov, S. Mike Dierken, Sam Ruby, Sam Weinig,
+ Scott Hess, Sean Knapp, Shaun Inman, Silvia Pfeiffer, Simon Pieters,
+ Stefan Haustein, Stephen Ma, Steve Faulkner, Steve Runyon, Steven
+ Garrity, Stewart Brodie, Stuart Parmenter, Sunava Dutta, Tantek
+ Çelik, Terrence Wood, Thomas Broyer, Thomas O'Connor, Tim
+ Altman, Tyler Close, Vladimir Vukićević, Wakaba, Wayne
+ Pollock, William Swanson, and Øistein E. Andersen, for their
+ useful and substantial comments.</p>
<p>Thanks also to everyone who has ever posted about HTML5 to their
blogs, public mailing lists, or forums, including the <a
More information about the Commit-Watchers
mailing list