css-style-attr/Overview.src.html

Mon, 13 Sep 2010 21:35:33 +0000

author
Tantek Çelik <tantek@cs.standford.edu>
date
Mon, 13 Sep 2010 21:35:33 +0000
changeset 1958
95fb75eb6487
parent 1953
41226843561b
child 1989
38b148685084
permissions
-rwxr-xr-x

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.

     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>Editors:
    27     <dd class="vcard"><a lang="tr" class="fn url" href="http://tantek.com/">Tantek &Ccedil;elik</a>
    28 (<span class="company role url">invited expert</span>,
    29 and before at <a href="http://www.microsoft.com/">Microsoft Corporation</a>)
    30      &lt;<a class="email"
    31 href="mailto:tantek@cs.stanford.edu">tantek@cs.stanford.edu</a>&gt;
    32     </dd>
    33     <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>)
    34     </dd>
    35   <dt>Previous Editors:
    36     <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>), &lt;<a class="email" href="mailto:bert@w3.org">bert@w3.org</a>&gt;
    37     </dd>
    38     <dd class="vcard"><span class="fn">Marc Attinasi</span> (<span class="org">AOL/Netscape</span>), &lt;<a class="email" href="mailto:attinasi@netscape.com">attinasi@netscape.com</a>&gt;
    39     </dd>
    40 </dl>
    41 <!--begin-copyright-->
    42 <p>[Here will be included the file "../copyright.inc"]</p>
    43 <!--end-copyright-->
    45 <hr title="Separator for header">
    46 </div>
    48 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
    50 <p>Markup languages such as HTML [[HTML401]] and SVG [[SVG11]] provide a style
    51 attribute on most elements, to hold inline style information that applies
    52 to those elements. One of the possible style sheet languages is CSS. This
    53 draft describes the syntax and interpretation of the CSS fragment that can
    54 be used in such style attributes.
    56 <h2 class="no-num no-toc" id="status">Status of this document</h2>
    57 <!--status-->
    58   <p>For this specification to exit the CR stage, the following conditions
    59    shall be met:
    61   <ol>
    62    <li>
    63     <p>There must be at least two interoperable implementations. For the
    64      purposes of this criterion, we define the following terms:</p>
    66     <dl>
    67      <dt>interoperable
    69      <dd>
    70       <p>passing the respective test case(s) in the <a
    71        href="http://www.w3.org/Style/CSS/Test/">CSS test suite</a>, or, if
    72        the implementation is not a Web browser, an equivalent test. Every
    73        relevant test in the test suite should have an equivalent test created
    74        if such a user agent (UA) is to be used to claim interoperability. In
    75        addition if such a UA is to be used to claim interoperability, then
    76        there must one or more additional UAs which can also pass those
    77        equivalent tests in the same way for the purpose of interoperability.
    78        The equivalent tests must be made publicly available for the purposes
    79        of peer review.</p>
    81      <dt>implementation
    83      <dd>
    84       <p>a user agent which:</p>
    86       <ol>
    87        <li>implements the specification.
    89        <li>is available (i.e. publicly downloadable or available through some
    90         other public point of sale mechanism). This is the "show me"
    91         requirement.
    93        <li>is shipped, or is a "nightly build" (i.e., a development version
    94         for the next release), but is not experimental (i.e., a version
    95         specifically designed to pass the test suite and not intended for
    96         daily usage going forward).
    97       </ol>
    98     </dl>
   100    <li>
   101     <p>A minimum of three months of the CR period must elapse. That
   102      is, this specification will not exit CR before (DATE OF PUBLICATION PLUS THREE MONTHS). When the
   103      specification exits CR, an implementation report will be published. At
   104      this point, no such report exists.</p>
   105   </ol>
   107   <p>A CSS Style Attributes <a href="http://www.w3.org/Style/CSS/Test/">Test
   108    Suite</a> will be developed during the Candidate Recommendation phase of
   109    this CSS Style Attributes specification.
   111 <h2 class="no-num no-toc" id="contents">Table of contents</h2>
   112 <!--toc-->
   114 <h2 id="intro">Introduction</h2>
   116 <p>Some document formats have a <dfn>style attribute</dfn> to permit
   117 the author to directly apply style information to specific elements
   118 in documents. If a document format defines a style attribute (whether named 'style' or something else) and the
   119 attribute accepts CSS as its value, then this specification defines that
   120 <dfn>style attribute</dfn>&rsquo;s syntax and interpretation.
   122 <div class="example">
   123   <p>The following example shows the use of the <code>style</code> attribute
   124   in HTML [[HTML401]]:</p>
   125   <pre>&lt;p style="<em>color: #090; line-height: 1.2</em>"&gt;...&lt;/p&gt;</pre>
   126 </div>
   128 <h2 id="conformance">Conformance</h2>
   130 <p>A document or implementation cannot conform to CSS Style Attributes alone, but can claim conformance to CSS Style Attributes
   131 if it satisfies the conformance requirements in this specification when
   132 implementing CSS together with style attribute handling as defined in a
   133 document language that has one or more CSS style attributes.</p>
   135 <p>Conformance to CSS Style Attributes is defined for two
   136 classes:
   137 <dl>
   138   <dt><dfn>document</dfn></dt>
   139     <dd>A document represented in a document language that defines a style
   140       attribute for one or more of its elements.
   141   <dt><dfn>interpreter</dfn></dt>
   142     <dd>Someone or something that interprets the semantics of a document and
   143       its associated style information.
   144       (Most CSS <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">user
   145       agents</a> fall under this category.)</dd>
   146 </dl>
   148 <p>The conformance requirements are expressed with a combination of
   149   descriptive assertions and RFC 2119 terminology. The key words "MUST",
   150   "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
   151   "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
   152   document are to be interpreted as described in RFC 2119.
   153   However, for readability, these words do not appear in all uppercase
   154   letters in this specification. All of the text of this specification is
   155   normative except sections explicitly marked as non-normative, examples,
   156   and notes. [[!RFC2119]]</p>
   158 <p>Examples in this specification are introduced with the words "for example"
   159   or are set apart from the normative text with <code>class="example"</code>,
   160   like this:
   162 <div class="example">
   163   <p>This is an example of an informative example.</p>
   164 </div>
   166 <p>Informative notes begin with the word "Note" and are set apart from the
   167   normative text with <code>class="note"</code>, like this:
   169 <p class="note">Note, this is an informative note.</p>
   171 <h2 id="syntax">Syntax and Parsing</h2>
   173 <p>The value of the style attribute must match the syntax of the contents of
   174 a CSS <a href="http://www.w3.org/TR/CSS21/syndata.html#rule-sets">declaration
   175 block</a> (excluding the delimiting braces), whose formal grammar is given
   176 below in the terms and conventions of the
   177 <a href="http://www.w3.org/TR/CSS21/syndata.html#syntax">CSS core grammar</a>:
   179 <pre>
   180 declaration-list
   181   : S* declaration? [ ';' S* declaration? ]*
   182   ;
   183 </pre>
   185 <p class="note">Note that following the CSS2.1 convention, comment tokens
   186 are not shown in the rule above.
   188 <p>The interpreter must parse the style attribute's value using the
   189 same forward-compatible parsing rules that apply to parsing declaration block
   190 contents in a normal CSS style sheet. See
   191 <a href="http://www.w3.org/TR/CSS21/syndata.html">chapter 4 of the CSS2.1
   192 specification</a> for details. [[!CSS21]]
   194 <p class="note">Note that because there is no open brace delimiting the
   195 declaration list in the CSS style attribute syntax, a close brace
   196 (<code>}</code>) in the style attribute's value does not terminate the
   197 style data: it is merely an invalid token.</p>
   199 <h2 id="interpret">Cascading and Interpretation</h2>
   201 <p>The declarations in a style attribute apply to the element to which
   202 the attribute belongs. In the cascade, these declarations are considered
   203 to have author origin and a specificity higher than any selector.
   204 CSS2.1 <a href="http://www.w3.org/TR/CSS21/cascade.html#specificity">defines</a>
   205 how style sheets and style attributes are cascaded together. [[!CSS21]]
   206 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
   207 defined) when the attribute's value is parsed<!-- so dynamic changes to
   208 the base URL don't affect the CSS ~Hixie -->.
   210 <p>Aside from the differences in cascading, the declarations in a style
   211 attribute must be interpreted exactly as if they were given in a CSS
   212 style rule that applies to the element.
   214 <p>The CSS Working Group strongly recommends that document languages do
   215 not allow multiple CSS style attributes on a single element. If a document
   216 language allows multiple CSS style attributes, each must be parsed
   217 independently and treated as a separate style rule, the ordering of which
   218 should be defined by the document language, else is undefined.
   220 <h2 id="ack">Acknowledgments</h2>
   222 <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>,
   223 <span class="vcard"><span class="fn">Bj&ouml;rn H&ouml;hrmann</span></span>.
   224 </p>
   226 <h2 id="references">References
   228 <h3 class="no-num" id="normative-references">Normative references</h3>
   230 <!--begin-normative-->
   231 <p>[Here will be inserted the file "normative.inc"]</p>
   232 <!--end-normative-->
   234 <h3 class="no-num" id="informative-references">Informative references</h3>
   236 <!--begin-informative-->
   237 <p>[Here will be inserted the file "informative.inc"]</p>
   238 <!--end-informative-->
   240 </body>
   241 </html>
   242 <!-- Keep this comment at the end of the file
   243 Local variables:
   244 mode: sgml
   245 sgml-declaration:"~/SGML/HTML4.decl"
   246 sgml-default-doctype-name:"html"
   247 sgml-minimize-attributes:t
   248 sgml-nofill-elements:("pre" "style" "br")
   249 End:
   250 -->

mercurial