-
Notifications
You must be signed in to change notification settings - Fork 791
Expand file tree
/
Copy pathOverview.html
More file actions
645 lines (523 loc) · 49 KB
/
Overview.html
File metadata and controls
645 lines (523 loc) · 49 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
<!DOCTYPE html><html lang=en><head>
<meta content="text/html; charset=utf-8" http-equiv=Content-Type>
<title>CSS Display Module Level 3</title>
<link href=../default.css rel=stylesheet type=text/css>
<link href=../csslogo.ico rel="shortcut icon" type=image/x-icon>
<style>
body {
background: url("https://www.w3.org/StyleSheets/TR/logo-ED") top left no-repeat white;
background-attachment: fixed;
color: black;
font-family: sans-serif;
margin: 0 auto;
max-width: 50em;
padding: 2em 1em 2em 70px;
}
:link { color: #00C; background: transparent }
:visited { color: #609; background: transparent }
a[href]:active { color: #C00; background: transparent }
a[href]:hover { background: #ffa }
a[href] img { border-style: none }
h1, h2, h3, h4, h5, h6 { text-align: left }
h1, h2, h3 { color: #005A9C; }
h1 { font: 170% sans-serif }
h2 { font: 140% sans-serif }
h3 { font: 120% sans-serif }
h4 { font: bold 100% sans-serif }
h5 { font: italic 100% sans-serif }
h6 { font: small-caps 100% sans-serif }
.hide { display: none }
div.head { margin-bottom: 1em }
div.head h1 { margin-top: 2em; clear: both }
div.head table { margin-left: 2em; margin-top: 2em }
p.copyright { font-size: small }
p.copyright small { font-size: small }
pre { margin-left: 2em }
dt { font-weight: bold }
ul.toc, ol.toc {
list-style: none;
}
</style>
</head>
<body class=h-entry>
<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 Display Module Level 3</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=20140129>29 January 2014</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-display>http://dev.w3.org/csswg/css-display</a><dt>Editor’s Draft:<dd><a href=http://dev.w3.org/csswg/css-display>http://dev.w3.org/csswg/css-display</a>
<dt>Feedback:</dt>
<dd><a href="mailto:www-style@w3.org?subject=%5Bcss-display%5D%20feedback">www-style@w3.org</a>
with subject line
“<kbd>[css-display] <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://xanthir.com/contact/>Tab Atkins Jr.</a> (<span class="p-org org">Google</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 contains the features of CSS relating to the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property and other box-generation details.
<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-display%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-display” in the subject,
preferably like this:
“[css-display] <em>…summary of comment…</em>”
<p>
This document was produced by the <a href=http://www.w3.org/Style/CSS/members>CSS Working Group</a>
(part of the <a href=http://www.w3.org/Style/>Style Activity</a>).
<p>
This document was produced by a group operating under
the <a href=http://www.w3.org/Consortium/Patent-Policy-20040205/>5 February 2004 W3C Patent Policy</a>.
W3C maintains a <a href=http://www.w3.org/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=http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential>Essential Claim(s)</a>
must disclose the information in accordance with <a href=http://www.w3.org/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><ul class=toc><li><a href=#placement><span class=secno>1.1</span>
Module interactions</a><li><a href=#values><span class=secno>1.2</span>
Values</a></ul><li><a href=#the-display-properties><span class=secno>2</span>
The Display Properties</a><ul class=toc><li><a href=#the-display-inside><span class=secno>2.1</span>
Setting the layout mode: the <span class=property data-link-type=propdesc title=display-inside>display-inside</span> property</a><li><a href=#the-display-outside><span class=secno>2.2</span>
Interacting with the layout mode: the <span class=property data-link-type=propdesc title=display-outside>display-outside</span> property</a><li><a href=#the-display-extras><span class=secno>2.3</span>
Additional stuff: the <span class=property data-link-type=propdesc title=display-extras>display-extras</span> property</a><li><a href=#the-display><span class=secno>2.4</span>
The <span class=property data-link-type=propdesc title=display>display</span> shorthand property</a></ul><li><a href=#the-display-box><span class=secno>3</span>
Controlling box generation: the <span class=property data-link-type=propdesc title=display-box>display-box</span> property</a><li><a href=#acknowledgments><span class=secno></span>
Acknowledgments</a><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> The <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property, introduced in CSS 2.1,
defines what kind of boxes an element generates
(and whether it generates boxes at all),
and how it lays out its contents.
<p> These concepts are actually rather independent,
though they’re conflated by the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property.
This causes some pain when a property value intended to affect one aspect
(such as setting an element to <a class=css data-link-type=propdesc href=#propdef-display title=display>display:none</a> to suppress box generation)
affects another aspect
(such as losing the memory of what it was <em>before</em> <a class=css data-link-type=propdesc href=#propdef-display title=display>display:none</a>,
so that it can be set back to that value later).
<p> This specification subsumes the CSS 2.1 definition of the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property,
and redefines it to be a shorthand property for a small family of longhands,
each controlling an independent aspect of an element’s "display".
<h3 class="heading settled heading" data-level=1.1 id=placement><span class=secno>1.1 </span><span class=content>
Module interactions</span><a class=self-link href=#placement></a></h3>
<p> This specification transforms the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property into a shorthand property,
and defines several longhand properties that it expands into or effects.
<p> This module replaces and extends the definition of the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property defined in <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a> section 9.2.4.
<p> None of the properties in this module apply to the <code>::first-line</code> or <code>::first-letter</code> pseudo-elements.
<h3 class="heading settled heading" data-level=1.2 id=values><span class=secno>1.2 </span><span class=content>
Values</span><a class=self-link href=#values></a></h3>
<p> This specification follows the
<a href=http://www.w3.org/TR/CSS21/about.html#property-defs>CSS property
definition conventions</a> from <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>. Value types not defined in
this specification are defined in CSS Level 2 Revision 1 <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>.
Other CSS modules may expand the definitions of these value types.
<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 class="heading settled heading" data-level=2 id=the-display-properties><span class=secno>2 </span><span class=content>
The Display Properties</span><a class=self-link href=#the-display-properties></a></h2>
<p> The <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> 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 class="heading settled heading" data-level=2.1 id=the-display-inside><span class=secno>2.1 </span><span class=content>
Setting the layout mode: the <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> property</span><a class=self-link href=#the-display-inside></a></h3>
<table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-display-inside>display-inside<a class=self-link href=#propdef-display-inside></a></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>Media:<td>all<tr><th>Computed value:<td>a keyword<tr><th>Percentages:<td>n/a</table>
<dl data-dfn-for=display-inside data-dfn-type=value>
<dt><dfn class=css-code data-dfn-for=display-inside data-dfn-type=value data-export="" id=valuedef-auto>auto<a class=self-link href=#valuedef-auto></a></dfn>
<dd>
If the element’s computed <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> value is <a class=css data-link-type=maybe href=#valuedef-inline-level title=inline-level>inline-level</a>,
the element is an inline element,
and lays out its contents using inline layout. <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>
If the element’s computed <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> value is <a class=css data-link-type=maybe href=#valuedef-table-row-group title=table-row-group>table-row-group</a>, <a class=css data-link-type=maybe href=#valuedef-table-header-group title=table-header-group>table-header-group</a>, <a class=css data-link-type=maybe href=#valuedef-table-footer-group title=table-footer-group>table-footer-group</a>, <a class=css data-link-type=maybe href=#valuedef-table-row title=table-row>table-row</a>, <a class=css data-link-type=maybe href=#valuedef-table-column-group title=table-column-group>table-column-group</a>, or <a class=css data-link-type=maybe href=#valuedef-table-column title=table-column>table-column</a>,
this elements acts as normal for its given <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> value.
Otherwise, this value computes to <a class=css data-link-for=display-inside data-link-type=maybe href=#valuedef-block0 title=block>block</a>.
<dt><dfn class=css-code data-dfn-for=display-inside data-dfn-type=value data-export="" id=valuedef-block0>block<a class=self-link href=#valuedef-block0></a></dfn>
<dd>
The element lays out its contents using block layout. <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>
<dt><dfn class=css-code data-dfn-for=display-inside data-dfn-type=value data-export="" id=valuedef-table0>table<a class=self-link href=#valuedef-table0></a></dfn>
<dd>
The element lays out its contents using table layout. <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>
<dt><dfn class=css-code data-dfn-for=display-inside data-dfn-type=value data-export="" id=valuedef-flex0>flex<a class=self-link href=#valuedef-flex0></a></dfn>
<dd>
The element lays out its contents using flex layout. <a data-biblio-type=normative data-link-type=biblio href=#css3-flexbox title=css3-flexbox>[CSS3-FLEXBOX]</a>
<dt><dfn class=css-code data-dfn-for=display-inside data-dfn-type=value data-export="" id=valuedef-grid0>grid<a class=self-link href=#valuedef-grid0></a></dfn>
<dd>
The element lays out its contents using grid layout. <a data-biblio-type=normative data-link-type=biblio href=#css3-grid-layout title=css3-grid-layout>[CSS3-GRID-LAYOUT]</a>
</dl>
<h3 class="heading settled heading" data-level=2.2 id=the-display-outside><span class=secno>2.2 </span><span class=content>
Interacting with the layout mode: the <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> property</span><a class=self-link href=#the-display-outside></a></h3>
<table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-display-outside>display-outside<a class=self-link href=#propdef-display-outside></a></dfn><tr><th>Value:<td>block-level | inline-level | none | 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>Media:<td>all<tr><th>Computed value:<td>as specified<tr><th>Percentages:<td>n/a</table>
<dl data-dfn-for=display-outside data-dfn-type=value>
<dt><dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-block-level>block-level<a class=self-link href=#valuedef-block-level></a></dfn>
<dd>
The element is block-level,
and participates in a block formatting context.
Other formatting contexts,
such as flex formatting contexts,
may also work with block-level elements. <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>
<dt><dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-inline-level>inline-level<a class=self-link href=#valuedef-inline-level></a></dfn>
<dd>
The element is inline-level,
and participates in an inline formatting context. <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>
<dt><dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-none0>none<a class=self-link href=#valuedef-none0></a></dfn>
<dd>
The element generates no boxes,
and does not participate in any formatting context.
<p class=note> Note: This value exists for legacy reasons,
and interacts with the separate <a class=property data-link-type=propdesc href=#propdef-display-box title=display-box>display-box</a> property.
It is recommended that <a class=property data-link-type=propdesc href=#propdef-display-box title=display-box>display-box</a> be used to suppress an element,
so that the element’s display type is automatically preserved
for when it’s no longer suppressed.
<dt><dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-row-group>table-row-group<a class=self-link href=#valuedef-table-row-group></a></dfn>, <dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-header-group>table-header-group<a class=self-link href=#valuedef-table-header-group></a></dfn>, <dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-footer-group>table-footer-group<a class=self-link href=#valuedef-table-footer-group></a></dfn>, <dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-row>table-row<a class=self-link href=#valuedef-table-row></a></dfn>, <dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-cell0>table-cell<a class=self-link href=#valuedef-table-cell0></a></dfn>, <dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-column-group>table-column-group<a class=self-link href=#valuedef-table-column-group></a></dfn>, <dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-column>table-column<a class=self-link href=#valuedef-table-column></a></dfn>, <dfn class=css-code data-dfn-for=display-outside data-dfn-type=value data-export="" id=valuedef-table-caption0>table-caption<a class=self-link href=#valuedef-table-caption0></a></dfn>
<dd>
The element is an internal table element,
and participates in a table layout context. <a data-biblio-type=normative data-link-type=biblio href=#css21 title=css21>[CSS21]</a>
</dl>
<p class=issue id=issue-d9dbe467><a class=self-link href=#issue-d9dbe467></a>
Do we need special bits about some of the interactions with <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a>?
For example, how <a class=css data-link-type=propdesc href=#propdef-display title=display>display:inline-level block;</a> 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 id=issue-959f23ef><a class=self-link href=#issue-959f23ef></a>
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 class="heading settled heading" data-level=2.3 id=the-display-extras><span class=secno>2.3 </span><span class=content>
Additional stuff: the <a class=property data-link-type=propdesc href=#propdef-display-extras title=display-extras>display-extras</a> property</span><a class=self-link href=#the-display-extras></a></h3>
<table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-display-extras>display-extras<a class=self-link href=#propdef-display-extras></a></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>Media:<td>all<tr><th>Computed value:<td>as specified<tr><th>Percentages:<td>n/a</table>
<dl data-dfn-for=display-extras data-dfn-type=value>
<dt><dfn class=css-code data-dfn-for=display-extras data-dfn-type=value data-export="" id=valuedef-list-item0>list-item<a class=self-link href=#valuedef-list-item0></a></dfn>
<dd>
The element generates a <code>::marker</code> pseudo-element
and is considered a <a data-link-type=dfn href=http://dev.w3.org/csswg/css-lists-3/#list-item title="list item">list item</a>.
</dl>
<p class=issue id=issue-70026084><a class=self-link href=#issue-70026084></a>
This property is probably dumb,
and at the very least has a dumb name.
Better names?
If I define more one-off weird box-generation details like this,
should I merge them into a single "extras" property like this,
or just have them all be separate properties?
<h3 class="heading settled heading" data-level=2.4 id=the-display><span class=secno>2.4 </span><span class=content>
The <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> shorthand property</span><a class=self-link href=#the-display></a></h3>
<table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-display>display<a class=self-link href=#propdef-display></a></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 | [ <a class=production data-link-type=propdesc href=#propdef-display-inside title=display-inside><‘display-inside’></a> || <a class=production data-link-type=propdesc href=#propdef-display-outside title=display-outside><‘display-outside’></a> || <a class=production data-link-type=propdesc href=#propdef-display-extras title=display-extras><‘display-extras’></a> ]<tr><th>Initial:<td>see individual properties<tr><th>Applies to:<td>see individual properties<tr><th>Inherited:<td>see individual properties<tr><th>Media:<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 id=issue-49dc1da3><a class=self-link href=#issue-49dc1da3></a>
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 <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a>, which is <a class=css data-link-type=maybe href=#valuedef-inline-level title=inline-level>inline-level</a>.
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 <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> keyword,
<a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> defaults to <a class=css data-link-type=maybe href=#valuedef-block-level title=block-level>block-level</a>.
If the latter is chosen, we could remove several more of the special expansions below
(all the ones that are identical to a <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> value).
<p class=note> 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 2.1,
before the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> property became a shorthand.
<dl data-dfn-for=display data-dfn-type=value>
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-inline>inline<a class=self-link href=#valuedef-inline></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="inline-level auto">inline-level auto</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-block>block<a class=self-link href=#valuedef-block></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="block-level block">block-level block</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-list-item>list-item<a class=self-link href=#valuedef-list-item></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="block-level block list-item">block-level block list-item</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-inline-list-item>inline-list-item<a class=self-link href=#valuedef-inline-list-item></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="inline-level block list-item">inline-level block list-item</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-inline-block>inline-block<a class=self-link href=#valuedef-inline-block></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="inline-level block">inline-level block</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-table>table<a class=self-link href=#valuedef-table></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="block-level table">block-level table</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-inline-table>inline-table<a class=self-link href=#valuedef-inline-table></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="inline-level table">inline-level table</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-table-caption>table-caption<a class=self-link href=#valuedef-table-caption></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="table-caption block">table-caption block</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-table-cell>table-cell<a class=self-link href=#valuedef-table-cell></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="table-cell block">table-cell block</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-flex>flex<a class=self-link href=#valuedef-flex></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="block-level flex">block-level flex</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-inline-flex>inline-flex<a class=self-link href=#valuedef-inline-flex></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="inline-level flex">inline-level flex</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-grid>grid<a class=self-link href=#valuedef-grid></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="block-level grid">block-level grid</span>.
<dt><dfn class=css-code data-dfn-for=display data-dfn-type=value data-export="" id=valuedef-inline-grid>inline-grid<a class=self-link href=#valuedef-inline-grid></a></dfn>
<dd>
Expands identically to <span class=css data-link-type=maybe title="inline-level grid">inline-level grid</span>.
</dl>
<h2 class="heading settled heading" data-level=3 id=the-display-box><span class=secno>3 </span><span class=content>
Controlling box generation: the <a class=property data-link-type=propdesc href=#propdef-display-box title=display-box>display-box</a> property</span><a class=self-link href=#the-display-box></a></h2>
<table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-display-box>display-box<a class=self-link href=#propdef-display-box></a></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>Media:<td>all<tr><th>Computed value:<td>see prose<tr><th>Percentages:<td>n/a</table>
<p> The <a class=property data-link-type=propdesc href=#propdef-display-box title=display-box>display-box</a> property is not part of the <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> shorthand,
so that <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> can be safely set without accidentally overriding whether an element is being suppressed or not.
<p> If the computed value of <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> is <a class=css data-link-for=display-outside data-link-type=maybe href=#valuedef-none0 title=none>none</a>,
the computed value of <a class=property data-link-type=propdesc href=#propdef-display-box title=display-box>display-box</a> is <span class=css data-link-for=display-box data-link-type=maybe title=none>none</span>.
Otherwise, the computed value is the specified value.
<dl data-dfn-for=box data-dfn-type=value>
<dt><dfn class=css-code data-dfn-for=box data-dfn-type=value data-export="" id=valuedef-normal>normal<a class=self-link href=#valuedef-normal></a></dfn>
<dd>
The element generates boxes as normal,
per its other <a class=property data-link-type=propdesc title=display-*>display-*</a> properties.
<dt><dfn class=css-code data-dfn-for=box data-dfn-type=value data-export="" id=valuedef-none>none<a class=self-link href=#valuedef-none></a></dfn>
<dd>
The element generates no boxes at all.
<dt><dfn class=css-code data-dfn-for=box data-dfn-type=value data-export="" id=valuedef-contents>contents<a class=self-link href=#valuedef-contents></a></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 id=issue-de0b625d><a class=self-link href=#issue-de0b625d></a>
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 id=issue-b8422544><a class=self-link href=#issue-b8422544></a>
<a class=css data-link-type=maybe href=#valuedef-contents title=contents>contents</a> 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?
<h2 class="no-num heading settled heading" id=acknowledgments><span class=content>
Acknowledgments</span><a class=self-link href=#acknowledgments></a></h2>
<p> We would like to thank the many people who have attempted to separate out the disparate details of box generation over the years,
most particularly Bert Bos,
whose last attempt with <a class=property data-link-type=propdesc title=display-model>display-model</a> and <a class=property data-link-type=propdesc title=display-role>display-role</a> didn’t get anywhere,
but primed us for the current spec.
<p> We would also like to thank the many JavaScript libraries such as jQuery which have hacked around the "what <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> should I give it when you call .show()?" problem, making it extremely clear that something needed to be done on our part.
<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=css21 title=CSS21><a class=self-link href=#css21></a>[CSS21]<dd>Bert Bos; et al. <a href=http://www.w3.org/TR/2011/REC-CSS2-20110607>Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification</a>. 7 June 2011. W3C Recommendation. URL: <a href=http://www.w3.org/TR/2011/REC-CSS2-20110607>http://www.w3.org/TR/2011/REC-CSS2-20110607</a><dt id=css3-flexbox title=CSS3-FLEXBOX><a class=self-link href=#css3-flexbox></a>[CSS3-FLEXBOX]<dd>Tab Atkins Jr.; Elika J. Etemad; Alex Mogilevsky. <a href=http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/>CSS Flexible Box Layout Module</a>. 18 September 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/>http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/</a><dt id=css3-grid-layout title=CSS3-GRID-LAYOUT><a class=self-link href=#css3-grid-layout></a>[CSS3-GRID-LAYOUT]<dd>Tab Atkins Jr.; Elika J. Etemad; Rossen Atanassov. <a href=http://www.w3.org/TR/2013/WD-css3-grid-layout-20130402/>CSS Grid Layout</a>. 2 April 2013. W3C Working Draft. (Work in progress.) URL: <a href=http://www.w3.org/TR/2013/WD-css3-grid-layout-20130402/>http://www.w3.org/TR/2013/WD-css3-grid-layout-20130402/</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></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>auto, <a href=#valuedef-auto title="section 2.1">2.1</a>
<li>block<ul><li>value for display-inside, <a href=#valuedef-block0 title="section 2.1">2.1</a>
<li>value for display, <a href=#valuedef-block title="section 2.4">2.4</a>
</ul><li>block-level, <a href=#valuedef-block-level title="section 2.2">2.2</a>
<li>contents, <a href=#valuedef-contents title="section 3">3</a>
<li>display, <a href=#propdef-display title="section 2.4">2.4</a>
<li>display-box, <a href=#propdef-display-box title="section 3">3</a>
<li>display-extras, <a href=#propdef-display-extras title="section 2.3">2.3</a>
<li>display-inside, <a href=#propdef-display-inside title="section 2.1">2.1</a>
<li>display-outside, <a href=#propdef-display-outside title="section 2.2">2.2</a>
<li>flex<ul><li>value for display-inside, <a href=#valuedef-flex0 title="section 2.1">2.1</a>
<li>value for display, <a href=#valuedef-flex title="section 2.4">2.4</a>
</ul><li>grid<ul><li>value for display-inside, <a href=#valuedef-grid0 title="section 2.1">2.1</a>
<li>value for display, <a href=#valuedef-grid title="section 2.4">2.4</a>
</ul><li>inline, <a href=#valuedef-inline title="section 2.4">2.4</a>
<li>inline-block, <a href=#valuedef-inline-block title="section 2.4">2.4</a>
<li>inline-flex, <a href=#valuedef-inline-flex title="section 2.4">2.4</a>
<li>inline-grid, <a href=#valuedef-inline-grid title="section 2.4">2.4</a>
<li>inline-level, <a href=#valuedef-inline-level title="section 2.2">2.2</a>
<li>inline-list-item, <a href=#valuedef-inline-list-item title="section 2.4">2.4</a>
<li>inline-table, <a href=#valuedef-inline-table title="section 2.4">2.4</a>
<li>list-item<ul><li>value for display-extras, <a href=#valuedef-list-item0 title="section 2.3">2.3</a>
<li>value for display, <a href=#valuedef-list-item title="section 2.4">2.4</a>
</ul><li>none<ul><li>value for display-outside, <a href=#valuedef-none0 title="section 2.2">2.2</a>
<li>value for box, <a href=#valuedef-none title="section 3">3</a>
</ul><li>normal, <a href=#valuedef-normal title="section 3">3</a>
<li>table<ul><li>value for display-inside, <a href=#valuedef-table0 title="section 2.1">2.1</a>
<li>value for display, <a href=#valuedef-table title="section 2.4">2.4</a>
</ul><li>table-caption<ul><li>value for display-outside, <a href=#valuedef-table-caption0 title="section 2.2">2.2</a>
<li>value for display, <a href=#valuedef-table-caption title="section 2.4">2.4</a>
</ul><li>table-cell<ul><li>value for display-outside, <a href=#valuedef-table-cell0 title="section 2.2">2.2</a>
<li>value for display, <a href=#valuedef-table-cell title="section 2.4">2.4</a>
</ul><li>table-column, <a href=#valuedef-table-column title="section 2.2">2.2</a>
<li>table-column-group, <a href=#valuedef-table-column-group title="section 2.2">2.2</a>
<li>table-footer-group, <a href=#valuedef-table-footer-group title="section 2.2">2.2</a>
<li>table-header-group, <a href=#valuedef-table-header-group title="section 2.2">2.2</a>
<li>table-row, <a href=#valuedef-table-row title="section 2.2">2.2</a>
<li>table-row-group, <a href=#valuedef-table-row-group title="section 2.2">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 data"><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>Computed value<tbody>
<tr><th scope=row><a data-property="">display-inside</a><td>auto | block | table | flex | grid<td>auto<td>all elements<td>no<td>n/a<td>all<td><td>a keyword
<tr><th scope=row><a data-property="">display-outside</a><td>block-level | inline-level | none | table-row-group | table-header-group | table-footer-group | table-row | table-cell | table-column-group | table-column | table-caption<td>inline-level<td>all elements<td>no<td>n/a<td>all<td><td>as specified
<tr><th scope=row><a data-property="">display-extras</a><td>none | list-item<td>none<td>all elements<td>no<td>n/a<td>all<td><td>as specified
<tr><th scope=row><a data-property="">display</a><td>inline | block | list-item | inline-list-item | inline-block | table | inline-table | table-cell | table-caption | flex | inline-flex | grid | inline-grid | [ <‘display-inside’> || <‘display-outside’> || <‘display-extras’> ]<td>see individual properties<td>see individual properties<td>see individual properties<td><td>see individual properties<td>see individual properties<td>see individual properties
<tr><th scope=row><a data-property="">display-box</a><td>normal | none | contents<td>normal<td>all elements<td>no<td>n/a<td>all<td><td>see prose</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"><div class=issue>
Do we need special bits about some of the interactions with <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a>?
For example, how <a class=css data-link-type=propdesc href=#propdef-display title=display>display:inline-level block;</a> 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?)
<a href=#issue-d9dbe467> ↵ </a></div><div 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?
<a href=#issue-959f23ef> ↵ </a></div><div class=issue>
This property is probably dumb,
and at the very least has a dumb name.
Better names?
If I define more one-off weird box-generation details like this,
should I merge them into a single "extras" property like this,
or just have them all be separate properties?
<a href=#issue-70026084> ↵ </a></div><div 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 <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a>, which is <a class=css data-link-type=maybe href=#valuedef-inline-level title=inline-level>inline-level</a>.
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 <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> keyword,
<a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a> defaults to <a class=css data-link-type=maybe href=#valuedef-block-level title=block-level>block-level</a>.
If the latter is chosen, we could remove several more of the special expansions below
(all the ones that are identical to a <a class=property data-link-type=propdesc href=#propdef-display-inside title=display-inside>display-inside</a> value).
<a href=#issue-49dc1da3> ↵ </a></div><div 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.?
<a href=#issue-de0b625d> ↵ </a></div><div class=issue>
<a class=css data-link-type=maybe href=#valuedef-contents title=contents>contents</a> 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?
<a href=#issue-b8422544> ↵ </a></div></div>