-
Notifications
You must be signed in to change notification settings - Fork 792
Expand file tree
/
Copy pathOverview.bs
More file actions
3722 lines (3243 loc) · 153 KB
/
Overview.bs
File metadata and controls
3722 lines (3243 loc) · 153 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
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<h1>CSS Flexible Box Layout Module Level 1</h1>
<pre class='metadata'>
Shortname: css-flexbox
Level: 1
Status: ED
Group: csswg
ED: http://dev.w3.org/csswg/css-flexbox/
TR: http://www.w3.org/TR/css-flexbox-1/
Previous Version: http://www.w3.org/TR/2014/WD-css-flexbox-1-20140325/
Previous Version: http://www.w3.org/TR/2012/CR-css3-flexbox-20120918/
Previous Version: http://www.w3.org/TR/2012/WD-css3-flexbox-20120612/
Previous Version: http://www.w3.org/TR/2012/WD-css3-flexbox-20120322/
Previous Version: http://www.w3.org/TR/2011/WD-css3-flexbox-20111129/
Previous Version: http://www.w3.org/TR/2011/WD-css3-flexbox-20110322/
Previous Version: http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/
Abstract: The specification describes a CSS box model optimized for user interface design. In the flex layout model, the children of a flex container can be laid out in any direction, and can “flex” their sizes, either growing to fill unused space or shrinking to avoid overflowing the parent. Both horizontal and vertical alignment of the children can be easily manipulated. Nesting of these boxes (horizontal inside vertical, or vertical inside horizontal) can be used to build layouts in two dimensions.
Editor: Tab Atkins Jr., Google, http://xanthir.com/contact/
Editor: fantasai, Mozilla, http://fantasai.inkedblade.net/contact
Editor: Rossen Atanassov, Microsoft, ratan@microsoft.com
Former Editor: Alex Mogilevsky, Microsoft Corporation, alexmog@microsoft.com
Former Editor: L. David Baron, Mozilla Corporation, dbaron@dbaron.org
Former Editor: Neil Deakin, Mozilla Corporation, enndeakin@gmail.com
Former Editor: Ian Hickson, formerly of Opera Software, ian@hixie.ch
Former Editor: David Hyatt, formerly of Netscape Corporation, hyatt@apple.com
!Issues List: <a href="http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325">http://dev.w3.org/csswg/css-flexbox-1/issues-lc-20140325</a>
Ignored Terms: column-*, auto, first formatted line, first letter
Link Defaults: css21 (property) margin/min-width/min-height/max-width/max-height, css-break-3 (property) break-after
</pre>
<style>
code.one-line { white-space: pre; }
.code-and-figure {
display: table;
margin: 0 auto;
border-spacing: 1em;
}
.code-and-figure > div {
display: table-cell;
vertical-align: middle;
}
ol[start="0"] { counter-reset: list -1; }
ol[start="0"],
ol.continue { list-style: none; }
ol[start="0"] > li,
ol.continue > li { position: relative; counter-increment: list; }
ol[start="0"] > li::before,
ol.continue > li::before { content: counter(list) "."; position: absolute; left: -4.5em; width: 4em; text-align: right; }
.compact, .compact li {
margin-top: 0;
margin-bottom: 0;
}
/* Overview catalog example */
#overview-example {
display:table;
margin: 0 auto 1em;
border-spacing: .5em 0;
min-width: 672px;
}
#overview-example > .col {
display: table-column;
background: hsl(60,100%,90%);
}
#overview-example > .desc {
display: table-cell;
vertical-align: top;
width: 300px;
padding: 1em 1em 0;
text-align: left;
border: thick solid hsl(60,80%,50%);
border-radius: 1em 1em 0 0;
border-bottom: none;
}
#overview-example > .desc > img {
margin: 0 auto;
display: block;
}
#overview-example > .desc > h1 {
background: transparent;
}
#overview-example > .buttons {
display: table-row;
}
#overview-example > .buttons > div {
display: table-cell;
border: thick solid hsl(60,80%,50%);
border-radius: 0 0 1em 1em;
border-top: none;
text-align: center;
}
#overview-example button {
background-color: hsl(120,100%,40%);
border: medium inset hsl(120,70%,40%);
border-radius: 1em;
padding: .5em;
font-weight: bold;
color: white;
font-size: 1.6em;
cursor: pointer;
width: 90%;
margin: 1em auto;
}
/* Visibility: Collapse example */
#visibility-collapse-example {
display: table;
width: 100%;
box-shadow: 3px 3px 10px #333;
}
#visibility-collapse-example > article,
#visibility-collapse-example > nav {
display: table-cell;
}
#visibility-collapse-example > article {
width: 100%;
background: white;
}
#visibility-collapse-example ul,
#visibility-collapse-example li {
list-style: none;
margin: 0;
padding: 0;
}
#visibility-collapse-example > nav > ul {
background: #444;
border-radius: 0.5em;
padding: 0.075em;
}
#visibility-collapse-example li {
padding: 0 0.5em;
background: #ddd;
color: black;
border-radius: 0.40em;
border: #444 solid 0.075em;
}
#visibility-collapse-example li li {
background: #444;
color: white;
margin: 0 -0.5em;
border-radius: 0;
}
#visibility-collapse-example li li:first-child {
border-radius: 0.375em 0.375em 0 0;
}
#visibility-collapse-example a {
background: transparent;
color: inherit;
}
#visibility-collapse-example > nav > ul > li:target,
#visibility-collapse-example > nav > ul > li:hover {
background: #888;
color: white;
}
#visibility-collapse-example > nav > ul > li:not(:target):not(:hover) > ul {
height: 0;
overflow: hidden;
}
#auto-bar {
overflow: hidden;
padding: .25em 1em;
background: #ddd;
list-style: none;
margin: 0;
border-radius: .3em;
}
#auto-bar > li {
float: left;
color: black;
margin: 0;
}
#auto-bar > li:first-child:after,
#auto-bar > li:first-child + li:after {
content: " | ";
white-space: pre;
}
#auto-bar > li > a {
display: inline-block;
padding: 0 .25em;
border-radius: .3em;
}
#auto-bar > li > a:not(:hover):not(:focus) {
text-decoration: none;
}
#auto-bar > li > a:hover {
color: #ddd;
background: #444;
}
#auto-bar > #login { float: right; }
.cross-auto-figure > div {
margin: 0 auto;
width: 70px;
background: #888;
padding: 0 .5em;
border-radius: 1em;
border: 1px solid transparent;
}
.cross-auto-figure > div > div {
border-spacing: 0;
display: table;
background: #ddd;
color: black;
text-align: center;
margin: .5em auto;
padding: .5em;
border-radius: .5em;
}
.axis { color: hsl( 0,80%,40%); }
.side { color: hsl(240,80%,50%); }
.size { color: hsl(120,80%,30%); }
</style>
<h2 id="intro">
Introduction</h2>
<p><em>This section is not normative.</em>
<p>
CSS 2.1 defined four layout modes — algorithms which determine
the size and position of boxes based on their relationships
with their sibling and ancestor boxes:
<ul class="compact">
<li>block layout, designed for laying out documents
<li>inline layout, designed for laying out text
<li>table layout, designed for laying out 2D data in a tabular format
<li>positioned layout, designed for very explicit positioning without much regard for other elements in the document
</ul>
<p>
This module introduces a new layout mode, <dfn export>flex layout</dfn>,
which is designed for laying out more complex applications and webpages.
<h3 id="overview">
Overview</h3>
<p><em>This section is not normative.</em>
<p>
Flex layout is superficially similar to block layout.
It lacks many of the more complex text- or document-centric properties
that can be used in block layout, such as
<a href="http://www.w3.org/TR/CSS21/visuren.html#floats">floats</a> and
<a href="http://www.w3.org/TR/css3-multicol/">columns</a>.
In return it gains simple and powerful tools
for distributing space and aligning content
in ways that webapps and complex web pages often need.
The contents of a flex container:
<ul>
<li>
can be laid out in any <a href="#flex-direction-property">flow direction</a>
(leftwards, rightwards, downwards, or even upwards!)
<li>
can have their display order <a href="#valuedef-row-reverse">reversed</a> or
<a href="#order-property">rearranged</a> at the style layer
(i.e., visual order can be independent of source and speech order)
<li>
can be laid out linearly along a single (<i title="main axis">main</i>) axis or
<a href="#flex-wrap-property">wrapped</a> into multiple lines along a secondary (<i title="cross axis">cross</i>) axis
<li>
can <a href="#flexibility">“flex” their sizes</a>
to respond to the available space
<li>
can be <a href="#alignment">aligned</a> with respect to their container or each other
<li>
can be dynamically <a href="#visibility-collapse">collapsed</a> or uncollapsed
along the <i>main axis</i> while preserving the container's <i>cross size</i>
</ul>
<div class='example'>
<p>
Here's an example of a catalog where each item has a title, an photo, a description, and a purchase button.
The designer's intention is that each entry has the same overall size,
that the photo be above the text,
and that the purchase buttons aligned at the bottom, regardless of the length of the item's description.
Flex layout makes many aspects of this design easy:
<ul>
<li>
The catalog uses flex layout to lay out rows of items horizontally,
and to ensure that items within a row are all equal-height.
Each entry is then itself a column flex container,
laying out its contents vertically.
<li>
Within each entry, the source document content is ordered logically
with the title first, followed by the description and the photo.
This provides a sensible ordering for speech rendering and in non-CSS browsers.
For a more compelling visual presentation, however,
'order' is used to pull the image up from later in the content to the top,
and 'align-self' is used to center it horizontally.
<li>
An <a href="#auto-margins"><span class=css>auto</span> margin</a> above the purchase button
forces it to the bottom within each entry box,
regardless of the height of that item's description.
</ul>
<pre>
<style>
#deals {
display: flex; /* Flex layout so items <a href="#propdef-align-self" title="Flex items stretch by default.">have equal height</a> */
flex-flow: row wrap; /* <a href="http://dev.w3.org/csswg/css3-flexbox/#flex-flow-property">Allow items to wrap into multiple lines</a> */
}
.sale-item {
display: flex; /* Lay out each item using flex layout */
flex-flow: column; /* <a href="#flex-flow-property">Lay out item's contents vertically</a> */
}
.sale-item > img {
order: -1; /* <a href="#order-property">Shift image before other content (in visual order)</a> */
align-self: center; /* <a href="#propdef-align-self">Center the image cross-wise (horizontally)</a> */
}
.sale-item > button {
margin-top: auto; /* <a href="#auto-margins">Auto top margin pushes button to bottom</a> */
}
</style></pre>
<pre>
<section id='deals'>
<section class='sale-item'>
<h1>Computer Starter Kit</h1>
<p>This is the best computer money can buy, if you don't have much money.
<ul>
<li>Computer
<li>Monitor
<li>Keyboard
<li>Mouse
</ul>
<img src='images/computer.jpg'
alt='You get: a white computer with matching peripherals.'>
<button>BUY NOW</button>
</section>
<section class='sale-item'>
…
</section>
…
</section></pre>
<figure>
<div id="overview-example">
<div class="col"></div>
<div class="col"></div>
<div class="desc">
<img src="images/computer.jpg" alt='You get: a white computer with matching keyboard and monitor.'>
<h1 id=quiet-pubrules-1 style="font-size: 1.4em;">Computer Starter Kit</h1>
<p>
This is the best computer money can buy,
if you don't have much money.
<ul>
<li>Computer
<li>Monitor
<li>Keyboard
<li>Mouse
</ul>
</div>
<div class="desc">
<img src="images/
C2A
printer.png" alt='You get: beautiful ASCII art.'>
<h1 id=quiet-pubrules-2 style="font-size: 1.4em;">Printer</h1>
<p>
Only capable of printing
ASCII art.
<ul>
<li>Paper and ink not included.
</ul>
</div>
<div class="buttons">
<div><button>BUY NOW</button></div>
<div><button>BUY NOW</button></div>
</div>
</div>
<figcaption>
An example rendering of the code above.
</figcaption>
</figure>
</div>
<h3 id="placement">
Module interactions</h3>
<p>
This module extends the definition of the 'display' property [[!CSS21]],
adding a new block-level and new inline-level display type,
and defining a new type of formatting context
along with properties to control its layout.
None of the properties defined in this module apply to the ''::first-line'' or ''::first-letter'' 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 [[CSS3VAL]], when combined with this module,
expands the definition of the <var><length></var> value type as used in this specification.
<p>In addition to the property-specific values listed in their definitions, all properties defined in this specification also accept the ''inherit'' keyword as their property value. For readability it has not been repeated explicitly.
<h2 id='box-model'>
Flex Layout Box Model and Terminology</h2>
<p>
A <dfn export>flex container</dfn> is the box generated by an element with a
computed 'display' of ''flex'' or ''inline-flex''.
In-flow children of a flex container are called <dfn export title="flex item" id="flex-item">flex items</dfn>
and are laid out using the flex layout model.
<p>
Unlike block and inline layout,
whose layout calculations are biased to the <a href="http://www.w3.org/TR/css3-writing-modes/#abstract-box">block and inline flow directions</a>,
flex layout is biased to the <dfn title="flex direction">flex directions</dfn>.
To make it easier to talk about flex layout,
this section defines a set of flex flow–relative terms.
The 'flex-flow' value determines how these terms map
to physical directions (top/right/bottom/left),
axes (vertical/horizontal), and sizes (width/height).
<figure>
<img src='images/flex-direction-terms.svg' width=665 height=277 alt>
<figcaption>
An illustration of the various directions and sizing terms as applied to a ''row'' flex container.
</figcaption>
</figure>
<dl id="main" export>
<dt class='axis'>main axis
<dt class='axis'>main dimension
<dd>
The <dfn title="main axis|main-axis">main axis</dfn> of a flex container is the primary axis along which <i>flex items</i> are laid out.
It extends in the <dfn>main dimension</dfn>.
<dt class='side'>main-start
<dt class='side'>main-end
<dd>
The <i>flex items</i> are placed within the container
starting on the <dfn>main-start</dfn> side
and going toward the <dfn>main-end</dfn> side.
<dt class='size'>main size
<dt class='size'>main size property
<dd>
A <i>flex item</i>’s width or height,
whichever is in the <i>main dimension</i>,
is the item's <dfn>main size</dfn>.
The <i>flex item</i>’s <dfn title="main size property|max main size property|min main size property">main size property</dfn> is
either the 'width' or 'height' property,
whichever is in the <i>main dimension</i>.
</dl>
<dl id="cross" export>
<dt class='axis'>cross axis
<dt class='axis'>cross dimension
<dd>
The axis perpendicular to the <i>main axis</i> is called the <dfn title="cross axis|cross-axis">cross axis</dfn>.
It extends in the <dfn>cross dimension</dfn>.
<dt class='side'>cross-start
<dt class='side'>cross-end
<dd>
<i>Flex lines</i> are filled with items and placed into the container
starting on the <dfn>cross-start</dfn> side of the flex container
and going toward the <dfn>cross-end</dfn> side.
<dt class='size'>cross size
<dt class='size'>cross size property
<dd>
The width or height of a <i>flex item</i>,
whichever is in the <i>cross dimension</i>,
is the item's <dfn>cross size</dfn>.
The <dfn title="cross size property|max cross size property|min cross size property">cross size property</dfn> is
whichever of 'width' or 'height' that is in the <i>cross dimension</i>.
</dl>
<!--
████████ ████ ██████ ████████ ██ ███ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ████
██ ██ ██ ██████ ████████ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ █████████ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██
████████ ████ ██████ ██ ████████ ██ ██ ██
-->
<h2 id='flex-containers'>
Flex Containers: the ''flex'' and ''inline-flex'' 'display' values</h2>
<pre class="propdef">
Name: display
New values: flex | inline-flex
</pre>
<dl dfn-type=value dfn-for=display>
<dt><dfn>flex</dfn>
<dd>
This value causes an element to generate a block-level <i>flex container</i> box.
<dt><dfn>inline-flex</dfn>
<dd>
This value causes an element to generate an inline-level <i>flex container</i> box.
</dl>
<p>
A <i>flex container</i> establishes a new <dfn export>flex formatting context</dfn> for its contents.
This is the same as establishing a block formatting context,
except that flex layout is used instead of block layout:
floats do not intrude into the flex container,
and the flex container's margins do not collapse with the margins of its contents.
<i>Flex containers</i> form a containing block for their contents
<a href="http://www.w3.org/TR/CSS21/visudet.html#containing-block-details">exactly like block containers do</a>. [[!CSS21]]
The 'overflow' property applies to <i>flex containers</i>.
<p>
Flex containers are not block containers,
and so some properties that were designed with the assumption of block layout don't apply in the context of flex layout.
In particular:
<ul>
<li>
all of the 'column-*' properties in the Multicol module have no effect on a flex container.
<li>
'float' and 'clear' have no effect on a <i>flex item</i>,
and do not take it out-of-flow.
However, the 'float' property can still affect box generation
by influencing the 'display' property's computed value.
<li>
'vertical-align' has no effect on a flex item.
<li>
the ''::first-line'' and ''::first-letter'' pseudo-elements do not apply to <a>flex containers</a>,
and <a>flex containers</a> do not contribute a <a>first formatted line</a> or <a>first letter</a>
to their ancestors.
Issue: When the Pseudo-Elements spec exists,
align this language with whatever algo we define for figuring out where to search for first-line/letter content.
</ul>
<p>
If an element's specified 'display' is ''inline-flex'',
then its 'display' property computes to ''flex''
in certain circumstances:
the table in <a href="http://www.w3.org/TR/CSS2/visuren.html#dis-pos-flo">CSS 2.1 Section 9.7</a>
is amended to contain an additional row,
with ''inline-flex'' in the "Specified Value" column
and ''flex'' in the "Computed Value" column.
<!--
████████ ██ ████████ ██ ██ ████ ████████ ████████ ██ ██ ██████
██ ██ ██ ██ ██ ██ ██ ██ ███ ███ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ████ ████ ██
██████ ██ ██████ ███ ██ ██ ██████ ██ ███ ██ ██████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ████████ ████████ ██ ██ ████ ██ ████████ ██ ██ ██████
-->
<h2 id='flex-items'>
Flex Items</h2>
Loosely speaking, the <a>flex items</a> of a <a>flex container</a>
are the in-flow boxes generated from the contents
of the element that generated the <a>flex container</a>.
<p>
Each in-flow child of a <i>flex container</i>
becomes a <i>flex item</i>,
and each contiguous run of text that is directly contained inside a <i>flex container</i>
is wrapped in an anonymous <i>flex item</i>.
However, an anonymous flex item that contains only
<a href="http://www.w3.org/TR/CSS21/text.html#white-space-prop">white space</a>
(i.e. characters that can be affected by the 'white-space' property)
is not rendered, as if it were ''display:none''.
<p>
A <i>flex item</i> establishes a new formatting context for its contents.
The type of this formatting context is determined by its 'display' value, as usual.
However, flex items themselves are flex-level boxes, not block-level boxes:
they participate in their container's flex formatting context,
not in a block formatting context.
<div class="example">
<p>Examples of flex items:
<pre>
<div style="display:flex">
<!-- flex item: block child -->
<div id="item1">block</div>
<!-- flex item: floated element; floating is ignored -->
<div id="item2" style="float: left;">float</div>
<!-- flex item: anonymous block box around inline content -->
anonymous item 3
<!-- flex item: inline child -->
<span>
item 4
<!-- flex items do not split around blocks -->
<div id=not-an-item>item 4</div>
item 4
</span>
</div></pre>
</div>
<p class="note">
Authors reading this spec may want to
<a href="#item-margins">skip past the following box-generation details</a>.
If the specified 'display-outside' of an in-flow child of an element that generates a <a>flex container</a>
is ''inline-level'',
it computes to ''block-level''.
(This effectively converts any inline 'display' values to their block equivalents.)
Note: Some values of 'display-outside' trigger the creation of anonymous boxes around the original box.
It's the outermost box, the direct child of the <a>flex container</a> box,
that becomes a <a>flex item</a>.
For example, given two contiguous child elements with ''display:table-cell'',
an anonymous table wrapper box around them becomes the <i>flex item</i>.
<p id="table-items">
On a flex item with ''display: table'', the table wrapper box becomes the <i>flex item</i>,
and the 'order' and 'align-self' properties apply to it.
The contents of any caption boxes contribute to the calculation of
the table wrapper box's min-content and max-content sizes.
However, like 'width' and 'height', the 'flex' longhands apply to the table box as follows:
the <i>flex item</i>’s final size is calculated
by performing layout as if the distance between
the table wrapper box's edges and the table box's content edges
were all part of the table box's border+padding area,
and the table box were the <i>flex item</i>.
<!--
███ ████████ ██████ ████████ ███████ ██████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ████████ ██████ ████████ ██ ██ ██████
█████████ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ████████ ██████ ██ ███████ ██████
-->
<h3 id='abspos-items'>
Absolutely-Positioned Flex Children</h3>
An absolutely-positioned child of a <i>flex container</i> does not participate in flex layout
beyond the <a href="#algo-flex-order">reordering step</a>.
Issue: This section is worded badly,
because 2.1 is incoherent about what "static position" really is.
The static position of an absolutely-positioned child of a <a>flex container</a>
is determined such that the child is positioned
as if it were the sole <a>flex item</a> in the <a>flex container</a>,
assuming both the child and the flex container
were fixed-size boxes of their used size.
In other words,
if the static position were conceived of as a point to which the absolutely-positioned element is aligned,
the static position of an absolutely-positioned child of a <a>flex container</a>
is determined by the alignment properties set on the <a>flex container</a> and the child
as if it were a zero-height, zero-width only-child in-flow flex item.
Furthermore, the absolutely-positioned child aligns itself in the given axis
to the static position in the same way:
<dl>
<dt>In the <a>main axis</a>
<dd>
If the <a>flex container's</a> 'justify-content' value
would align a single <a>flex item</a>
to the start, center, or end side of the <a>main axis</a>,
the static position in the <a>main axis</a> is the start, center, or end of the flex container's content box, respectively,
and the absolutely-positioned box aligns its outer start, center, or end to the static position point, respectively.
<dt>In the <a>cross axis</a>
<dd>
If the child's 'align-self' value,
if specified on a hypothetical single <a>flex item</a> child of the <a>flex container</a>,
would align that hypothetical child to the start, center, or end side of the <a>cross axis</a>,
the static position in the <a>cross axis</a> is the start, center, or end of the flex container's content box, respectively,
and the absolutely-positioned box aligns its outer start, center, or end to the static position point, respectively.
</dl>
<div class='example'>
The effect of this is that if you set, for example,
''align-content: center;'' on an absolutely-positioned child of a <a>flex container</a>,
the child will be centered in the <a>flex container's</a> <a>cross axis</a>.
(The static position will be in the center of the <a>cross axis</a>,
and the child will align its center with the static position.)
</div>
<h3 id='item-margins'>
Flex Item Margins and Paddings</h3>
<p>
The margins of adjacent <i>flex items</i> do not collapse.
Auto margins absorb extra space in the corresponding dimension and can be used for alignment
and to push adjacent flex items apart;
see <a href="#auto-margins">Aligning with <span class=css>auto</span> margins</a>.
<p>
Percentage margins and paddings on <i>flex items</i> are always resolved against their respective dimensions;
unlike blocks, they do not always resolve against the inline dimension of their containing block.
<h3 id='painting'>
Flex Item Z-Ordering</h3>
<p>
<i>Flex items</i> paint exactly the same as inline blocks [[!CSS21]],
except that 'order'-modified document order is used in place of raw document order,
and 'z-index'
values other than ''z-index/auto'' create a stacking context
even if 'position' is ''static''.
<p class="note">
Note: Descendants that are positioned outside a flex item still participate
in any stacking context established by the flex item.
<!--
██████ ███████ ██ ██ ███ ████████ ██████ ████████ ████████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ████████ ██████ ██████ ██ ██
██ ██ ██ ██ ██ █████████ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██
██████ ███████ ████████ ████████ ██ ██ ██ ██████ ████████ ████████
-->
<h3 id='visibility-collapse'>
Collapsed Items</h3>
<p>
Specifying ''visibility:collapse'' on a flex item
causes it to become a <dfn title="collapsed flex item|collapsed">collapsed flex item</dfn>,
producing an effect similar to ''visibility:collapse'' on a table-row or table-column:
the collapsed flex item is removed from rendering entirely,
but leaves behind a "strut" that keeps the flex line's cross-size stable.
Thus, if a flex container has only one flex line,
dynamically collapsing or uncollapsing items
is guaranteed to have no effect on the flex container's <i>cross size</i>
and won't cause the rest of the page's layout to "wobble".
Flex line wrapping <em>is</em> re-done after collapsing, however,
so the cross-size of a flex container with multiple lines might or might not change.
<p>
Though collapsed flex items aren't rendered,
they do appear in the <a href="http://www.w3.org/TR/CSS21/intro.html#formatting-structure">formatting structure</a>.
Therefore, unlike on ''display:none'' items [[!CSS21]],
effects that depend on a box appearing in the formatting structure
(like incrementing counters or running animations and transitions)
still operate on collapsed items.
<div class="example">
<p>In the following example,
a sidebar is sized to fit its content.
''visibility: collapse'' is used to dynamically hide parts of a navigation sidebar
without affecting its width, even though the widest item (“Architecture”)
is in a collapsed section.
<figure>
<figcaption>Sample rendering for example code below</figcaption>
<div id="visibility-collapse-example">
<!-- No, don't look at this source code, look at the other source code. -->
<nav>
<ul>
<li id="nav-about"><a href="#nav-about">About</a>
<ul>
<li><a href="#">History</a>
<li><a href="#">Mission</a>
<li><a href="#">People</a>
</ul>
<li id="nav-projects"><a href="#nav-projects">Projects</a>
<ul>
<li><a href="#">Art</a>
<li><a href="#">Architecture</a>
<li><a href="#">Music</a>
</ul>
<li id="nav-interact"><a href="#nav-interact">Interact</a>
<ul>
<li><a href="#">Blog</a>
<li><a href="#">Forums</a>
<li><a href="#">Events</a>
</ul>
</ul>
</nav>
<article>
Interesting Stuff to Read
</article>
</div>
</figure>
<pre>
<style>
@media (min-width: 60em) {
/* <a href="http://www.w3.org/TR/css3-mediaqueries/#width">two column layout only when enough room</a> (relative to default text size) */
header + div { display: flex; }
#main {
flex: 1; /* <a href="#flexibility">Main takes up all remaining space</a> */
order: 1; /* <a href="#order-property">Place it after (to the right of) the navigation</a> */
min-width: 12em; /* Optimize main content area sizing */
}
}
/* menu items use flex layout so that visibility:collapse will work */
nav > ul > li {
display: flex;
flex-flow: column;
}
/* dynamically collapse submenus when not targetted */
nav > ul > li:not(:target):not(:hover) > ul {
visibility: collapse;
}
</style>
…
</header>
<div>
<article id="main">
Interesting Stuff to Read
</article>
<nav>
<ul>
<li id="nav-about"><a href="#nav-about">About</a>
…
<li id="nav-projects"><a href="#nav-projects">Projects</a>
<ul>
<li><a href="…">Art</a>
<li><a href="…">Architecture</a>
<li><a href="…">Music</a>
</ul>
<li id="nav-interact"><a href="#nav-interact">Interact</a>
…
</ul>
</nav>
</div>
<footer>
…
</pre>
</div>
<p>
To compute the size of the strut, flex layout is first performed with all items uncollapsed,
and then re-run with each collapsed item replaced by a strut that maintains
the original cross-size of the item's original line.
See the <a href="#layout-algorithm">Flex Layout Algorithm</a>
for the normative definition of how ''visibility:collapse''
interacts with flex layout.
<p class='note'>
Note that using ''visibility:collapse'' on any flex items
will cause the flex layout algorithm to repeat partway through,
re-running the most expensive steps.
It's recommended that authors
8C51
continue to use ''display:none'' to hide items
if the items will not be dynamically collapsed and uncollapsed,
as that is more efficient for the layout engine.
(Since only part of the steps need to be repeated when 'visibility' is changed,
however, 'visibility: collapse' is still recommended for dynamic cases.)
<!--
██ ██ ████ ██ ██
███ ███ ██ ███ ██ ██ ██
████ ████ ██ ████ ██ ██ ██
██ ███ ██ ██ ██ ██ ██ ███████ █████████
██ ██ ██ ██ ████ ██ ██
██ ██ ██ ██ ███ ██ ██
██ ██ ████ ██ ██
-->
<h3 id="min-size-auto">
Implied Minimum Size of Flex Items</h3>
To provide a more reasonable default minimum size for <a>flex items</a>,
this specification introduces a new ''min-width/auto'' value
as the initial value of the 'min-width' and 'min-height' properties defined in CSS 2.1. [[!CSS21]]
<pre class="propdef partial">
Name: min-width, min-height
New values: auto
New initial value: auto
New computed value: the percentage as specified or the absolute length or a keyword
</pre>
<dl dfn-type=value dfn-for="min-width min-height">
<dt><dfn>auto</dfn>
<dd>
On a <a>flex item</a> whose 'overflow' is ''overflow/visible'' in the <a>main axis</a>,
when specified on the <a>flex item's</a> main-axis min-size property,
the following table gives the minimum size:
<table class=data>
<colgroup span=2></colgroup>
<colgroup span=1></colgroup>
<thead>
<tr>
<th>Clamped Size
<th>Transferred Size
<th>Minimum Size
<tbody>
<tr>
<td>
<td>
<td><var>content size</var>
<tr>
<td>✓
<td>
<td>min(<var>clamped size</var>, <var>content size</var>)
<tr>
<td>
<td>✓
<td>min(<var>transferred size</var>, <var>content size</var>)
<tr>
<td>✓
<td>✓
<td>min(<var>clamped size</var>, <var>content size</var>)
</table>
Where:
<dl>
<dt><var>clamped size</var>
<dd>
is defined if the item’s 'flex-basis' is ''main-size''
and its computed <a>main size property</a> is <a>definite</a>,
and is that size (clamped by its <a>max main size property</a> if it's <a>definite</a>).
<dt><var>transferred size</var>
<dd>
is defined if the item has an intrinsic aspect ratio
and its computed <a>cross size property</a> is <a>definite</a>,
and is that size (clamped by its <a title="min cross size property">min and max cross size properties</a> if they are <a>definite</a>),
converted through the aspect ratio.
<dt><var>content size</var>
<dd>
is the <a>min-content size</a> in the <a>main axis</a>,
clamped, if it has an aspect ratio, by any <a>definite</a> <a title="min cross size property">min and max cross size properties</a> converted through the aspect ratio,
and then further clamped by the <a>max main size property</a> if that is <a>definite</a>.
</dl>
Otherwise,
this keyword computes to ''0''
(unless otherwise defined by a future specification).
</dl>
<div class="note" id="min-size-opt">
<p>
Note that while a content-based minimum size is often appropriate,
and helps prevent content from overlapping or spilling outside its container,
in some cases it is not:
<p>
In particular, if flex sizing is being used for a major content area of a document,
it is better to set an explicit font-relative minimum width such as ''min-width: 12em''.
A content-based minimum width could result in a large table or large image
stretching the size of the entire content area into an overflow zone,
and thereby making lines of text gratuitously long and hard to read.
<p>
Note also, when content-based sizing is used on an item with large amounts of content,
the layout engine must traverse all of this content before finding its minimum size,
whereas if the author sets an explicit minimum, this is not necessary.
(For items with small amounts of content, however,
this traversal is trivial and therefore not a performance concern.)
</div>
<h2 id="flow-order">
Ordering and Orientation</h2>
<p>
The contents of a flex container can be laid out in any direction and in any order.
This allows an author to trivially achieve effects that would previously have required complex or fragile methods,
such as hacks using the 'float' and 'clear' properties.
This functionality is exposed through the 'flex-direction', 'flex-wrap', and 'order' properties.
<p class="note">
The reordering capabilities of flex layout intentionally affect
<em>only the visual rendering</em>,
leaving speech order and navigation based on the source order.
This allows authors to manipulate the visual presentation
while leaving the source order intact for non-CSS UAs and for
linear models such as speech and sequential navigation.
See <a href="#order-accessibility">Reordering and Accessibility</a>
and the <a href="#overview">Flex Layout Overview</a> for examples
that use this dichotomy to improve accessibility.
<p>
Authors <em>must not</em> use 'order' or the ''*-reverse'' values of 'flex-flow'/'flex-direction'
as a substitute for correct source ordering,
as that can ruin the accessibility of the document.
<!--
████████ ██ ████████ ██ ██ ████████ ████ ████████ ████████ ██████ ████████ ████ ███████ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ████ ██
██████ ██ ██████ ███ ███████ ██ ██ ██ ████████ ██████ ██ ██ ██ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ████
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███