forked from w3c/csswg-drafts
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathOverview.html
More file actions
executable file
·3854 lines (3013 loc) · 148 KB
/
Overview.html
File metadata and controls
executable file
·3854 lines (3013 loc) · 148 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
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html lang=en>
<head profile="http://www.w3.org/2006/03/hcard"><meta
content="text/html; charset=utf-8" http-equiv=Content-Type>
<title>CSS Regions Module Level 3</title>
<link href="../shared/style/default.css" rel=stylesheet type="text/css">
<script defer
src="http://test.csswg.org/harness/annotate.js#CSS3-REGIONS_DEV"
type="text/javascript"></script>
<style type="text/css">
#region-style-example p, #region-style-example pre {
clear: both;
}
#region_styling_illustration {
margin: 0px auto;
width: 70ex;
}
</style>
<link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet
type="text/css">
<link href="../shared/style/issues.css" rel=stylesheet type="text/css">
<link href="../shared/style/alternate-spec-style.css" id=st rel=stylesheet
title="alternate spec style" type="text/css">
<body>
<div class=head id=div-head>
<p><a href="http://www.w3.org/"><img alt=W3C height=53 id=mobile-logo
src="http://www.w3.org/2008/site/images/logo-w3c-mobile-lg" width=90></a>
<!--begin-logo-->
<p><a href="http://www.w3.org/"><img alt=W3C height=48
src="http://www.w3.org/Icons/w3c_home" width=72></a> <!--end-logo--></p>
<h1 id=css-regions-module>CSS Regions Module Level 3</h1>
<h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 August 2012</h2>
<dl>
<dt>This version:
<dd><a
href="http://www.w3.org/TR/2012/ED-css3-regions-20120829/">http://www.w3.org/csswg/css3-regions</a>
<dt>Latest version:
<dd><a
href="http://www.w3.org/TR/css3-regions/">http://www.w3.org/TR/css3-regions/</a>
<dt>Previous version:
<dd><a
href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/">http://www.w3.org/TR/2011/WD-css3-regions-20111129/</a>
<dt>Editors:
<dd class=vcard><span class=fn>Vincent Hardy</span>, <span
class=org>Adobe Systems, Inc.</span>, <span
class=email>vhardy@adobe.com</span>
<dd class=vcard><span class=fn>Alex Mogilevsky</span>, <span
class=org>Microsoft</span>, <span
class=email>alexmog@microsoft.com</span>
<dd class=vcard><span class=fn>Alan Stearns</span>, <span class=org>Adobe
Systems, Inc.</span>, <span class=email>stearns@adobe.com</span>
<dt>Issues List:
<dd><a
href="https://www.w3.org/Bugs/Public/buglist.cgi?product=CSS&component=Regions&resolution=---">Bugzilla
Bugs for CSS regions</a>
<dt>Discussion:
<dd><a
href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a>
with subject line "<code>[css3-regions] message topic</code>"
</dl>
<!--begin-copyright-->
<p class=copyright><a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
rel=license>Copyright</a> © 2012 <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>), 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>
<!--end-copyright-->
<hr title="Separator for header">
</div>
<h2 class="no-num no-toc" id=abstract>Abstract</h2>
<p>The CSS regions module allows content to flow across multiple areas
called regions. The regions are not necessarily contiguous in the document
order. The CSS regions module provides an advanced content flow mechanism,
which can be combined with positioning schemes as defined by other CSS
modules such as the Multi-Column Module <a href="#CSS3COL"
rel=biblioentry>[CSS3COL]<!--{{CSS3COL}}--></a> or the Grid Layout Module
<a href="#CSS3-GRID-LAYOUT"
rel=biblioentry>[CSS3-GRID-LAYOUT]<!--{{CSS3-GRID-LAYOUT}}--></a> to
position the regions where content flows.
<h2 class="no-num no-toc" id=status-of-this-document>Status of this
document</h2>
<p class="big note"><span class=note-prefix>Note </span>This document uses
an experimental style sheet. We welcome your feedback on the styles at <a
href="mailto:site-comments@w3.org">site-comments@w3.org</a>.</p>
<!--begin-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=%5Bcss3-regions%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
“css3-regions” in the subject, preferably like this:
“[<!---->css3-regions<!---->] <em>…summary of comment…</em>”
<p>This document was produced by the <a href="/Style/CSS/members">CSS
Working Group</a> (part of the <a href="/Style/">Style Activity</a>).
<p>This document was produced by a group operating under the <a
href="/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent
Policy</a>. W3C maintains a <a href="/2004/01/pp-impl/32061/status"
rel=disclosure>public list of any patent disclosures</a> made in
connection with the deliverables of the group; that page also includes
instructions for disclosing a patent. An individual who has actual
knowledge of a patent which the individual believes contains <a
href="/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a
href="/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the
W3C Patent Policy</a>.</p>
<!--end-status-->
<p>This draft is related to the drafts about Multi-column Layout <a
href="#CSS3COL" rel=biblioentry>[CSS3COL]<!--{{CSS3COL}}--></a>, Grid
Layout <a href="#CSS3GRID"
rel=biblioentry>[CSS3GRID]<!--{{CSS3GRID}}--></a>, Flexible Box Layout <a
href="#CSS3-FLEXBOX"
rel=biblioentry>[CSS3-FLEXBOX]<!--{{CSS3-FLEXBOX}}--></a>, and Template
Layout <a href="#CSS3LAYOUT"
rel=biblioentry>[CSS3LAYOUT]<!--{{CSS3LAYOUT}}--></a>.
<h2 class="no-num no-toc" id=table-of-contents>Table of contents</h2>
<!--begin-toc-->
<ul class=toc>
<li><a href="#introduction"><span class=secno>1. </span>Introduction</a>
<ul class=toc>
<li><a href="#named-flows-and-regions"><span class=secno>1.1.
</span>Named flows and region chains</a>
<li><a href="#region-styling"><span class=secno>1.2. </span>CSS Region
names and styling</a>
</ul>
<li><a href="#css-regions-concepts"><span class=secno>2. </span>CSS
regions concepts</a>
<ul class=toc>
<li><a href="#regions"><span class=secno>2.1. </span>Regions</a>
<li><a href="#region-chain"><span class=secno>2.2. </span>Region
chain</a>
<li><a href="#named-flow"><span class=secno>2.3. </span>Named flows</a>
<li><a href="#regions-flow-breaking-rules"><span class=secno>2.4.
</span>Regions flow breaking rules</a>
</ul>
<li><a href="#properties-and-rules"><span class=secno>3. </span>Properties
and rules</a>
<ul class=toc>
<li><a href="#the-flow-into-property"><span class=secno>3.1. </span>The
‘<code class=property>flow-into</code>’ property</a>
<li><a href="#the-flow-from-property"><span class=secno>3.2. </span>The
‘<code class=property>flow-from</code>’ property</a>
<li><a href="#region-flow-break"><span class=secno>3.3. </span>Region
flow break properties: ‘<code class=property>break-before</code>’,
‘<code class=property>break-after</code>’, ‘<code
class=property>break-inside</code>’</a>
<li><a href="#the-region-overflow-property"><span class=secno>3.4.
</span>The region-overflow property</a>
<li><a href="#the-at-region-style-rule"><span class=secno>3.5.
</span>The @region rule</a>
</ul>
<li><a href="#multi-column-regions"><span class=secno>4.
</span>Multi-column regions</a>
<li><a href="#pseudo_elements"><span class=secno>5.
</span>Pseudo-elements</a>
<ul class=toc>
<li><a href="#processing-model"><span class=secno>5.1. </span>Processing
model</a>
</ul>
<li><a href="#cssom_view_and_css_regions"><span class=secno>6.
</span>CSSOM</a>
<ul class=toc>
<li><a href="#the-namedflow-interface"><span class=secno>6.1. </span>The
NamedFlow interface</a>
<li><a href="#the-region-interface"><span class=secno>6.2. </span>The
Region interface</a>
<li><a href="#region-style-rule-interface"><span class=secno>6.3.
</span>The CSSRegionStyleRule interface</a>
<li><a href="#region-flow-layout-events"><span class=secno>6.4.
</span>Region flow layout events</a>
<li><a href="#cssomview-and-regions"><span class=secno>6.5.
</span>Clarifications on pre-existing APIs</a>
<ul class=toc>
<li><a
href="#cssomview-getclientrects-and-getboundingclientrect"><span
class=secno>6.5.1. </span><code class=idl>getClientRects()</code> and
<code>getBoundingClientRects()</code></a>
<li><a href="#cssomview-offset-attributes"><span class=secno>6.5.2.
</span><code class=idl>offsetTop</code>, <code
class=idl>offsetLeft</code>, <code class=idl>offsetWidth</code> and
<code class=idl>offsetWidth</code></a>
</ul>
</ul>
<li><a href="#regions-visual-formatting-details"><span class=secno>7.
</span>Regions visual formatting details</a>
<ul class=toc>
<li><a href="#regions-flow-content-box"><span class=secno>7.1.
</span>The Region Flow Content Box (RFBC)</a>
<ul class=toc>
<li><a href="#rfbc-width-resolution"><span class=secno>7.1.1.
</span>RFCB ‘<code class=property>width</code>’ resolution</a>
</ul>
<li><a href="#regions-visual-formatting-steps"><span class=secno>7.2.
</span>Regions visual formatting steps</a>
<ul class=toc>
<li><a href="#rfcb-flow-fragment-height-resolution"><span
class=secno>7.2.1. </span>Step 1: RFCB flow fragment height
resolution</a>
<ul class=toc>
<li><a href="#rfcb-flow-fragment-height-resolution-phase-1"><span
class=secno>7.2.1.1. </span>RFCB flow fragment height resolution,
Phase 1</a>
<li><a href="#rfcb-flow-fragment-height-resolution-phase-2"><span
class=secno>7.2.1.2. </span>RFCB flow fragment height resolution,
Phase 2</a>
</ul>
<li><a href="#regions-boxes-layout"><span class=secno>7.2.2.
</span>Step 2: region boxes layout</a>
<li><a href="#named-flows-layout"><span class=secno>7.2.3. </span>Step
3: named flows layout</a>
</ul>
<li><a href="#regions-visual-formatting-implementation-note"><span
class=secno>7.3. </span>Regions visual formatting: implementation
note</a>
<li><a href="#regions-visual-formatting-examples"><span class=secno>7.4.
</span>Regions visual formatting example</a>
<ul class=toc>
<li><a href="#step-1--phase-1-laying-out-rfcbs-with-us"><span
class=secno>7.4.1. </span>Step 1 - Phase 1: Laying out RFCBs with
used height of zero</a>
<li><a href="#step-1--phase-2-layout-flow-to-compute-t"><span
class=secno>7.4.2. </span>Step 1 - Phase 2: Layout flow to compute
the RFCBs' flow fragments heights</a>
<li><a href="#step-2-layout-document-and-regions-witho"><span
class=secno>7.4.3. </span>Step 2: Layout document and regions without
named flows</a>
<li><a href="#step-3-named-flows-layout"><span class=secno>7.4.4.
</span>Step 3: named flows layout</a>
</ul>
</ul>
<li><a href="#relation-to-document-events"><span class=secno>8.
</span>Relation to document events</a>
<li><a href="#relation-to-other-specifications"><span class=secno>9.
</span>Relation to other specifications</a>
<li><a href="#usecases"><span class=secno>10. </span>Use Cases</a>
<li><a href="#conformance"><span class=secno>11. </span>Conformance</a>
<li><a href="#changes"><span class=secno>12. </span>Changes</a>
<ul class=toc>
<li><a href="#changes_from_Aug_28_2012"><span class=secno>12.1.
</span>Changes from August 28<sup>th</sup> 2012 version</a>
<li><a href="#changes_from_May_03_2012"><span class=secno>12.2.
</span>Changes from May 3<sup>rd</sup> 2012 version</a>
<li><a href="#changes_from_November_29_2011"><span class=secno>12.3.
</span>Changes from November 29<sup>th</sup> 2011 version</a>
<li><a href="#changes_from_June_09_2011"><span class=secno>12.4.
</span>Changes from June 09<sup>th</sup> 2011 version</a>
</ul>
<li class=no-num><a href="#acknowledgments">Acknowledgments</a>
<li class=no-num><a href="#intro-example-code">Appendix A. Example Code
for Introduction</a>
<li class=no-num><a href="#references">References</a>
<ul class=toc>
<li class=no-num><a href="#normative-references">Normative
references</a>
<li class=no-num><a href="#other-references">Other references</a>
</ul>
<li class=no-num><a href="#index">Index</a>
<li class=no-num><a href="#property-index">Property index</a>
</ul>
<!--end-toc-->
<h2 id=introduction><span class=secno>1. </span>Introduction</h2>
<p><em>This section is non-normative.</em>
<p>Displaying the complex layouts of a typical magazine, newspaper, or
textbook on the web requires capabilities beyond those available in
existing CSS modules. Dynamic magazine layout in particular requires
flexibility in placement of boxes for content flows. This is the purpose
of the CSS regions module.
<div class=issue-marker data-bug_id=15733 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15733">Issue-15733</a>
<div class=issue-details>
<p class=short-desc>Should the region specification define a mechanism to
create blocks that can be regions with CSS syntax?</p>
</div>
</div>
<p>For more complex layouts, content needs to flow from one area of the
page to the next without limitation on the areas' sizes and positions.
These arbitrary areas are the target of specific content flows which this
document calls <a href="#named-flow0">named flows</a>. Each <a
href="#named-flow0">named flow</a> can be associated with a set of CSS
Regions called a region chain. CSS Regions are based on the rectangular
geometry of the CSS box model. Elements in a <a href="#named-flow0">named
flow</a> are taken out of the normal visual formatting and rendered in a
chain of CSS Regions.
<h3 id=named-flows-and-regions><span class=secno>1.1. </span>Named flows
and region chains</h3>
<p>Consider the layout illustrated in figure 1.
<div class=figure> <img
alt="multiple chained regions which should receive content from a flow"
src="images/intro-example-layout.svg" width=400>
<p class=caption>Layout requiring sophisticated content flow</p>
</div>
<p>The designer's intent is to position an image in box ‘<code
class=property>A</code>’ and to flow an article's content from box
‘<code class=css>1</code>’ through boxes ‘<code
class=css>2</code>’, ‘<code class=css>3</code>’ and ‘<code
class=css>4</code>’. Note that the second box should have two columns,
and the image is not contained in the article. Box ‘<code
class=css>4</code>’ should auto-size to render the remainder of the
article content that did not fit in the earlier boxes.
<p>Figure 2 shows an example of the intended visual rendering of the
content.
<div class=figure> <img
alt="Sample rendering showing a single thread of text flowing through a chain of regions"
src="images/regions-intro-rendering.png" width=450>
<p class=caption>Sample rendering for desired layout</p>
</div>
<p>There is no existing mechanism in CSS to associate the content with
these boxes arranged in this manner so that content flows as intended. The
CSS regions module properties provide that mechanism.
<p>The following example illustrates how the content of an
<code><article></code> element becomes a <a
href="#named-flow0">named flow</a> and how boxes marked with ‘<code
class=css>region1</code>’, ‘<code class=css>region2</code>’,
‘<code class=css>region3</code>’ and ‘<code
class=css>region4</code>’ IDs become CSS Regions that consume the
‘<code class=css>article_flow</code>’ content.
<div class=example>
<pre>
<style>
article {
<strong>flow-into: article_flow;</strong>
}
#region1, #region2, #region3, #region4 {
<strong>flow-from: article_flow;</strong>
}
</style>
</pre>
</div>
<p>The ‘<code class=css>article_flow</code>’ value on the ‘<a
href="#flow-into"><code class=property>flow-into</code></a>’ property
directs the <code>article</code> element to the ‘<code
class=css>article_flow</code>’ <a href="#named-flow0">named flow</a>.
Setting the ‘<a href="#flow-from"><code
class=property>flow-from</code></a>’ property on block containers to
‘<code class=css>article_flow</code>’ makes them CSS Regions and
associates the resulting region chain with the <a
href="#named-flow0">named flow</a>: the flow is ‘<code
class=css>poured</code>’ into the region chain.
<p>See <a href="#intro-example-code">Appendix A</a> for sample code using
grid layout that implements this example
<div class=issue-marker data-bug_id=16858 data-bug_status=ASSIGNED> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16858">Issue-16858</a>
<div class=issue-details>
<p class=short-desc>Should creation of regions from elements be
disallowed?</p>
</div>
</div>
<div class=note><span class=note-prefix>Note </span>
<p><strong>CSS Regions are independent from layout</strong></p>
<p>Any of the CSS layout facilities can be used to create, position and
size boxes that can become CSS Regions. Using a grid layout <a
href="#CSS3-GRID-LAYOUT"
rel=biblioentry>[CSS3-GRID-LAYOUT]<!--{{CSS3-GRID-LAYOUT}}--></a> is just
an example. The example could use a flexible box layout <a
href="#CSS3-FLEXBOX"
rel=biblioentry>[CSS3-FLEXBOX]<!--{{CSS3-FLEXBOX}}--></a> instead.</p>
<p>The CSS regions specification does not define a layout mechanism and is
meant to integrate with existing and future CSS layout facilities.</p>
<p><strong>CSS Regions do not have to be elements</strong></p>
<p>The CSS regions module is independent of the layout of boxes and the
mechanism used to create them. For simplicity, our example code in <a
href="#intro-example-code">Appendix A</a> uses elements to define the
boxes.</p>
<p>While the example uses elements for CSS Regions (since <a
href="#CSS3-GRID-LAYOUT"
rel=biblioentry>[CSS3-GRID-LAYOUT]<!--{{CSS3-GRID-LAYOUT}}--></a>
requires elements to create grid items) it is important to note that this
is not required. CSS Regions can be pseudo-elements, such as ‘<code
class=css>::before</code>’ and ‘<code class=css>::after</code>’.
The only requirement for an element or pseudo-element to become a CSS
Region is that it needs to be subject to CSS styling to receive the ‘<a
href="#flow-from"><code class=property>flow-from</code></a>’ property.
The CSS page template module (see <a href="#CSS3-PAGE-TEMPLATE"
rel=biblioentry>[CSS3-PAGE-TEMPLATE]<!--{{CSS3-PAGE-TEMPLATE}}--></a>)
proposes another mechanism to create stylable boxes that can become CSS
Regions with the <code class=css>@slot</code> syntax.</p>
</div>
<h3 id=region-styling><span class=secno>1.2. </span>CSS Region names and
styling</h3>
<div class=issue-marker data-bug_id=16859 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16859">Issue-16859</a>
<div class=issue-details>
<p class=short-desc>Reconsider using @rule for region styling</p>
</div>
</div>
<p>Content can be styled depending on the CSS Region it flows into. It is
an extension of pseudo-element styling such as <a
href="http://www.w3.org/TR/css3-selectors/#first-line"> <code
class=css>::first-line</code> </a> which applies a particular style to a
fragment of content. With CSS Region styling, additional selectors may
apply depending on the CSS Region into which content flows.
<p>In our example, the designer wants to make text flowing into #region1
dark blue and bold.
<p>This design can be expressed as shown below.
<div class=example>
<pre>
<style>
@region #region1 {
p {
color: #0C3D5F;
font-weight: bold;
}
</style></pre>
</div>
<p>The <code class=css>@region #region1</code> rule limits its selectors to
content flowing into <code class=css>#region1</code>. The following figure
shows how the rendering changes if we apply styling specific to
<code>#region1</code>. Note how less text fits into this box now that the
‘<code class=property>font-weight</code>’ is bold instead of normal.
<div class=figure> <img
alt="Illustrate how changing region styling affects the flow of content."
src="images/region-styling.png" width=450>
<p class=caption>Different rendering with a different region styling</p>
</div>
<h2 id=css-regions-concepts><span class=secno>2. </span>CSS regions
concepts</h2>
<h3 id=regions><span class=secno>2.1. </span>Regions</h3>
<div class="issue-marker wrapper">
<div class=issue-marker data-bug_id=15186 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15186">Issue-15186</a>
<div class=issue-details>
<p class=short-desc>Is a mechanism to auto-generate regions necessary in
order to support reusable style sheets?</p>
</div>
</div>
<div class=issue-marker data-bug_id=15187 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15187">Issue-15187</a>
<div class=issue-details>
<p class=short-desc>Explain how regions and pages interact. How can
regions be placed onto certain pages, and how can they be positiond
wrt. pages.</p>
</div>
</div>
</div>
<p id=region> A <dfn id=css-region title=region>CSS Region</dfn> is a block
container that has an associated <a href="#named-flow0"><em><span>named
flow</span></em></a> (see the ‘<a href="#flow-from"><code
class=property>flow-from</code></a>’ property).
<h3 id=region-chain><span class=secno>2.2. </span>Region chain</h3>
<p>A <dfn id=region-chain0>region chain</dfn> is the sequence of regions
that are associated with a <a href="#named-flow0">named flow</a>. <a
href="#css-region" title=region>CSS Regions</a> in a region chain receive
content from the named flow following their order in the chain. <a
href="#css-region" title=region>CSS Regions</a> are organized into a <span
title=region-chain>region chain</span> according to the document order.
<h3 id=named-flow><span class=secno>2.3. </span>Named flows</h3>
<p>A <dfn id=named-flow0>named flow</dfn> is the ordered sequence of
elements associated with a flow with a given identifier. Elements in a <a
href="#named-flow0">named flow</a> are ordered according to the document
order.
<p>Elements are placed into a <a href="#named-flow0">named flow</a> with
the ‘<a href="#flow-into"><code class=property>flow-into</code></a>’
property. The elements in a <a href="#named-flow0">named flow</a> are laid
out in the <span title=region-chain>region chain</span> that is associated
with this <a href="#named-flow0">named flow</a>.
<p>Content from a <a href="#named-flow0">named flow</a> is broken up
between regions according to the regions flow breaking rules.
<p>A <a href="#named-flow0">named flow</a> is created when at least one
element is moved into the flow with the given identifier or when at least
one CSS Region requests content from that flow.
<h3 id=regions-flow-breaking-rules><span class=secno>2.4. </span>Regions
flow breaking rules</h3>
<p>Breaking a <a href="#named-flow0">named flow</a> across a region chain
is similar to breaking a document's content across pages (see <a
href="#CSS3PAGE" rel=biblioentry>[CSS3PAGE]<!--{{CSS3PAGE}}--></a>) or a
multi-column element's content across column boxes (see <a href="#CSS3COL"
rel=biblioentry>[CSS3COL]<!--{{CSS3COL}}--></a>). One difference is that
page boxes are generated based on the available content whereas a region
chain is a set of recipient boxes for the <a href="#named-flow0">named
flow</a> content whose dynamic generation is not in the scope of this
specification.
<p>Each CSS Region in turn consumes content from its associated <a
href="#named-flow0">named flow</a>. The <a href="#named-flow0">named
flow</a> content is positioned in the <dfn id=current-region
title=current-region>current region</dfn> until a natural or forced region
break occurs, at which point the next region in the <span
title=region-chain>region chain</span> becomes the <a
href="#current-region" title=current-region>current region</a>. If there
are no more <a href="#css-region">region</a>s in the region chain and
there is still content in the flow, the positioning of the remaining
content is controlled by the ‘<a href="#region-overflow"><code
class=property>region-overflow</code></a>’ property on the last <a
href="#css-region">region</a> in the chain.
<p>The CSS regions module follows the fragmentation rules defined in the
CSS Fragmentation Module Level 3 (see <a href="#CSS3-BREAK"
rel=biblioentry>[CSS3-BREAK]<!--{{!CSS3-BREAK}}--></a>).
<h2 id=properties-and-rules><span class=secno>3. </span>Properties and
rules</h2>
<h3 id=the-flow-into-property><span class=secno>3.1. </span>The ‘<a
href="#flow-into"><code class=property>flow-into</code></a>’ property</h3>
<div class="issue-marker wrapper">
<div class=issue-marker data-bug_id=15811 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15811">Issue-15811</a>
<div class=issue-details>
<p class=short-desc>Creating a named flow from external resource</p>
</div>
</div>
<div class=issue-marker data-bug_id=16002 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16002">Issue-16002</a>
<div class=issue-details>
<p class=short-desc>flow-into and anonymous blocks or fix-ups</p>
</div>
</div>
<div class=issue-marker data-bug_id=16527 data-bug_status=ASSIGNED> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16527">Issue-16527</a>
<div class=issue-details>
<p class=short-desc>[Shadow]: getFlowByName and shadow DOM</p>
</div>
</div>
</div>
<p>The ‘flow-into’ property can place an element into a <a
href="#named-flow0">named flow</a>. Elements that belong to the same flow
are laid out in the region chain associated with that flow.
<table class=propdef summary="flow property definition">
<tbody>
<tr>
<th>Name:
<td><dfn id=flow-into>flow-into</dfn>
<tr>
<th>Value:
<td><ident> | none | inherit
<tr>
<th>Initial:
<td>none
<tr>
<th>Applies to:
<td>any element.
<p>The ‘<a href="#flow-into"><code
class=property>flow-into</code></a>’ property does not apply to any
<a
href="http://www.w3.org/TR/selectors/#pseudo-elements">pseudo-element</a>
such as <code class=css>::first-line</code>, <code
class=css>::first-letter</code>, <code class=css>::before</code> or
<code class=css>::after</code>.
<tr>
<th>Inherited:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Media:
<td>visual
<tr>
<th>Computed value:
<td>as specified
</table>
<dl>
<dt>none
<dd>The element is not moved to a <a href="#named-flow0">named flow</a>
and normal CSS processing takes place.
<dt><a
href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a>
<dd>The element is taken out of its parent's flow and placed into the flow
with the name ‘<code class=css><ident></code>’. The element is
said to have a <dfn id=specified-flow>specified flow</dfn>. The values
‘<code class=property>none</code>’, ‘<code
class=property>inherit</code>’, ‘<code
class=property>default</code>’, ‘<code class=property>auto</code>’
and ‘<code class=property>initial</code>’ are invalid flow names.
</dl>
<p>A <a href="#named-flow0">named flow</a> needs to be associated with a
region chain (one or more CSS regions) for its elements to be visually
formatted. If no region chain is associated with a given <a
href="#named-flow0">named flow</a>, the elements in the <a
href="#named-flow0">named flow</a> are not rendered: they do not generate
boxes and are not displayed.
<p>The children of an element with a specified flow may themselves have a
specified flow.
<p>If an element has the same specified flow as one of its ancestors, it
becomes a sibling of its ancestor for the purpose of layout in the region
chain laying out content from that flow.
<p>The ‘<a href="#flow-into"><code class=property>flow-into</code></a>’
property does not affect the CSS cascade and inheritance for the elements
on which it is specified. The ‘<a href="#flow-into"><code
class=property>flow-into</code></a>’ property affects the visual
formatting of elements placed into a <a href="#named-flow0">named flow</a>
and of the region chain laying out content from a <a
href="#named-flow0">named flow</a>.
<p>The edges of the first CSS region in a region chain associated with a <a
href="#named-flow0">named flow</a> establish the rectangle that is the <a
href="http://www.w3.org/TR/CSS2/visudet.html#containing-block-details">containing
block</a> used for absolutely positioned elements in the <a
href="#named-flow0">named flow</a> which do not have an ancestor with a
‘<code class=property>position</code>’ of ‘<code
class=property>absolute</code>’, ‘<code
class=property>relative</code>’ or ‘<code
class=property>fixed</code>’ (see <a href="#CSS21"
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>). That first CSS region
rectangle is used as the containing block instead of the initial
containing block. This does not affect fixed position elements in the <a
href="#named-flow0">named flow</a> - they are still positioned relative to
the viewport or page area even if they have been redirected to a named
flow.
<p>The first region defines the <a
href="http://www.w3.org/TR/css3-writing-modes/#writing-mode">writing
mode</a> for the entire flow. The writing mode on subsequent regions is
ignored.
<p>Elements in a <a href="#named-flow0">named flow</a> are sequenced in
document order.
<div class=note><span class=note-prefix>Note </span>
<p>The ‘<a href="#flow-into"><code
class=property>flow-into</code></a>’ property moves an element into the
flow and the interplay with selectors should be considered carefully.</p>
<p>For example,</p>
<pre>table {flow-into: table-content}</pre>
<p>will move all tables in the ‘<code
class=property>table-content</code>’ <a href="#named-flow0">named
flow</a>. However, the</p>
<pre>table > * {flow-into: table-content} ...</pre>
<p>selector will move all immediate children of all table elements into
the ‘table-content’ <a href="#named-flow0">named flow</a> (which may
be useful as it will usually result, if the immediate children are rows,
in merging rows of multiple tables), but the</p>
<pre>table * {flow-into: table-content}</pre>
<p>selector will move all descendants of table elements into the
‘table-content’ <a href="#named-flow0">named flow</a>, transforming
the element tree into a flat list in order of opening tags (which is
probably not intentional). This will make all the descendants of table
elements siblings in the <a href="#named-flow0">named flow</a>. Having
the descendants become siblings in the <a href="#named-flow0">named
flow</a> results in a different processing (see <a
href="http://www.w3.org/TR/2011/REC-CSS2-20110607/tables.html#anonymous-boxes">CSS
2.1‘<code class=css>s anonymous table objects</code></a>). This note
illustrates how authors must exercise caution when choosing a particular
selector for setting the ’flow-into' property to avoid unintended
results.</p>
</div>
<h3 id=the-flow-from-property><span class=secno>3.2. </span>The ‘<a
href="#flow-from"><code class=property>flow-from</code></a>’ property</h3>
<p>The ‘<a href="#flow-from"><code class=property>flow-from</code></a>’
property makes a block container a region and associates it with a <a
href="#named-flow0">named flow</a>.
<table class=propdef summary="flow-from property definition">
<tbody>
<tr>
<th>Name:
<td><dfn id=flow-from>flow-from</dfn>
<tr>
<th>Value:
<td><ident> | none | inherit
<tr>
<th>Initial:
<td>none
<tr>
<th>Applies to:
<td>Non-replaced <a
href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block
containers</a>. <br>
This might be expanded in future versions of the specification to allow
other types of containers to receive flow content.
<tr>
<th>Inherited:
<td>no
<tr>
<th>Percentages:
<td>N/A
<tr>
<th>Media:
<td>visual
<tr>
<th>Computed value:
<td>as specified
</table>
<dl>
<dt><strong>none</strong>
<dd>The block container is not a <a href="#css-region"
title=region>region</a>.
<dt><strong><ident></strong>
<dd> If the ‘<code class=property>content</code>’ property computes to
something else than ‘<code class=property>normal</code>’, the block
container does not become a <span>CSS Region</span>. If the ‘<code
class=property>content</code>’ property computes to ‘<code
class=property>normal</code>’, then the block container becomes a
<span>CSS Region</span> and is ordered in a <a
href="#region-chain0">region chain</a> according to its document order.
The content from the flow with the <a
href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a>
name will be <a href="#region-flow-break">broken into fragments</a> and
visually formatted in the <a
href="http://www.w3.org/TR/CSS21/visuren.html#principal-box">principal
boxes</a> of the <a href="#css-region">regions</a> in the <a
href="#region-chain0">region chain</a>. <br>
If there is no flow with name <ident>, then the block container
does not format any content visually. <br>
Likewise, if the block container is part of the flow with name
<ident>, then the block container does not format any content
visually.
</dl>
<div class=issue-marker data-bug_id=16819 data-bug_status=ASSIGNED> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16819">Issue-16819</a>
<div class=issue-details>
<p class=short-desc>No display when combining flow-from and flow-into is
bad</p>
</div>
</div>
<p>A <span>CSS Region</span>‘<code class=css>s document children are not
visually formatted unless they are directed to a <a
href="#named-flow0">named flow</a> with an associated <a
href="#region-chain0">region chain</a>.</code>
<div class=note><span class=note-prefix>Note </span>
<p>An block container becomes a <span>CSS Region</span> when its
’flow-from' property is set to a valid <ident> value, even if
there is no content contributing to the referenced flow. For example:</p>
<pre>
<style>
.article{
flow-into: thread;
}
.region{
flow-from: thread;
}
</style>
<html>
<body>
<div class=region>div content</div>
</body>
</html>
</pre>
There is no element matching the <code>.article</code> selector and
therefore no content in the <code>thread</code> flow. However, the block
container matching the <a href="#css-region"><code>.region</code></a>
selector is still associated with that empty <a href="#named-flow0">named
flow</a> and, consequently, its children are not formatted visually.</div>
<div class=note><span class=note-prefix>Note </span>
<p>At the time of this note-writing, the <code>display</code> values that
always result in a non-replaced block container include
<code>block</code>, <code>inline-block</code>, <code>table-cell</code>,
<code>table-caption</code>, and <code>list-item</code>. All of these
display values work as regions with non-replaced elements.
</div>
<div class="issue-marker wrapper">
<div class=issue-marker data-bug_id=15189 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15189">Issue-15189</a>
<div class=issue-details>
<p class=short-desc>Should regions be non-breakable?</p>
</div>
</div>
<div class=issue-marker data-bug_id=15824 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15824</a>
<div class=issue-details>
<p class=short-desc>Should regions not create a new stacking context?</p>
</div>
</div>
<div class=issue-marker data-bug_id=15827 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15827</a>
<div class=issue-details>
<p class=short-desc>Specify behavior of stacking contexts that are split
between regions</p>
</div>
</div>
<div class=issue-marker data-bug_id=16636 data-bug_status=NEW> <a
href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16636">Issue-16636</a>
<div class=issue-details>
<p class=short-desc>Should re-introduce region order</p>
</div>
</div>
</div>
<p><a href="#css-region" title=region>CSS Regions</a> create a new <a
href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking
context</a>. <a href="#css-region" title=region>CSS Regions</a> establish
a new <a
href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block
formatting Context</a>.
<div class=note><span class=note-prefix>Note </span>
<p>With <a href="#region-chain0">region chains</a>, an element may be
split across multiple boxes and these boxes may overlap (for example if
they are absolutely positioned). So fragments of the same element can
overlap each other. Since each element has a single z-index, it would be
required to find another mechanism to decide in which order
the fragments are rendered. Since each <span>CSS Region</span> creates a
new stacking context, it is clear that each fragment is rendered
separately and their rendering order follows the regular CSS rendering
model.</p>