drafts: css-style-attr/Overview.src.html@4ce7b66b553a (annotated)

css-style-attr/Overview.src.html@4ce7b66b553a (annotated)

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

 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
 <html lang="en">
 <head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
   <title>CSS Style Attributes</title>
   <link rel="stylesheet" type="text/css" href="../default.css">
   <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED">
   <script defer=defer
     src="http://test.csswg.org/harness/annotate.js#CSS-STYLE-ATTR_DEV"
     type="text/javascript"></script>
 </head>
 <div class="head">
 <!--logo-->
 <h1>CSS Style Attributes</h1>
 <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
 <dl>
   <dt>This version:</dt>
     <!-- <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> -->
     <dd><a href="http://dev.w3.org/csswg/css-style-attr/">http://dev.w3.org/csswg/css-style-attr/</a>
     </dd>
   <dt>Latest version:
     <dd><a href="http://www.w3.org/TR/css-style-attr/">http://www.w3.org/TR/css-style-attr/</a>
   <dt>Previous version:
     <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>
     <dt>Feedback:
       <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-style-attr%5D%20feedback">www-style@w3.org</a>
           with subject line &ldquo;<kbd>[css-style-attr] <var>&hellip; message topic &hellip;</var></kbd>&rdquo;
           (<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/">archives</a>)
   <dt>Editors:
     <dd class="vcard"><a lang="tr" class="fn url" href="http://tantek.com/">Tantek &Ccedil;elik</a>
 (<span class="company role url">Invited Expert</span>,
 formerly <a href="http://www.microsoft.com/">Microsoft Corporation</a>)
      &lt;<a class="email"
 href="mailto:tantek@cs.stanford.edu">tantek@cs.stanford.edu</a>&gt;
     </dd>
     <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>)
     </dd>
   <dt>Previous Editors:
     <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;
     </dd>
     <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;
     </dd>
 </dl>
 <!--begin-copyright-->
 <p>[Here will be included the file "../copyright.inc"]</p>
 <!--end-copyright-->
 <hr title="Separator for header">
 </div>
 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
 <p>Markup languages such as HTML [[HTML401]] and SVG [[SVG11]] provide a style
 attribute on most elements, to hold inline style information that applies
 to those elements. One of the possible style sheet languages is CSS. This
 draft describes the syntax and interpretation of the CSS fragment that can
 be used in such style attributes.
 <h2 class="no-num no-toc" id="status">Status of this document</h2>
 <!--status-->
   <p>For this specification to exit the CR stage, the following conditions
    shall be met:
   <ol>
    <li>
     <p>There must be at least two interoperable implementations. For the
      purposes of this criterion, we define the following terms:</p>
     <dl>
      <dt>interoperable
      <dd>
       <p>passing the respective test case(s) in the <a
        href="http://www.w3.org/Style/CSS/Test/">CSS test suite</a>, or, if
        the implementation is not a Web browser, an equivalent test. Every
        relevant test in the test suite should have an equivalent test created
        if such a user agent (UA) is to be used to claim interoperability. In
        addition if such a UA is to be used to claim interoperability, then
        there must one or more additional UAs which can also pass those
        equivalent tests in the same way for the purpose of interoperability.
        The equivalent tests must be made publicly available for the purposes
        of peer review.</p>
      <dt>implementation
      <dd>
       <p>a user agent which:</p>
       <ol>
        <li>implements the specification.
        <li>is available (i.e. publicly downloadable or available through some
         other public point of sale mechanism). This is the "show me"
         requirement.
        <li>is shipped, or is a "nightly build" (i.e., a development version
         for the next release), but is not experimental (i.e., a version
         specifically designed to pass the test suite and not intended for
         daily usage going forward).
       </ol>
     </dl>
    <li>
     <p>A minimum of three months of the CR period must elapse. That
      is, this specification will not exit CR before (DATE OF PUBLICATION PLUS THREE MONTHS). When the
      specification exits CR, an implementation report will be published. At
      this point, no such report exists.</p>
   </ol>
   <p>A CSS Style Attributes <a href="http://www.w3.org/Style/CSS/Test/">Test
    Suite</a> will be developed during the Candidate Recommendation phase of
    this CSS Style Attributes specification.
 <h2 class="no-num no-toc" id="contents">Table of contents</h2>
 <!--toc-->
 <h2 id="intro">Introduction</h2>
 <p>Some document formats have a <dfn>style attribute</dfn> to permit
 the author to directly apply style information to specific elements
 in documents. If a document format defines a style attribute (whether named 'style' or something else) and the
 attribute accepts CSS as its value, then this specification defines that
 <dfn>style attribute</dfn>&rsquo;s syntax and interpretation.
 <div class="example">
   <p>The following example shows the use of the <code>style</code> attribute
   in HTML [[HTML401]]:</p>
   <pre>&lt;p style="<em>color: #090; line-height: 1.2</em>"&gt;...&lt;/p&gt;</pre>
 </div>
 <h2 id="conformance">Conformance</h2>
 <p>A document or implementation cannot conform to CSS Style Attributes alone, but can claim conformance to CSS Style Attributes
 if it satisfies the conformance requirements in this specification when
 implementing CSS together with style attribute handling as defined in a
 document language that has one or more CSS style attributes.</p>
 <p>Conformance to CSS Style Attributes is defined for two
 classes:
 <dl>
   <dt><dfn>document</dfn></dt>
     <dd>A document represented in a document language that defines a style
       attribute for one or more of its elements.
   <dt><dfn>interpreter</dfn></dt>
     <dd>Someone or something that interprets the semantics of a document and
       its associated style information.
       (Most CSS <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">user
       agents</a> fall under this category.)</dd>
 </dl>
 <p>The conformance requirements are expressed with a combination of
   descriptive assertions and RFC 2119 terminology. The key words "MUST",
   "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
   "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
   document are to be interpreted as described in RFC 2119.
   However, for readability, these words do not appear in all uppercase
   letters in this specification. All of the text of this specification is
   normative except sections explicitly marked as non-normative, examples,
   and notes. [[!RFC2119]]</p>
 <p>Examples in this specification are introduced with the words "for example"
   or are set apart from the normative text with <code>class="example"</code>,
   like this:
 <div class="example">
   <p>This is an example of an informative example.</p>
 </div>
 <p>Informative notes begin with the word "Note" and are set apart from the
   normative text with <code>class="note"</code>, like this:
 <p class="note">Note, this is an informative note.</p>
 <h2 id="syntax">Syntax and Parsing</h2>
 <p>The value of the style attribute must match the syntax of the contents of
 a CSS <a href="http://www.w3.org/TR/CSS21/syndata.html#rule-sets">declaration
 block</a> (excluding the delimiting braces), whose formal grammar is given
 below in the terms and conventions of the
 <a href="http://www.w3.org/TR/CSS21/syndata.html#syntax">CSS core grammar</a>:
 <pre>
 declaration-list
   : S* declaration? [ ';' S* declaration? ]*
   ;
 </pre>
 <p class="note">Note that following the CSS2.1 convention, comment tokens
 are not shown in the rule above.
 <p>The interpreter must parse the style attribute's value using the
 same forward-compatible parsing rules that apply to parsing declaration block
 contents in a normal CSS style sheet. See
 <a href="http://www.w3.org/TR/CSS21/syndata.html">chapter 4 of the CSS2.1
 specification</a> for details. [[!CSS21]]
 <p class="note">Note that because there is no open brace delimiting the
 declaration list in the CSS style attribute syntax, a close brace
 (<code>}</code>) in the style attribute's value does not terminate the
 style data: it is merely an invalid token.</p>
 <h2 id="interpret">Cascading and Interpretation</h2>
 <p>The declarations in a style attribute apply to the element to which
 the attribute belongs. In the cascade, these declarations are considered
 to have author origin and a specificity higher than any selector.
 CSS2.1 <a href="http://www.w3.org/TR/CSS21/cascade.html#specificity">defines</a>
 how style sheets and style attributes are cascaded together. [[!CSS21]]
 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
 defined) when the attribute's value is parsed<!-- so dynamic changes to
 the base URL don't affect the CSS ~Hixie -->.
 <p>Aside from the differences in cascading, the declarations in a style
 attribute must be interpreted exactly as if they were given in a CSS
 style rule that applies to the element.
 <p>The CSS Working Group strongly recommends that document languages do
 not allow multiple CSS style attributes on a single element. If a document
 language allows multiple CSS style attributes, each must be parsed
 independently and treated as a separate style rule, the ordering of which
 should be defined by the document language, else is undefined.
 <h2 id="ack">Acknowledgments</h2>
 <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>,
 <span class="vcard"><span class="fn">Bj&ouml;rn H&ouml;hrmann</span></span>.
 </p>
 <h2 id="references">References
 <h3 class="no-num" id="normative-references">Normative references</h3>
 <!--begin-normative-->
 <p>[Here will be inserted the file "normative.inc"]</p>
 <!--end-normative-->
 <h3 class="no-num" id="informative-references">Informative references</h3>
 <!--begin-informative-->
 <p>[Here will be inserted the file "informative.inc"]</p>
 <!--end-informative-->
 </body>
 </html>
 <!-- Keep this comment at the end of the file
 Local variables:
 mode: sgml
 sgml-declaration:"~/SGML/HTML4.decl"
 sgml-default-doctype-name:"html"
 sgml-minimize-attributes:t
 sgml-nofill-elements:("pre" "style" "br")
 End:
 -->

Mercurial > drafts / annotate

css-style-attr/Overview.src.html@4ce7b66b553a (annotated)

css-style-attr/Overview.src.html