css-style-attr/Overview.src.html@0bc709e6bef5
css-style-attr/Overview.src.html
Thu, 04 Apr 2013 18:10:11 -0700
- author
- L. David Baron <dbaron@dbaron.org>
- date
- Thu, 04 Apr 2013 18:10:11 -0700
- changeset 7921
- 0bc709e6bef5
- parent 7857
- 23b4eae0ebde
- child 8243
- 4696787da066
- permissions
- -rwxr-xr-x
Fix double-brackets (an escaped set and an incorrectly unescaped set) in the feedback mailto: URLs.
This fixes a mistake introduced in:
changeset: 7856:589545d6b465
user: Tab Atkins Jr. <jackalmage@gmail.com>
date: Thu Mar 28 18:31:31 2013 -0700
summary: Change feedback shortnames.
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 </head>
11 <div class="head">
12 <!--logo-->
14 <h1>CSS Style Attributes</h1>
16 <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
17 <dl>
18 <dt>This version:</dt>
19 <!-- <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> -->
20 <dd><a href="http://dev.w3.org/csswg/css-style-attr/">http://dev.w3.org/csswg/css-style-attr/</a>
21 </dd>
22 <dt>Latest version:
23 <dd><a href="http://www.w3.org/TR/css-style-attr">http://www.w3.org/TR/css-style-attr</a>
24 <dt>Previous version:
25 <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>
26 <dt>Feedback:
27 <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-style-attr%5D%20feedback">www-style@w3.org</a>
28 with subject line “<kbd>[css-style-attr] <var>… message topic …</var></kbd>”
29 (<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/">archives</a>)
30 <dt>Editors:
31 <dd class="vcard"><a lang="tr" class="fn url" href="http://tantek.com/">Tantek Çelik</a>
32 (<span class="company role url">Invited Expert</span>,
33 formerly <a href="http://www.microsoft.com/">Microsoft Corporation</a>)
34 <<a class="email"
35 href="mailto:tantek@cs.stanford.edu">tantek@cs.stanford.edu</a>>
36 </dd>
37 <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>)
38 </dd>
39 <dt>Previous Editors:
40 <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>>
41 </dd>
42 <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>>
43 </dd>
44 </dl>
45 <!--begin-copyright-->
46 <p>[Here will be included the file "../copyright.inc"]</p>
47 <!--end-copyright-->
49 <hr title="Separator for header">
50 </div>
52 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
54 <p>Markup languages such as HTML [[HTML401]] and SVG [[SVG11]] provide a style
55 attribute on most elements, to hold inline style information that applies
56 to those elements. One of the possible style sheet languages is CSS. This
57 draft describes the syntax and interpretation of the CSS fragment that can
58 be used in such style attributes.
60 <h2 class="no-num no-toc" id="status">Status of this document</h2>
61 <!--status-->
62 <p>For this specification to exit the CR stage, the following conditions
63 shall be met:
65 <ol>
66 <li>
67 <p>There must be at least two interoperable implementations. For the
68 purposes of this criterion, we define the following terms:</p>
70 <dl>
71 <dt>interoperable
73 <dd>
74 <p>passing the respective test case(s) in the <a
75 href="http://www.w3.org/Style/CSS/Test/">CSS test suite</a>, or, if
76 the implementation is not a Web browser, an equivalent test. Every
77 relevant test in the test suite should have an equivalent test created
78 if such a user agent (UA) is to be used to claim interoperability. In
79 addition if such a UA is to be used to claim interoperability, then
80 there must one or more additional UAs which can also pass those
81 equivalent tests in the same way for the purpose of interoperability.
82 The equivalent tests must be made publicly available for the purposes
83 of peer review.</p>
85 <dt>implementation
87 <dd>
88 <p>a user agent which:</p>
90 <ol>
91 <li>implements the specification.
93 <li>is available (i.e. publicly downloadable or available through some
94 other public point of sale mechanism). This is the "show me"
95 requirement.
97 <li>is shipped, or is a "nightly build" (i.e., a development version
98 for the next release), but is not experimental (i.e., a version
99 specifically designed to pass the test suite and not intended for
100 daily usage going forward).
101 </ol>
102 </dl>
104 <li>
105 <p>A minimum of three months of the CR period must elapse. That
106 is, this specification will not exit CR before (DATE OF PUBLICATION PLUS THREE MONTHS). When the
107 specification exits CR, an implementation report will be published. At
108 this point, no such report exists.</p>
109 </ol>
111 <p>A CSS Style Attributes <a href="http://www.w3.org/Style/CSS/Test/">Test
112 Suite</a> will be developed during the Candidate Recommendation phase of
113 this CSS Style Attributes specification.
115 <h2 class="no-num no-toc" id="contents">Table of contents</h2>
116 <!--toc-->
118 <h2 id="intro">Introduction</h2>
120 <p>Some document formats have a <dfn>style attribute</dfn> to permit
121 the author to directly apply style information to specific elements
122 in documents. If a document format defines a style attribute (whether named 'style' or something else) and the
123 attribute accepts CSS as its value, then this specification defines that
124 <dfn>style attribute</dfn>’s syntax and interpretation.
126 <div class="example">
127 <p>The following example shows the use of the <code>style</code> attribute
128 in HTML [[HTML401]]:</p>
129 <pre><p style="<em>color: #090; line-height: 1.2</em>">...</p></pre>
130 </div>
132 <h2 id="conformance">Conformance</h2>
134 <p>A document or implementation cannot conform to CSS Style Attributes alone, but can claim conformance to CSS Style Attributes
135 if it satisfies the conformance requirements in this specification when
136 implementing CSS together with style attribute handling as defined in a
137 document language that has one or more CSS style attributes.</p>
139 <p>Conformance to CSS Style Attributes is defined for two
140 classes:
141 <dl>
142 <dt><dfn>document</dfn></dt>
143 <dd>A document represented in a document language that defines a style
144 attribute for one or more of its elements.
145 <dt><dfn>interpreter</dfn></dt>
146 <dd>Someone or something that interprets the semantics of a document and
147 its associated style information.
148 (Most CSS <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">user
149 agents</a> fall under this category.)</dd>
150 </dl>
152 <p>The conformance requirements are expressed with a combination of
153 descriptive assertions and RFC 2119 terminology. The key words "MUST",
154 "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
155 "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
156 document are to be interpreted as described in RFC 2119.
157 However, for readability, these words do not appear in all uppercase
158 letters in this specification. All of the text of this specification is
159 normative except sections explicitly marked as non-normative, examples,
160 and notes. [[!RFC2119]]</p>
162 <p>Examples in this specification are introduced with the words "for example"
163 or are set apart from the normative text with <code>class="example"</code>,
164 like this:
166 <div class="example">
167 <p>This is an example of an informative example.</p>
168 </div>
170 <p>Informative notes begin with the word "Note" and are set apart from the
171 normative text with <code>class="note"</code>, like this:
173 <p class="note">Note, this is an informative note.</p>
175 <h2 id="syntax">Syntax and Parsing</h2>
177 <p>The value of the style attribute must match the syntax of the contents of
178 a CSS <a href="http://www.w3.org/TR/CSS21/syndata.html#rule-sets">declaration
179 block</a> (excluding the delimiting braces), whose formal grammar is given
180 below in the terms and conventions of the
181 <a href="http://www.w3.org/TR/CSS21/syndata.html#syntax">CSS core grammar</a>:
183 <pre>
184 declaration-list
185 : S* declaration? [ ';' S* declaration? ]*
186 ;
187 </pre>
189 <p class="note">Note that following the CSS2.1 convention, comment tokens
190 are not shown in the rule above.
192 <p>The interpreter must parse the style attribute's value using the
193 same forward-compatible parsing rules that apply to parsing declaration block
194 contents in a normal CSS style sheet. See
195 <a href="http://www.w3.org/TR/CSS21/syndata.html">chapter 4 of the CSS2.1
196 specification</a> for details. [[!CSS21]]
198 <p class="note">Note that because there is no open brace delimiting the
199 declaration list in the CSS style attribute syntax, a close brace
200 (<code>}</code>) in the style attribute's value does not terminate the
201 style data: it is merely an invalid token.</p>
203 <h2 id="interpret">Cascading and Interpretation</h2>
205 <p>The declarations in a style attribute apply to the element to which
206 the attribute belongs. In the cascade, these declarations are considered
207 to have author origin and a specificity higher than any selector.
208 CSS2.1 <a href="http://www.w3.org/TR/CSS21/cascade.html#specificity">defines</a>
209 how style sheets and style attributes are cascaded together. [[!CSS21]]
210 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
211 defined) when the attribute's value is parsed<!-- so dynamic changes to
212 the base URL don't affect the CSS ~Hixie -->.
214 <p>Aside from the differences in cascading, the declarations in a style
215 attribute must be interpreted exactly as if they were given in a CSS
216 style rule that applies to the element.
218 <p>The CSS Working Group strongly recommends that document languages do
219 not allow multiple CSS style attributes on a single element. If a document
220 language allows multiple CSS style attributes, each must be parsed
221 independently and treated as a separate style rule, the ordering of which
222 should be defined by the document language, else is undefined.
224 <h2 id="ack">Acknowledgments</h2>
226 <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>,
227 <span class="vcard"><span class="fn">Björn Höhrmann</span></span>.
228 </p>
230 <h2 id="references">References
232 <h3 class="no-num" id="normative-references">Normative references</h3>
234 <!--begin-normative-->
235 <p>[Here will be inserted the file "normative.inc"]</p>
236 <!--end-normative-->
238 <h3 class="no-num" id="informative-references">Informative references</h3>
240 <!--begin-informative-->
241 <p>[Here will be inserted the file "informative.inc"]</p>
242 <!--end-informative-->
244 </body>
245 </html>
246 <!-- Keep this comment at the end of the file
247 Local variables:
248 mode: sgml
249 sgml-declaration:"~/SGML/HTML4.decl"
250 sgml-default-doctype-name:"html"
251 sgml-minimize-attributes:t
252 sgml-nofill-elements:("pre" "style" "br")
253 End:
254 -->
