csswg-drafts/css-module-bikeshed/Overview.html at 30ce5fda690f74b16ec1d62f7a70c114810ff1bb · w3c/csswg-drafts · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
<!DOCTYPE html><html lang=en><head>
  <meta content="text/html; charset=utf-8" http-equiv=Content-Type>
  <title>CSS Foo Module Level N</title>
  <link href=../default.css rel=stylesheet type=text/css>
  <link href=../csslogo.ico rel="shortcut icon" type=image/x-icon>
  <link href=https://www.w3.org/StyleSheets/TR/W3C-ED rel=stylesheet type=text/css>
</head>
<body class=h-entry>
<style scoped 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;
}
</style>

<div class=head>
  <p data-fill-with=logo><a class=logo href=http://www.w3.org/>
    <img alt=W3C height=48 src=http://www.w3.org/Icons/w3c_home width=72>
</a></p>
  <h1 class="p-name no-ref" id=title>CSS Foo Module Level N</h1>
  <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft,
    <span class=dt-updated><span class=value-title title=20130912>12 September 2013</span></span></span></h2>
  <div data-fill-with=spec-metadata><dl><dt>This version:<dd><a class=u-url href=http://dev.w3.org/csswg/css-foo/>http://dev.w3.org/csswg/css-foo/</a><dt>Latest version:<dd><a href=http://www.w3.org/TR/css-foo/>http://www.w3.org/TR/css-foo/</a><dt>Editor’s Draft:<dd><a href=http://dev.w3.org/csswg/css-foo/>http://dev.w3.org/csswg/css-foo/</a>
<dt>Feedback:</dt>
    <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-foo%5D%20feedback">www-style@w3.org</a>
        with subject line
        “<kbd>[css-foo] <var>… message topic …</var></kbd>”
        (<a href=http://lists.w3.org/Archives/Public/www-style/ rel=discussion>archives</a>)<dt>Test Suite:<dd>None Yet<dt>Editors:
<dd class="p-author h-card vcard"><a class="p-name fn u-url url" href=http://example.com/contact>Name1</a> (<span class="p-org org">Company1</span>)<dd class="p-author h-card vcard"><a class="p-name fn u-email email" href=mailto:name2@example.com>Name2</a> (<span class="p-org org">Company2</span>)</dl></div>
  <div data-fill-with=warning></div>
  <p class=copyright data-fill-with=copyright><a href=http://www.w3.org/Consortium/Legal/ipr-notice#Copyright>Copyright</a> © 2013 <a href=http://www.w3.org/><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href=http://www.csail.mit.edu/><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href=http://www.ercim.eu/><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href=http://www.keio.ac.jp/>Keio</a>, <a href=http://ev.buaa.edu.cn/>Beihang</a>), All Rights Reserved. W3C <a href=http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer>liability</a>, <a href=http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks>trademark</a> and <a href=http://www.w3.org/Consortium/Legal/copyright-documents>document use</a> rules apply.</p>
  <hr title="Separator for header">
</div>

<h2 class="no-num no-toc no-ref heading settled heading" id=abstract><span class=content>Abstract</span></h2>
<p class=p-summary data-fill-with=abstract>This module introduces the <a class=property data-link-type=propdesc href=#propdef-foo title=foo>foo</a> property and related values, which do bar and baz.
<a href=http://www.w3.org/TR/CSS/>CSS</a> is a language for describing the rendering of structured documents
(such as HTML and XML)
on screen, on paper, in speech, etc.</p>

<h2 class="no-num no-toc no-ref heading settled heading" id=status><span class=content>Status of this document</span></h2>
<div data-fill-with=status><p>
	This is a public copy of the editors' draft.
	It is provided for discussion only and may change at any moment.
	Its publication here does not imply endorsement of its contents by W3C.
	Don’t cite this document other than as work in progress.

<p>
	The (<a href=http://lists.w3.org/Archives/Public/www-style/>archived</a>) public mailing list
	<a href="mailto:www-style@w3.org?Subject=%5Bcss-foo%5D%20PUT%20SUBJECT%20HERE">www-style@w3.org</a>
	(see <a href=http://www.w3.org/Mail/Request>instructions</a>)
	is preferred for discussion of this specification.
	When sending e-mail,
	please put the text “css-foo” in the subject,
	preferably like this:
	“[css-foo] <em>…summary of comment…</em>”

<p>
	This document was produced by the <a href=/Style/CSS/members>CSS Working Group</a>
	(part of the <a href=/Style/>Style Activity</a>).

<p>
	This document was produced by a group operating under
	the <a href=/Consortium/Patent-Policy-20040205/>5 February 2004 W3C Patent Policy</a>.
	W3C maintains a <a href=/2004/01/pp-impl/32061/status rel=disclosure>public list of any patent disclosures</a>
	made in connection with the deliverables of the group;
	that page also includes instructions for disclosing a patent.
	An individual who has actual knowledge of a patent which the individual believes contains <a href=/Consortium/Patent-Policy-20040205/#def-essential>Essential Claim(s)</a>
	must disclose the information in accordance with <a href=/Consortium/Patent-Policy-20040205/#sec-Disclosure>section 6 of the W3C Patent Policy</a>.</div>
<div data-fill-with=at-risk></div>

<h2 class="no-num no-toc no-ref heading settled heading" id=contents><span class=content>Table of contents</span></h2>
<div data-fill-with=table-of-contents><ul class=toc><li><a href=#intro><span class=secno>1</span>
Introduction</a><li><a href=#sample-topic><span class=secno>2</span>
Sample section</a><ul class=toc><li><a href=#the-display-model><span class=secno>2.1</span>
Internal display model: the <span class=property data-link-type=propdesc title=display-inside>display-inside</span> property</a></ul><li><a href=#conformance><span class=secno></span>
Conformance</a><ul class=toc><li><a href=#conventions><span class=secno></span>
Document conventions</a><li><a href=#conformance-classes><span class=secno></span>
Conformance classes</a><li><a href=#partial><span class=secno></span>
Partial implementations</a><li><a href=#experimental><span class=secno></span>
Experimental implementations</a><li><a href=#testing><span class=secno></span>
Non-experimental implementations</a></ul><li><a href=#references><span class=secno></span>
References</a><ul class=toc><li><a href=#normative><span class=secno></span>
Normative References</a><li><a href=#informative><span class=secno></span>
Informative References</a></ul><li><a href=#index><span class=secno></span>
Index</a><li><a href=#property-index><span class=secno></span>
Property index</a><li><a href=#issues-index><span class=secno></span>Issues Index</a></ul></div>


<h2 class="heading settled heading" data-level=1 id=intro><span class=secno>1 </span><span class=content>
Introduction</span><a class=self-link href=#intro></a></h2>

<p>	<em>This section is not normative.</em>

<p>	<var class=replaceme>Provide background, motivation, etc.</var>


<h2 class="heading settled heading" data-level=2 id=sample-topic><span class=secno>2 </span><span class=content>
Sample section</span><a class=self-link href=#sample-topic></a></h2>

<p>	Look at the mark-up in this section for examples.
	See the <a href=https://www.w3.org/Style/Group/css3-src/bin/README>documentation</a> for more precise instructions.
	The companion of this template shows the <a href=Overview.html>processed result</a>.

<p>	To refer to HTML, use <a data-biblio-type=informative data-link-type=biblio href=#html40 title=HTML40>[HTML40]</a> (note the double square brackets).
	To make a normative reference,
	insert a “!”, like this:
	<a data-biblio-type=normative data-link-type=biblio href=#css3syn title=CSS3SYN>[CSS3SYN]</a>
	The currently available <a href=https://www.w3.org/Style/Group/css3-src/biblio.ref>list of bibliographic data</a> can of course be extended.

<p>	We write about a property such as <a class=property data-link-type=propdesc href=#propdef-foo title=foo>foo</a> like this
	and about a piece of CSS code like this: <a class=css data-link-type=maybe href=#propdef-foo title=foo>foo: bar</a>.
	(Note that if it looks like a "property: value",
	it’ll automatically link to the property.)
	Inline HTML and XML are similar,
	but use the CODE element: <code class=html>&lt;blockquote&gt;...&lt;/blockquote&gt;</code>
	and <code class=xml>&lt;r:xyz&gt;...&lt;/r:xyz&gt;</code>.

<p class=note>	Note: Note that the property will automatically be linked to its definition.

<p>	To define <dfn data-dfn-type=dfn data-noexport="" id=terms>terms<a class=self-link href=#terms></a></dfn> into the <dfn data-dfn-type=dfn data-noexport="" id=index0>index<a class=self-link href=#index0></a></dfn>,
	there are many <dfn data-dfn-type=dfn data-noexport="" id=variants title=variant>variants<a class=self-link href=#variants></a></dfn>,
	but hopefully the <dfn data-dfn-type=dfn data-noexport="" id=simplest title=simple|simpler|simplest>simplest<a class=self-link href=#simplest></a></dfn>
	will be the most common.

<p class=note>	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 <a data-link-type=element>div</a>:

	<div class=note>
		Note that this note is a multi-paragraph note.

<p>		It doesn’t <em>need</em> to have two paragraphs, but it could.
	</div>

<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.

	<div class=example>
		The following example is the same as the previous one,
		but now it is explained:

<pre>EM { font-style: italic }</pre>	</div>

<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>	A formal definition of a property looks like this:

<h3 class="heading settled heading" data-level=2.1 id=the-display-model><span class=secno>2.1 </span><span class=content>
Internal display model: the <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-display-3/#display-inside title=display-inside>display-inside</a> property</span><a class=self-link href=#the-display-model></a></h3>

<table class=propdef><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-foo>foo<a class=self-link href=#propdef-foo></a></dfn><tr><th>Value:<td>inline-inside | block-inside | table | ruby | icon<tr><th>Initial:<td>text<tr><th>Applies to:<td>all elements<tr><th>Inherited:<td>no<tr><th>Media:<td>visual<tr><th>Computed value:<td>specified value<tr><th>Canonical order:<td>per grammar<tr><th>Percentages:<td>n/a<tr><th>Animatable:<td>no</table>
	<dl data-dfn-for=foo data-dfn-type=value>
		<dt><dfn class=css-code data-dfn-for=foo data-dfn-type=value data-export="" id=valuedef-value-name>value-name<a class=self-link href=#valuedef-value-name></a></dfn>
		<dd>
			Define values using a <a data-link-type=element>dl</a>.
			Note that the <a data-link-type=element>dl</a> wrapper
			specifies the default <a data-link-type=element>dfn</a> type and what property it’s for,
			so you don’t have to repeat that information in each individual definition.
	</dl>

<p>	<dfn data-dfn-type=dfn data-noexport="" id=cross-references>Cross-references<a class=self-link href=#cross-references></a></dfn> are created by enclosing a term or phrase in &lt;dfn&gt;
	(like the word <a href=#cross-references>cross-references</a> earlier in this sentence).
	Then an &lt;a&gt; without an <code>href=''</code> attribute
	with the same text content will automatically be linked.
	Both &lt;dfn&gt;s and &lt;a&gt;s are typed,
	which allows the same text to appear as different types of terms without a collision.
	The type can often be inferred,
	but sometimes it needs to be specified,
	like when you’re linking to a <a class=idl-code data-link-type=interface href=#dom-foo>Foo</a> WebIDL interface.

<p>	And a figure with a caption is done like this:

	</p><figure>
		<img alt="A table with a caption above it; both have margins and the margins between them are collapsed, as is normal for vertical margins." src=corner.png>
		<figcaption>
			Just a random image.
			Use SVG if you can.
			Otherwise, W3C prefers PNG over GIF (obviously, since PNG is a W3C Rec).
		</figcaption>
	</figure>

<p>	Don’t forget to write the alt.

	<p class=issue id=issue-1383a6cc><a class=self-link href=#issue-1383a6cc></a>
		An open issue or editorial remark is OK in a WD,
		but they should be resolved/removed before the document goes to “CR”
		(Candidate Recommendation).
		Use class=“issue”.

	<p class=issue id=issue-e459e740><a class=self-link href=#issue-e459e740></a>
		Inline issues will be copied into an <a href=#issues-index>Issues Index</a> at the end of the document,
		for easy reference.

	<pre class=idl>/* Write WebIDL in a &lt;pre class="idl"&gt; as plain text. */
  interface <dfn class=idl-code data-dfn-type=interface data-export="" id=dom-foo title=Foo>Foo<a class=self-link href=#dom-foo></a></dfn> {
    readonly attribute DOMString <dfn class=idl-code data-dfn-for=Foo data-dfn-type=attribute data-export="" id=dom-foo-bar title=bar>bar<a class=self-link href=#dom-foo-bar></a></dfn>;
    boolean <dfn class=idl-code data-dfn-for=Foo data-dfn-type=method data-export="" id=dom-foo-baz title=baz()>baz<a class=self-link href=#dom-foo-baz></a></dfn>(<a data-link-type=idl href=#dictdef-foodict>FooDict</a> <dfn class=idl-code data-dfn-for=Foo/baz() data-dfn-type=argument data-export="" id=dom-foobaz-arg1 title=Arg1>Arg1<a class=self-link href=#dom-foobaz-arg1></a></dfn>, (DOMString or <a data-link-type=idl href=#dom-foo>Foo</a>) <dfn class=idl-code data-dfn-for=Foo/baz() data-dfn-type=argument data-export="" id=dom-foobaz-arg2 title=Arg2>Arg2<a class=self-link href=#dom-foobaz-arg2></a></dfn>);
  };

  dictionary <dfn class=idl-code data-dfn-type=dictionary data-export="" id=dictdef-foodict title=FooDict>FooDict<a class=self-link href=#dictdef-foodict></a></dfn> {
    sequence&lt;<a data-link-type=idl href=#dom-foo>Foo</a>&gt; foo;
    boolean bar;
    DOMString baz = "qux";
  };
</pre>
<h2 class="no-ref no-num heading settled heading" id=conformance><span class=content>
Conformance</span><a class=self-link href=#conformance></a></h2>

<h3 class="no-ref heading settled heading" id=conventions><span class=content>
Document conventions</span><a class=self-link href=#conventions></a></h3>

    <p>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.

    <p>All of the text of this specification is normative except sections
    explicitly marked as non-normative, examples, and notes. <a data-biblio-type=normative data-link-type=biblio href=#rfc2119 title=RFC2119>[RFC2119]</a></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>

<h3 class="no-ref heading settled heading" id=conformance-classes><span class=content>
Conformance classes</span><a class=self-link href=#conformance-classes></a></h3>

    <p>Conformance to this specification
    is defined for three conformance classes:
    <dl>
        <dt>style sheet
            <dd>A <a href=http://www.w3.org/TR/CSS21/conform.html#style-sheet>CSS
            style sheet</a>.
        <dt>renderer
            <dd>A <a href=http://www.w3.org/TR/CSS21/conform.html#user-agent>UA</a>
            that interprets the semantics of a style sheet and renders
            documents that use them.
        <dt>authoring tool
            <dd>A <a href=http://www.w3.org/TR/CSS21/conform.html#user-agent>UA</a>
            that writes a style sheet.
    </dl>

    <p>A style sheet is conformant to this specification
    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 this specification
    if, in addition to interpreting the style sheet as defined by the
    appropriate specifications, it supports all the features defined
    by this specification 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 this specification
    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 class="no-ref heading settled heading" id=partial><span class=content>
Partial implementations</span><a class=self-link href=#partial></a></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=http://www.w3.org/TR/CSS21/conform.html#ignore>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 class="no-ref heading settled heading" id=experimental><span class=content>
Experimental implementations</span><a class=self-link href=#experimental></a></h3>

    <p>To avoid clashes with future CSS features, the CSS2.1 specification
    reserves a <a href=http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords>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.
    </p>

<h3 class="no-ref heading settled heading" id=testing><span class=content>
Non-experimental implementations</span><a class=self-link href=#testing></a></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=http://www.w3.org/Style/CSS/Test/>http://www.w3.org/Style/CSS/Test/</a>.
    Questions should be directed to the
    <a href=http://lists.w3.org/Archives/Public/public-css-testsuite>public-css-testsuite@w3.org</a>
    mailing list.

<h2 class="no-num no-ref heading settled heading" id=references><span class=content>
References</span><a class=self-link href=#references></a></h2>

<h3 class="no-num no-ref heading settled heading" id=normative><span class=content>
Normative References</span><a class=self-link href=#normative></a></h3>
<div data-fill-with=normative-references><dl><dt id=css3syn title=CSS3SYN><a class=self-link href=#css3syn></a>[CSS3SYN]<dd>L. David Baron. <a href=http://www.w3.org/TR/2003/WD-css3-syntax-20030813>CSS3 module: Syntax</a>. 13 August 2003. W3C Working Draft. (Work in progress.) URL: <a href=http://www.w3.org/TR/2003/WD-css3-syntax-20030813>http://www.w3.org/TR/2003/WD-css3-syntax-20030813</a><dt id=rfc2119 title=RFC2119><a class=self-link href=#rfc2119></a>[RFC2119]<dd>S. Bradner. <a href=http://www.ietf.org/rfc/rfc2119.txt>Key words for use in RFCs to Indicate Requirement Levels</a>. URL: <a href=http://www.ietf.org/rfc/rfc2119.txt>http://www.ietf.org/rfc/rfc2119.txt</a></dl></div>

<h3 class="no-num no-ref heading settled heading" id=informative><span class=content>
Informative References</span><a class=self-link href=#informative></a></h3>
<div data-fill-with=informative-references><dl><dt id=html40 title=HTML40><a class=self-link href=#html40></a>[HTML40]<dd>Ian Jacobs; David Raggett; Arnaud Le Hors. <a href=http://www.w3.org/TR/1998/REC-html40-19980424>HTML 4.0 Specification</a>. 24 April 1998. W3C Recommendation. URL: <a href=http://www.w3.org/TR/1998/REC-html40-19980424>http://www.w3.org/TR/1998/REC-html40-19980424</a></dl></div>

<h2 class="no-num no-ref heading settled heading" id=index><span class=content>
Index</span><a class=self-link href=#index></a></h2>
<div data-fill-with=index><ul class=indexlist>
<li>Arg1, <a href=#dom-foobaz-arg1 title="section 2.1">2.1</a>
<li>Arg2, <a href=#dom-foobaz-arg2 title="section 2.1">2.1</a>
<li>bar, <a href=#dom-foo-bar title="section 2.1">2.1</a>
<li>baz(), <a href=#dom-foo-baz title="section 2.1">2.1</a>
<li>Cross-references, <a href=#cross-references title="section 2.1">2.1</a>
<li>Foo, <a href=#dom-foo title="section 2.1">2.1</a>
<li>FooDict, <a href=#dictdef-foodict title="section 2.1">2.1</a>
<li>index, <a href=#index0 title="section 2">2</a>
<li>simple, <a href=#simplest title="section 2">2</a>
<li>simpler, <a href=#simplest title="section 2">2</a>
<li>simplest, <a href=#simplest title="section 2">2</a>
<li>terms, <a href=#terms title="section 2">2</a>
<li>value-name (value), <a href=#valuedef-value-name title="section 2.1">2.1</a>
<li>variant, <a href=#variants title="section 2">2</a>
</ul></div>

<h2 class="no-num no-ref heading settled heading" id=property-index><span class=content>
Property index</span><a class=self-link href=#property-index></a></h2>
<div data-fill-with=property-index><table class=proptable><thead><tr><th scope=col>Name<th scope=col>Value<th scope=col>Initial<th scope=col>Applies To<th scope=col>Inh.<th scope=col>%ages<th scope=col>Media<th scope=col>Animatable<th scope=col>Applies to<th scope=col>Canonical order<th scope=col>Computed value<tbody>
<tr><th scope=row><a data-property="">foo</a><td>inline-inside | block-inside | table | ruby | icon<td>text<td><td>no<td>n/a<td>visual<td>no<td>all elements<td>per grammar<td>specified value</table></div>


<h2 class="no-num heading settled" id=issues-index><span class=content>Issues Index</span><a class=self-link href=#issues-index></a></h2><div style="counter-reset: issue"><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 “CR”
		(Candidate Recommendation).
		Use class=“issue”.

	<a href=#issue-1383a6cc> ↵ </a><p class=issue>
		Inline issues will be copied into an <a href=#issues-index>Issues Index</a> at the end of the document,
		for easy reference.

	<a href=#issue-e459e740> ↵ </a></div>