-
Notifications
You must be signed in to change notification settings - Fork 790
Expand file tree
/
Copy pathOverview.src.html
More file actions
executable file
·715 lines (588 loc) · 24.3 KB
/
Overview.src.html
File metadata and controls
executable file
·715 lines (588 loc) · 24.3 KB
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
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>CSS Display Module Level 3</title>
<link rel=contents href="#contents">
<link rel=index href="#index">
<link rel="stylesheet" type="text/css" href="../default.css">
<link href="../csslogo.ico" rel="shortcut icon" type="image/x-icon">
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS].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;
}
</style>
</head>
<div class="head">
<!--logo-->
<h1>CSS Display Module Level 3</h1>
<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
<dl>
<dt>This version:
<dd><a href="[VERSION]" class="replaceme">http://www.w3.org/TR/[YEAR]/ED-cssN-FIXME-[CDATE]/</a>
<dt>Latest version:
<dd><a href="http://www.w3.org/TR/[SHORTNAME]/">http://www.w3.org/TR/[SHORTNAME]/</a>
<dt>Editor's draft:
<dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">http://dev.w3.org/csswg/[SHORTNAME]/</a>
<dt>Previous version:
<dd><a href="http://www.w3.org/PreviousVersionURI">
http://www.w3.org/PreviousVersionURI</a>
<dt>Issue Tracking:</dt>
<dd><a href="http://www.w3.org/Style/CSS/Tracker/products/FIXME">http://www.w3.org/Style/CSS/Tracker/products/FIXME</a>
<dt>Feedback:</dt>
<dd><a href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a> with subject line “<kbd>[[SHORTNAME]] <var>… message topic …</var></kbd>”
<dt>Editors:
<dd class="h-card vcard">
<a class="p-name fn u-url url" rel="author"
href="http://www.xanthir.com/">Tab Atkins Jr.</a>
(<span class="p-org org">Google, Inc.</span>),
<span class="u-email email">jackalmage@gmail.com</span>
</dl>
<!--copyright-->
<hr title="Separator for header">
</div>
<h2 class="no-num no-toc" id="abstract">Abstract</h2>
<p>
This module contains the features of CSS relating to the 'display' property.
<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.
<h2 class="no-num no-toc" id="status">Status of this document</h2>
<p>
This is currently a personal draft,
not yet approved by the CSSWG to be an Editor's Draft.
(Ignore the branding on the side and heading, which are artifacts of the spec generation process.)
<!--//status-->
<p>The following features are at risk: …
<h2 class="no-num no-toc" id="contents">
Table of contents</h2>
<!--toc-->
<h2 id="intro">
Introduction</h2>
<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>.
<p>
None of the properties in this module apply to the <code>::first-line</code> or <code>::first-letter</code> pseudo-elements.
<h3 id="values">
Values</h3>
<p>This specification follows the
<a href="http://www.w3.org/TR/CSS21/about.html#property-defs">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 <color> 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="http://www.w3.org/TR/css3-values/#common-keywords">CSS-wide keywords</a>
as their property value. For readability it has not been repeated explicitly.
<h2>
The Display Properties</h2>
<p>
The 'display' shorthand and its associated family of properties control the layout mode of elements
(how the element determines the sizes and positions of itself and its descendants),
and what boxes they and their descendants generate.
<h3 id='the-display-inside'>
Setting the layout mode: the 'display-inside' property</h3>
<table class='propdef'>
<tr>
<th>Name:
<td><dfn>display-inside</dfn>
<tr>
<th>Value:
<td>auto | block | table | flex | grid
<tr>
<th>Initial:
<td>auto
<tr>
<th>Applies To:
<td>all elements
<tr>
<th>Inherited:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Computed Value:
<td>a keyword
</table>
<dl>
<dt><dfn id='display-inside:auto'>auto</dfn>
<dd>
If the element's computed 'display-outside' value is ''inline-level'',
the element is an <i>inline element</i>,
and lays out its contents using inline layout. [[!CSS21]]
If the element's computed 'display-outside' value is ''table-row-group'', ''table-header-group'', ''table-footer-group'', ''table-row'', ''table-column-group'', or ''table-column'',
this elements acts as normal for its given 'display-outside' value.
Otherwise, this value computes to ''block''.
<dt><dfn id='display-inside:block'>block</dfn>
<dd>
The element lays out its contents using block layout. [[!CSS21]]
<dt><dfn id='display-inside:table'>table</dfn>
<dd>
The element lays out its contents using table layout. [[!CSS21]]
<dt><dfn id='display-inside:flex'>flex</dfn>
<dd>
The element lays out its contents using flex layout. [[!CSS3-FLEXBOX]]
<dt><dfn id='display-inside:grid'>grid</dfn>
<dd>
The element lays out its contents using grid layout. [[!CSS3-GRID]]
</dl>
<h3 id='the-display-outside'>
Interacting with the layout mode: the 'display-outside' property</h3>
<table class='propdef'>
<tr>
<th>Name:
<td><dfn>display-outside</dfn>
<tr>
<th>Value:
<td>block-level | inline-level | table-row-group | table-header-group | table-footer-group | table-row | table-cell | table-column-group | table-column | table-caption
<tr>
<th>Initial:
<td>inline-level
<tr>
<th>Applies To:
<td>all elements
<tr>
<th>Inherited:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Computed Value:
<td>as specified
</table>
<dl>
<dt><dfn id='display-outside:block-level'>block-level</dfn>
<dd>
The element is <i>block-level</i>,
and participates in a block formatting context.
Other formatting contexts,
such as flex formatting contexts,
may also work with <i>block-level</i> elements. [[!CSS21]]
<dt><dfn id='display-outside:inline-level'>inline-level</dfn>
<dd>
The element is <i>inline-level</i>,
and participates in an inline formatting context. [[!CSS21]]
<dt><dfn id='display-outside:table-row-group'>table-row-group</dfn>, <dfn id='display-outside:table-header-group'>table-header-group</dfn>, <dfn id='display-outside:table-footer-group'>table-footer-group</dfn>, <dfn id='display-outside:table-row'>table-row</dfn>, <dfn id='display-outside:table-cell'>table-cell</dfn>, <dfn id='display-outside:table-column-group'>table-column-group</dfn>, <dfn id='display-outside:table-column'>table-column</dfn>, <dfn id='display-outside:table-caption'>table-caption</dfn>
<dd>
The element is an internal table element,
and participates in a table layout context. [[!CSS21]]
</dl>
<p class='issue'>
Do we need special bits about some of the interactions with 'display-inside'?
For example, how ''display:inline-level block;'' works?
Or does that fall out of what exists,
and the definitions of Block Layout in 2.1?
(...or a new Block Layout spec, explaining all the 2.1 stuff more sanely?)
<p class='issue'>
Is <a href="http://lists.w3.org/Archives/Public/www-style/2012Jul/0450.html">fantasai's proposal for a run-in model</a> sane enough to include in this spec?
<h3 id='the-display-box'>
Controlling box generation: the 'display-box' property</h3>
<table class='propdef'>
<tr>
<th>Name:
<td><dfn>display-box</dfn>
<tr>
<th>Value:
<td>normal | none | contents
<tr>
<th>Initial:
<td>normal
<tr>
<th>Applies To:
<td>all elements
<tr>
<th>Inherited:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Computed Value:
<td>as specified
</table>
<dl>
<dt><dfn id='display-box:normal'>normal</dfn>
<dd>
The element generates boxes as normal,
per its other 'display-*' properties.
<dt><dfn id='display-box:none'>none</dfn>
<dd>
The element generates no boxes at all.
<dt><dfn id='display-box:contents'>contents</dfn>
<dd>
The element itself does not generate any boxes,
but its children and pseudo-elements still generate boxes as normal.
For the purposes of box generation and layout,
the element must be treated as if it had been replaced with its children and pseudo-elements in the document tree.
</dl>
<p class='issue'>
Is there a need for a value that suppresses box generation for layout purposes,
but still generates them for the purposes of animations/counters/etc.?
<p class='issue'>
''contents'' currently only has an effect on box generation and layout.
Other things that care about the document tree are unaffected, like counter scopes.
Is this what we want?
<h3 id='the-display-extras'>
Additional stuff: the 'display-extras' property</h3>
<table class='propdef'>
<tr>
<th>Name:
<td><dfn>display-extras</dfn>
<tr>
<th>Value:
<td>none | [ list-item ]
<tr>
<th>Initial:
<td>none
<tr>
<th>Applies To:
<td>all elements
<tr>
<th>Inherited:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Computed Value:
<td>as specified
</table>
<dl>
<dt><dfn id='display-extras:list-item'>list-item</dfn>
<dd>
The element generates a <code>::marker</code> pseudo-element
and is considered a <a href="../css3-lists/#list-item">list item</a>.
</dl>
<h3 id='the-display'>
The 'display' shorthand property</h3>
<table class='propdef'>
<tr>
<th>Name
3028
:
<td><dfn>display</dfn>
<tr>
<th>Value:
<td>inline | block | list-item | inline-list-item | inline-block | table | inline-table | table-cell | table-caption | flex | inline-flex | grid | inline-grid | none | [ <'display-inside'> || <'display-outside'> || <'display-box'> || <'display-extras'> ]
<tr>
<th>Initial:
<td>see individual properties
<tr>
<th>Applies To:
<td>all elements
<tr>
<th>Inherited:
<td>no
<tr>
<th>Percentages:
<td>see individual properties
<tr>
<th>Computed Value:
<td>see individual properties
<tr>
<th>Animatable:
<td>see individual properties
</table>
<p>
The single-keyword values listed explicitly in the grammar above are handled specially,
for legacy reasons.
All other single-keyword values,
and all other values in general,
are handled as normal for shorthands.
<p class='issue'>
The general rule for new layout modes seems to be that they're block-level by default.
However, this conflicts with the default value of 'display-outside', which is ''inline-level''.
What's the best way to address this?
Simplest answer is to just expand this list of special values as we go along.
Another possibility is to magic up the expansion in a different way,
so that if the value is just a 'display-inside' keyword,
'display-outside' defaults to ''block-level''.
If the latter is chosen, we could remove several more of the special expansions below
(all the ones that are identical to a 'display-inside' value).
<p class='note'>
Several of the "special" expansions below are actually just what the shorthand would expand to normally.
They're included here for clarity,
as they're very familiar from long usage in CSS
DB98
2.1,
before the 'display' property became a shorthand.
<dl>
<dt><dfn id='display:inline'>inline</dfn>
<dd>
Expands identically to ''inline-level auto''.
<dt><dfn id='display:block'>block</dfn>
<dd>
Expands identically to ''block-level block''.
<dt><dfn id='display:list-item'>list-item</dfn>
<dd>
Expands identically to ''block-level block list-item''.
<dt><dfn id='display:inline-list-item'>inline-list-item</dfn>
<dd>
Expands identically to ''inline-level block list-item''.
<dt><dfn id='display:inline-block'>inline-block</dfn>
<dd>
Expands identically to ''inline-level block''.
<dt><dfn id='display:table'>table</dfn>
<dd>
Expands identically to ''block-level table''.
<dt><dfn id='display:inline-table'>inline-table</dfn>
<dd>
Expands identically to ''inline-level table''.
<dt><dfn id='display:table-caption'>table-caption</dfn>
<dd>
Expands identically to ''table-caption block''.
<dt><dfn id='display:table-cell'>table-cell</dfn>
<dd>
Expands identically to ''table-cell block''.
<dt><dfn id='display:flex'>flex</dfn>
<dd>
Expands identically to ''block-level flex''.
<dt><dfn id='display:inline-flex'>inline-flex</dfn>
<dd>
Expands identically to ''inline-level flex''.
<dt><dfn id='display:grid'>grid</dfn>
<dd>
Expands identically to ''block-level grid''.
<dt><dfn id='display:inline-grid'>inline-grid</dfn>
<dd>
Expands identically to ''inline-level grid''.
<dt><dfn id='display:none'>none</dfn>
<dd>
Expands identically to ''inline-level auto none''.
</dl>
<!--
TTTTTTTTTTTTTTTTTTTTTTTHHHHHHHHH HHHHHHHHHEEEEEEEEEEEEEEEEEEEEEE
T:::::::::::::::::::::TH:::::::H H:::::::HE::::::::::::::::::::E
T:::::::::::::::::::::TH:::::::H H:::::::HE::::::::::::::::::::E
T:::::TT:::::::TT:::::THH::::::H H::::::HHEE::::::EEEEEEEEE::::E
TTTTTT T:::::T TTTTTT H:::::H H:::::H E:::::E EEEEEE
T:::::T H:::::H H:::::H E:::::E
T:::::T H::::::HHHHH::::::H E::::::EEEEEEEEEE
T:::::T H:::::::::::::::::H E:::::::::::::::E
T:::::T H:::::::::::::::::H E:::::::::::::::E
T:::::T H::::::HHHHH::::::H E::::::EEEEEEEEEE
T:::::T H:::::H H:::::H E:::::E
T:::::T H:::::H H:::::H E:::::E EEEEEE
TT:::::::TT HH::::::H H::::::HHEE::::::EEEEEEEE:::::E
T:::::::::T H:::::::H H:::::::HE::::::::::::::::::::E
T:::::::::T H:::::::H H:::::::HE::::::::::::::::::::E
TTTTTTTTTTT HHHHHHHHH HHHHHHHHHEEEEEEEEEEEEEEEEEEEEEE
EEEEEEEEEEEEEEEEEEEEEENNNNNNNN NNNNNNNNDDDDDDDDDDDDD
E::::::::::::::::::::EN:::::::N N::::::ND::::::::::::DDD
E::::::::::::::::::::EN::::::::N N::::::ND:::::::::::::::DD
EE::::::EEEEEEEEE::::EN:::::::::N N::::::NDDD:::::DDDDD:::::D
E:::::E EEEEEEN::::::::::N N::::::N D:::::D D:::::D
E:::::E N:::::::::::N N::::::N D:::::D D:::::D
E::::::EEEEEEEEEE N:::::::N::::N N::::::N D:::::D D:::::D
E:::::::::::::::E N::::::N N::::N N::::::N D:::::D D:::::D
E:::::::::::::::E N::::::N N::::N:::::::N D:::::D D:::::D
E::::::EEEEEEEEEE N::::::N N:::::::::::N D:::::D D:::::D
E:::::E N::::::N N::::::::::N D:::::D D:::::D
E:::::E EEEEEEN::::::N N:::::::::N D:::::D D:::::D
EE::::::EEEEEEEE:::::EN::::::N N::::::::NDDD:::::DDDDD:::::D
E::::::::::::::::::::EN::::::N N:::::::ND:::::::::::::::DD
E::::::::::::::::::::EN::::::N N::::::ND::::::::::::DDD
EEEEEEEEEEEEEEEEEEEEEENNNNNNNN NNNNNNNDDDDDDDDDDDDD
-->
<h2 id="conformance">
Conformance</h2>
<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”,
“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. [[!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>
<h3 id="conformance-classes">
Conformance classes</h3>
<p>Conformance to <var class="replaceme">CSS TEMPLATE Module</var>
is defined for three conformance classes:
<dl>
<dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
<dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
style sheet</a>.
<dt><dfn>renderer</dfn></dt>
<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><dfn id="authoring-tool">authoring tool</dfn></dt>
<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 <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="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 id="experimental">
Experimental implementations</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 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="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.
<h3 id="cr-exit-criteria">
CR exit criteria</h3>
<p class="replaceme">Remove this section unless/until the module is in CR.</p>
<!-- This text was <a href="http://www.w3.org/Style/CSS/Tracker/actions/44"> 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:
<dl>
<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
equiv
4FF6
alent 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).
</ol>
</dl>
<p>The specification will remain Candidate Recommendation for at least
six months.
<h2 class=no-num id="acknowledgments">
Acknowledgments</h2>
<p><var class="replaceme">[acknowledgments]</var></p>
<h2 class=no-num id="references">
References</h2>
<h3 class="no-num" id="normative-references">
Normative references</h3>
<!--normative-->
<h3 class="no-num" id="other-references">
Other references</h3>
<!--informative-->
<h2 class="no-num" id="index">
Index</h2>
<!--index-->
<h2 class="no-num" id="property-index">
Property index</h2>
<!-- properties -->
</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")
sgml-live-element-indicator:t
sgml-omittag:nil
sgml-shorttag:nil
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-always-quote-attributes:t
sgml-indent-step:nil
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->