You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
simplify title "CSS Styling Attributes Level 1" to "CSS Style Attributes" to reduce chance of unnecessary developer confusion (why "styling" vs "style"?). Make respective changes in body text. Add parenthetical note that style attribute may be named 'style' or something else.
</dt><ddclass="vcard"><aclass="fn url" href="http://tantek.com/" lang="tr">Tantek Çelik</a> (<spanclass="company role url">invited
40
+
expert</span>, and before at <ahref="http://www.microsoft.com/">Microsoft Corporation</a>) <<aclass="email" href="mailto:tantek@cs.stanford.edu">tantek@cs.stanford.edu</a>>
41
+
42
+
</dd><ddclass="vcard"><aclass="fn n url" href="http://fantasai.inkedblade.net/contact"><spanclass="given-name">Elika</span><abbrclass="additional-name">J.</abbr>
Consortium">W3C</acronym></a><sup>®</sup> (<ahref="http://www.csail.mit.edu/"><acronymtitle="Massachusetts Institute
55
+
of Technology">MIT</acronym></a>, <ahref="http://www.ercim.eu/"><acronymtitle="European Research Consortium for Informatics and
56
+
Mathematics">ERCIM</acronym></a>, <ahref="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <ahref="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<p>Markup languages such as HTML <ahref="#HTML401" rel="biblioentry">[HTML401]<!--{{HTML401}}--></a> and SVG <ahref="#SVG11" rel="biblioentry">[SVG11]<!--{{SVG11}}--></a> provide a style attribute on
67
+
most elements, to hold inline style information that applies to those
68
+
elements. One of the possible style sheet languages is CSS. This draft
69
+
describes the
B3F3
syntax and interpretation of the CSS fragment that can be
70
+
used in such style attributes.
71
+
72
+
</p><h2class="no-num no-toc" id="status">Status of this document</h2>
73
+
<!--begin-status-->
74
+
75
+
<p>This is a public copy of the editors' draft. It is provided for
76
+
discussion only and may change at any moment. Its publication here does
77
+
not imply endorsement of its contents by W3C. Don't cite this document
78
+
other than as work in progress.
79
+
80
+
</p><p>The (<ahref="http://lists.w3.org/Archives/Public/www-style/">archived</a>) public
81
+
mailing list <ahref="mailto:www-style@w3.org?Subject=%5Bcss-style-attr%5D%20PUT%20SUBJECT%20HERE">
82
+
www-style@w3.org</a> (see <ahref="http://www.w3.org/Mail/Request">instructions</a>) is preferred for
83
+
discussion of this specification. When sending e-mail, please put the text
84
+
“css-style-attr” in the subject, preferably like this:
85
+
“[<!---->css-style-attr<!---->] <em>…summary of
86
+
comment…</em>”
87
+
88
+
</p><p>This document was produced by the <ahref="http://cgi.w3.org/Style/CSS/members">CSS
89
+
Working Group</a> (part of the <ahref="http://cgi.w3.org/Style/">Style Activity</a>).
90
+
91
+
</p><p>This document was produced by a group operating under the <ahref="http://cgi.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent
92
+
Policy</a>. W3C maintains a <ahref="http://cgi.w3.org/2004/01/pp-impl/32061/status" rel="disclosure">public list of any patent disclosures</a> made in
93
+
connection with the deliverables of the group; that page also includes
94
+
instructions for disclosing a patent. An individual who has actual
95
+
knowledge of a patent which the individual believes contains <ahref="http://cgi.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
96
+
Claim(s)</a> must disclose the information in accordance with <ahref="http://cgi.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the
97
+
W3C Patent Policy</a>.</p>
98
+
<!--end-status-->
99
+
100
+
<p>For this specification to exit the CR stage, the following conditions
101
+
shall be met:
102
+
103
+
</p><ol>
104
+
<li>
105
+
<p>There must be at least two interoperable implementations. For the
106
+
purposes of this criterion, we define the following terms:</p>
107
+
108
+
<dl>
109
+
<dt>interoperable
110
+
111
+
</dt><dd>
112
+
<p>passing the respective test case(s) in the <ahref="http://www.w3.org/Style/CSS/Test/">CSS test suite</a>, or, if
113
+
the implementation is not a Web browser, an equivalent test. Every
114
+
relevant test in the test suite should have an equivalent test created
115
+
if such a user agent (UA) is to be used to claim interoperability. In
116
+
addition if such a UA is to be used to claim interoperability, then
117
+
there must one or more additional UAs which can also pass those
118
+
equivalent tests in the same way for the purpose of interoperability.
119
+
The equivalent tests must be made publicly available for the purposes
120
+
of peer review.</p>
121
+
122
+
</dd><dt>implementation
123
+
124
+
</dt><dd>
125
+
<p>a user agent which:</p>
126
+
127
+
<ol>
128
+
<li>implements the specification.
129
+
130
+
</li><li>is available (i.e. publicly downloadable or available through some
131
+
other public point of sale mechanism). This is the "show me"
132
+
requirement.
133
+
134
+
</li><li>is shipped, or is a "nightly build" (i.e., a development version
135
+
for the next release), but is not experimental (i.e., a version
136
+
specifically designed to pass the test suite and not intended for
137
+
daily usage going forward).
138
+
</li></ol>
139
+
</dd></dl>
140
+
141
+
</li><li>
142
+
<p>A minimum of three months of the CR period must elapse. That is, this
143
+
specification will not exit CR before (DATE OF PUBLICATION PLUS THREE
144
+
MONTHS). When the specification exits CR, an implementation report will
145
+
be published. At this point, no such report exists.</p>
0 commit comments