css-style-attr/Overview.src.html@4ce7b66b553a
css-style-attr/Overview.src.html
Wed, 05 Jun 2013 18:07:44 -0700
- author
- Peter Linss <peter.linss@hp.com>
- date
- Wed, 05 Jun 2013 18:07:44 -0700
- changeset 8357
- 4ce7b66b553a
- parent 8243
- 4696787da066
- child 8599
- 18bc8956c979
- permissions
- -rwxr-xr-x
[css-style-attr] add test annotations
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
2 <html lang="en">
3 <head>
4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
5 <title>CSS Style Attributes</title>
6 <link rel="stylesheet" type="text/css" href="../default.css">
8 <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED">
9 <script defer=defer
10 src="http://test.csswg.org/harness/annotate.js#CSS-STYLE-ATTR_DEV"
11 type="text/javascript"></script>
12 </head>
14 <div class="head">
15 <!--logo-->
17 <h1>CSS Style Attributes</h1>
19 <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
20 <dl>
21 <dt>This version:</dt>
22 <!-- <dd><dd><a href="http://www.w3.org/TR/[YEAR]/WD-css-style-attr-[CDATE]/">http://www.w3.org/TR/[YEAR]/WD-css-style-attr-[CDATE]/</a></dd> -->
23 <dd><a href="http://dev.w3.org/csswg/css-style-attr/">http://dev.w3.org/csswg/css-style-attr/</a>
24 </dd>
25 <dt>Latest version:
26 <dd><a href="http://www.w3.org/TR/css-style-attr/">http://www.w3.org/TR/css-style-attr/</a>
27 <dt>Previous version:
28 <dd><a href="http://www.w3.org/TR/2010/WD-css-style-attr-20100121/">http://www.w3.org/TR/2010/WD-css-style-attr-20100121/</a>
29 <dt>Feedback:
30 <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-style-attr%5D%20feedback">www-style@w3.org</a>
31 with subject line “<kbd>[css-style-attr] <var>… message topic …</var></kbd>”
32 (<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/">archives</a>)
33 <dt>Editors:
34 <dd class="vcard"><a lang="tr" class="fn url" href="http://tantek.com/">Tantek Çelik</a>
35 (<span class="company role url">Invited Expert</span>,
36 formerly <a href="http://www.microsoft.com/">Microsoft Corporation</a>)
37 <<a class="email"
38 href="mailto:tantek@cs.stanford.edu">tantek@cs.stanford.edu</a>>
39 </dd>
40 <dd class="vcard"><a class="fn n url" href="http://fantasai.inkedblade.net/contact"><span class="given-name">Elika</span> <abbr class="additional-name">J.</abbr> <span class="family-name">Etemad</span></a> (<span class="company role">Invited Expert</span>)
41 </dd>
42 <dt>Previous Editors:
43 <dd class="vcard"><a class="fn url" href="http://www.w3.org/People/Bos/">Bert Bos</a> (<a class="org" href="http://www.w3.org/">W3C</a>), <<a class="email" href="mailto:bert@w3.org">bert@w3.org</a>>
44 </dd>
45 <dd class="vcard"><span class="fn">Marc Attinasi</span> (<span class="org">AOL/Netscape</span>), <<a class="email" href="mailto:attinasi@netscape.com">attinasi@netscape.com</a>>
46 </dd>
47 </dl>
48 <!--begin-copyright-->
49 <p>[Here will be included the file "../copyright.inc"]</p>
50 <!--end-copyright-->
52 <hr title="Separator for header">
53 </div>
55 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
57 <p>Markup languages such as HTML [[HTML401]] and SVG [[SVG11]] provide a style
58 attribute on most elements, to hold inline style information that applies
59 to those elements. One of the possible style sheet languages is CSS. This
60 draft describes the syntax and interpretation of the CSS fragment that can
61 be used in such style attributes.
63 <h2 class="no-num no-toc" id="status">Status of this document</h2>
64 <!--status-->
65 <p>For this specification to exit the CR stage, the following conditions
66 shall be met:
68 <ol>
69 <li>
70 <p>There must be at least two interoperable implementations. For the
71 purposes of this criterion, we define the following terms:</p>
73 <dl>
74 <dt>interoperable
76 <dd>
77 <p>passing the respective test case(s) in the <a
78 href="http://www.w3.org/Style/CSS/Test/">CSS test suite</a>, or, if
79 the implementation is not a Web browser, an equivalent test. Every
80 relevant test in the test suite should have an equivalent test created
81 if such a user agent (UA) is to be used to claim interoperability. In
82 addition if such a UA is to be used to claim interoperability, then
83 there must one or more additional UAs which can also pass those
84 equivalent tests in the same way for the purpose of interoperability.
85 The equivalent tests must be made publicly available for the purposes
86 of peer review.</p>
88 <dt>implementation
90 <dd>
91 <p>a user agent which:</p>
93 <ol>
94 <li>implements the specification.
96 <li>is available (i.e. publicly downloadable or available through some
97 other public point of sale mechanism). This is the "show me"
98 requirement.
100 <li>is shipped, or is a "nightly build" (i.e., a development version
101 for the next release), but is not experimental (i.e., a version
102 specifically designed to pass the test suite and not intended for
103 daily usage going forward).
104 </ol>
105 </dl>
107 <li>
108 <p>A minimum of three months of the CR period must elapse. That
109 is, this specification will not exit CR before (DATE OF PUBLICATION PLUS THREE MONTHS). When the
110 specification exits CR, an implementation report will be published. At
111 this point, no such report exists.</p>
112 </ol>
114 <p>A CSS Style Attributes <a href="http://www.w3.org/Style/CSS/Test/">Test
115 Suite</a> will be developed during the Candidate Recommendation phase of
116 this CSS Style Attributes specification.
118 <h2 class="no-num no-toc" id="contents">Table of contents</h2>
119 <!--toc-->
121 <h2 id="intro">Introduction</h2>
123 <p>Some document formats have a <dfn>style attribute</dfn> to permit
124 the author to directly apply style information to specific elements
125 in documents. If a document format defines a style attribute (whether named 'style' or something else) and the
126 attribute accepts CSS as its value, then this specification defines that
127 <dfn>style attribute</dfn>’s syntax and interpretation.
129 <div class="example">
130 <p>The following example shows the use of the <code>style</code> attribute
131 in HTML [[HTML401]]:</p>
132 <pre><p style="<em>color: #090; line-height: 1.2</em>">...</p></pre>
133 </div>
135 <h2 id="conformance">Conformance</h2>
137 <p>A document or implementation cannot conform to CSS Style Attributes alone, but can claim conformance to CSS Style Attributes
138 if it satisfies the conformance requirements in this specification when
139 implementing CSS together with style attribute handling as defined in a
140 document language that has one or more CSS style attributes.</p>
142 <p>Conformance to CSS Style Attributes is defined for two
143 classes:
144 <dl>
145 <dt><dfn>document</dfn></dt>
146 <dd>A document represented in a document language that defines a style
147 attribute for one or more of its elements.
148 <dt><dfn>interpreter</dfn></dt>
149 <dd>Someone or something that interprets the semantics of a document and
150 its associated style information.
151 (Most CSS <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">user
152 agents</a> fall under this category.)</dd>
153 </dl>
155 <p>The conformance requirements are expressed with a combination of
156 descriptive assertions and RFC 2119 terminology. The key words "MUST",
157 "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
158 "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
159 document are to be interpreted as described in RFC 2119.
160 However, for readability, these words do not appear in all uppercase
161 letters in this specification. All of the text of this specification is
162 normative except sections explicitly marked as non-normative, examples,
163 and notes. [[!RFC2119]]</p>
165 <p>Examples in this specification are introduced with the words "for example"
166 or are set apart from the normative text with <code>class="example"</code>,
167 like this:
169 <div class="example">
170 <p>This is an example of an informative example.</p>
171 </div>
173 <p>Informative notes begin with the word "Note" and are set apart from the
174 normative text with <code>class="note"</code>, like this:
176 <p class="note">Note, this is an informative note.</p>
178 <h2 id="syntax">Syntax and Parsing</h2>
180 <p>The value of the style attribute must match the syntax of the contents of
181 a CSS <a href="http://www.w3.org/TR/CSS21/syndata.html#rule-sets">declaration
182 block</a> (excluding the delimiting braces), whose formal grammar is given
183 below in the terms and conventions of the
184 <a href="http://www.w3.org/TR/CSS21/syndata.html#syntax">CSS core grammar</a>:
186 <pre>
187 declaration-list
188 : S* declaration? [ ';' S* declaration? ]*
189 ;
190 </pre>
192 <p class="note">Note that following the CSS2.1 convention, comment tokens
193 are not shown in the rule above.
195 <p>The interpreter must parse the style attribute's value using the
196 same forward-compatible parsing rules that apply to parsing declaration block
197 contents in a normal CSS style sheet. See
198 <a href="http://www.w3.org/TR/CSS21/syndata.html">chapter 4 of the CSS2.1
199 specification</a> for details. [[!CSS21]]
201 <p class="note">Note that because there is no open brace delimiting the
202 declaration list in the CSS style attribute syntax, a close brace
203 (<code>}</code>) in the style attribute's value does not terminate the
204 style data: it is merely an invalid token.</p>
206 <h2 id="interpret">Cascading and Interpretation</h2>
208 <p>The declarations in a style attribute apply to the element to which
209 the attribute belongs. In the cascade, these declarations are considered
210 to have author origin and a specificity higher than any selector.
211 CSS2.1 <a href="http://www.w3.org/TR/CSS21/cascade.html#specificity">defines</a>
212 how style sheets and style attributes are cascaded together. [[!CSS21]]
213 Relative URLs in the style data must be resolved relative to the style attribute's element (or to the document if per-element resolution is not
214 defined) when the attribute's value is parsed<!-- so dynamic changes to
215 the base URL don't affect the CSS ~Hixie -->.
217 <p>Aside from the differences in cascading, the declarations in a style
218 attribute must be interpreted exactly as if they were given in a CSS
219 style rule that applies to the element.
221 <p>The CSS Working Group strongly recommends that document languages do
222 not allow multiple CSS style attributes on a single element. If a document
223 language allows multiple CSS style attributes, each must be parsed
224 independently and treated as a separate style rule, the ordering of which
225 should be defined by the document language, else is undefined.
227 <h2 id="ack">Acknowledgments</h2>
229 <p>Thanks to feedback from <span class="vcard"><span class="fn">Daniel Glazman</span></span>, <span class="vcard"><span class="fn">Ian Hickson</span></span>, <span class="vcard"><span class="fn n"><span class="given-name">Eric</span> <abbr class="additional-name">A.</abbr> <span class="family-name">Meyer</span></span></span>,
230 <span class="vcard"><span class="fn">Björn Höhrmann</span></span>.
231 </p>
233 <h2 id="references">References
235 <h3 class="no-num" id="normative-references">Normative references</h3>
237 <!--begin-normative-->
238 <p>[Here will be inserted the file "normative.inc"]</p>
239 <!--end-normative-->
241 <h3 class="no-num" id="informative-references">Informative references</h3>
243 <!--begin-informative-->
244 <p>[Here will be inserted the file "informative.inc"]</p>
245 <!--end-informative-->
247 </body>
248 </html>
249 <!-- Keep this comment at the end of the file
250 Local variables:
251 mode: sgml
252 sgml-declaration:"~/SGML/HTML4.decl"
253 sgml-default-doctype-name:"html"
254 sgml-minimize-attributes:t
255 sgml-nofill-elements:("pre" "style" "br")
256 End:
257 -->
