Skip to content


Subversion checkout URL

You can clone with
Download ZIP
branch: master
Fetching contributors…

Cannot retrieve contributors at this time

468 lines (375 sloc) 17.148 kb
<!DOCTYPE html public '-//W3C//DTD HTML 4.01//EN'
<html lang="en">
<head profile="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>CSS TEMPLATE Module Level N</title>
<link rel="stylesheet" type="text/css" href="../default.css">
<link rel="stylesheet" type="text/css"
<style type="text/css">
/* delete this block when you've cleared out all the .replaceme elements */
.replaceme {
border: solid red;
padding: 0 0.5em;
margin: 0 0.1em;
background: yellow;
color: green;
.replaceme:before {
content: "FIXME(";
color: black;
.replaceme:after {
content: ")";
color: black;
<div class="head">
<h1>CSS Display Module Level 3</h1>
<h2 class="no-num no-toc">PROPOSAL [DATE]</h2>
<dt>This version:
<dd><a href="[VERSION]" class="replaceme">[YEAR]/ED-cssN-FIXME-[CDATE]/</a>
<dt>Latest version:
<dd><a href="[SHORTNAME]/">[SHORTNAME]/</a>
<dt>Editor's draft:
<dd><a href="[SHORTNAME]/">[SHORTNAME]/</var></a>
<dt>Previous version:
<dd><a href=""></a>
<dt>Issues List:</dt>
<dd><a href=""></a>
<dd><a href=""></a> with subject line &ldquo;<kbd>[[SHORTNAME]] <var>&hellip; message topic &hellip;</var></kbd>&rdquo;
<dd class=vcard><span class=fn>[editor1 name]</span>,
<span class=org>[affiliation (opt.)]</span>,
<span class=email>[email address (opt.)]</span>
<dd class=vcard><span class=fn>[editor2 name]</span>,
<span class=org>[affiliation (opt.)]</span>,
<span class=email>[email address (opt.)]</span>
<hr title="Separator for header">
<h2 class="no-num no-toc" id="abstract">Abstract</h2>
<p>CSS is a language for describing the rendering of structured documents
(such as HTML and XML) on screen, on paper, in speech, etc. This module
contains the features of CSS level&nbsp;3 relating to <var class="replaceme">DESCRIBE HERE</var>.
It includes and extends the functionality of CSS level&nbsp;2 [[!CSS21]],
which builds on CSS level&nbsp;1 [[CSS1]].
The main extensions compared to level&nbsp;2 are <var class="replaceme">SUMMARIZE HERE</var>.
<h2 class="no-num no-toc" id="status">Status of this document</h2>
<p>The following features are at risk: &hellip;
<h2 class="no-num no-toc" id="contents">
Table of contents</h2>
<h2 id="intro">
<p><em>This section is not normative.</em>
<p><var class="replaceme">Provide background, motivation, etc.</var></p>
<h3 id="placement">
Module interactions</h3>
<p class="replaceme">Explain, normatively, how this module affects the definition of CSS.</p>
<p>This module replaces and extends the <var class="replaceme">SUMMARIZE HERE</var>
features defined in [[!CSS21]] sections <var class="replaceme">W.X and Y.Z</var>.
<h3 id="values">
<p>This specification follows the
<a href="">CSS property
definition conventions</a> from [[!CSS21]]. Value types not defined in
this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
Other CSS modules may expand the definitions of these value types: for
example [[CSS3COLOR]], when combined with this module, expands the
definition of the &lt;color&gt; value type as used in this specification.</p>
<p>In addition to the property-specific values listed in their definitions,
all properties defined in this specification also accept the
<a href="">inherit</a>
keyword as their property value. For readability it has not been repeated
<h2 id="sample-topic">
The 'display' property</h2>
<p>Look at the mark-up in this section for examples. See the <a
href="">documentation</a> for more precise instructions. The
companion of this template shows the <a href="Overview.html">processed
<p>To refer to HTML, use [[HTML40]] (note the double square brackets). To
make a normative reference, insert a &ldquo;!&rdquo;, like this:
[[!CSS3SYN]] The currently available
<a href="">list of bibliographic data</a>
can of course be extended.</p>
<p>We write about a property such as 'display-model' like this and
about a piece of CSS code like this: ''foo: bar''. Inline HTML and XML
are similar, but use the CODE element: <code
class=html>&lt;blockquote&gt;...&lt;/blockquote&gt;</code> and <code
<p class=note>Note that the property will automatically be linked to its
<p>To put <span class=index>terms</span> into the <span
class=index-def>index</span>, there are many <span class=index
title="variant">variants</span>, but hopefully the <span class=index
title="simple|simpler|simplest">simplest</span> will be the most <span
class=index title="frequency::common">common</span>. But a little more
<span class=index title="work|resource::time spent">work</span> now
will help many people for a long time.
<p class=note>Note that you can add non-normative notes like this.
<p>Of course, multi-paragraph notes are also possible: just enclose them in a
<div class=note>
<p>Note that this note is a multi-paragraph note.</p>
<p>It doesn't <em>need</em> to have two paragraphs, but it could.</p>
<p>Displayed examples come in eight different types: CSS examples that need
no separate paragraph of explanation are put in a simple PRE:
<pre class=example>EM { font-style: italic }</pre>
<p>CSS examples that need extra text need a DIV.</p>
<div class=example>
<p>The following example is the same as the previous one, but now it is
<pre>EM { font-style: italic }</pre>
<p>Illegal CSS examples (examples of errors) are the same, but with class
"illegal example". Examples of HTML and XML code have class "html" and "xml"
respectively, but are otherwise ditto.</p>
<p>A formal definition of a property looks like this:</p>
<h3 id="the-display-model">
Internal display model: the 'display-inside' property</h3>
<table class=propdef>
<th><a href="#values">Value</a>:
<td>inline-inside | block-inside | table | ruby | icon
<th>Applies to:
<td>all elements
<td>specified value
<th>Canonical order:
<td><abbr title="follows order of property value definition">per grammar<abbr>
<dd>Define values using a DL
<p><dfn>Cross-references</dfn> are created by enclosing a term or phrase in
&lt;dfn&gt; (like the word <em>cross-references</em> earlier in this
sentence). Then any element with the same content will automatically be
linked. For example: <span>cross-references</span>.</p>
<p>And a figure with a caption is done like this:
<div class=figure>
<p><img src="corner.png"
alt="A table with a caption above it; both have margins and the margins between them are collapsed, as is normal for vertical margins.">
<p class=caption>Just a random image. SVG would be nice, but maybe SVG
isn't sufficiently easy to use yet. W3C prefers PNG over GIF (obviously,
since PNG is a W3C Rec).
<p>Don't forget to write the longdesc.
<p class=issue>An open issue or editorial remark is OK in a WD, but
they should be resolved/removed before the document goes to
&ldquo;CR&rdquo; (Candidate Recommendation). Use
<h2 id="conformance">
<h3 id="conventions">
Document conventions</h3>
<p>Conformance requirements are expressed with a combination of
descriptive assertions and RFC 2119 terminology. The key words “MUST”,
“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.
<p>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>
<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>
<h3 id="conformance-classes">
Conformance classes</h3>
<p>Conformance to <var class="replaceme">CSS TEMPLATE Module</var>
is defined for three conformance classes:
<dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
<dd>A <a href="">CSS
style sheet</a>.
<dd>A <a href="">UA</a>
that interprets the semantics of a style sheet and renders
documents that use them.
<dt><dfn id="authoring-tool">authoring tool</dfn></dt>
<dd>A <a href="">UA</a>
that writes a style sheet.
<p>A style sheet is conformant to <var class="replaceme">CSS TEMPLATE Module</var>
if all of its statements that use syntax defined in this module are valid
according to the generic CSS grammar and the individual grammars of each
feature defined in this module.
<p>A renderer is conformant to <var class="replaceme">CSS TEMPLATE Module</var>
if, in addition to interpreting the style sheet as defined by the
appropriate specifications, it supports all the features defined
by <var class="replaceme">CSS TEMPLATE Module</var> by parsing them correctly
and rendering the document accordingly. However, the inability of a
UA to correctly render a document due to limitations of the device
does not make the UA non-conformant. (For example, a UA is not
required to render color on a monochrome monitor.)
<p>An authoring tool is conformant to <var class="replaceme">CSS TEMPLATE Module</var>
if it writes style sheets that are syntactically correct according to the
generic CSS grammar and the individual grammars of each feature in
this module, and meet all other conformance requirements of style sheets
as described in this module.
<h3 id="partial">
Partial implementations</h3>
<p>So that authors can exploit the forward-compatible parsing rules to
assign fallback values, CSS renderers <strong>must</strong>
treat as invalid (and <a href="">ignore
as appropriate</a>) any at-rules, properties, property values, keywords,
and other syntactic constructs for which they have no usable level of
support. In particular, user agents <strong>must not</strong> selectively
ignore unsupported component values and honor supported values in a single
multi-value property declaration: if any value is considered invalid
(as unsupported values must be), CSS requires that the entire declaration
be ignored.</p>
<h3 id="experimental">
Experimental implementations</h3>
<p>To avoid clashes with future CSS features, the CSS2.1 specification
reserves a <a href="">prefixed
syntax</a> for proprietary and experimental extensions to CSS.
<p>Prior to a specification reaching the Candidate Recommendation stage
in the W3C process, all implementations of a CSS feature are considered
experimental. The CSS Working Group recommends that implementations
use a vendor-prefixed syntax for such features, including those in
W3C Working Drafts. This avoids incompatibilities with future changes
in the draft.
<h3 id="testing">
Non-experimental implementations</h3>
<p>Once a specification reaches the Candidate Recommendation stage,
non-experimental implementations are possible, and implementors should
release an unprefixed implementation of any CR-level feature they
can demonstrate to be correctly implemented according to spec.
<p>To establish and maintain the interoperability of CSS across
implementations, the CSS Working Group requests that non-experimental
CSS renderers submit an implementation report (and, if necessary, the
testcases used for that implementation report) to the W3C before
releasing an unprefixed implementation of any CSS features. Testcases
submitted to W3C are subject to review and correction by the CSS
Working Group.
<p>Further information on submitting testcases and implementation reports
can be found from on the CSS Working Group's website at
<a href=""></a>.
Questions should be directed to the
<a href=""></a>
mailing list.
<h3 id="cr-exit-criteria">
CR exit criteria</h3>
<p class=issue>[Change or remove the following CR exit criteria if
the spec is not a module, but, e.g., a Note or a profile. This text was <a
href=""> decided on 2008-06-04.</a>]</p>
For this specification to be advanced to Proposed Recommendation,
there must be at least two independent, interoperable implementations
of each feature. Each feature may be implemented by a different set of
products, there is no requirement that all features be implemented by
a single product. For the purposes of this criterion, we define the
following terms:
<dt>independent <dd>each implementation must be developed by a
different party and cannot share, reuse, or derive from code
used by another qualifying implementation. Sections of code that
have no bearing on the implementation of this specification are
exempt from this requirement.
<dt>interoperable <dd>passing the respective test case(s) in the
official CSS test suite, 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.
<dt>implementation <dd>a user agent which:
<ol class=inline>
<li>implements the specification.
<li>is available to the general public. The implementation may
be a shipping product or other publicly available version
(i.e., beta version, preview release, or “nightly build”).
Non-shipping product releases must have implemented the
feature(s) for a period of at least one month in order to
demonstrate stability.
<li>is not experimental (i.e., a version specifically designed
to pass the test suite and is not intended for normal usage
going forward).
<p>The specification will remain Candidate Recommendation for at least
six months.
<h2 class=no-num id="acknowledgments">
<p><var class="replaceme">[acknowledgments]</var></p>
<h2 class=no-num id="references">
<h3 class="no-num" id="normative-references">
Normative references</h3>
<h3 class="no-num" id="other-references">
Other references</h3>
<h2 class="no-num" id="index">
<h2 class="no-num" id="property-index">
Property index</h2>
<!-- properties -->
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-nofill-elements:("pre" "style" "br")
Jump to Line
Something went wrong with that request. Please try again.