changeset
[css3-regions] rename region-overflow to region-fragment
Thu, 27 Sep 2012 15:20:14 -0700
- author
- Alan Stearns <stearns@adobe.com>
- date
- Thu, 27 Sep 2012 15:20:14 -0700
- changeset 6796
- aa526b29b5a0
- parent 6795
- 7d499c573981
- child 6797
- cd81dda906b1
[css3-regions] rename region-overflow to region-fragment
| css3-regions/Overview.html | file | annotate | diff | comparison | revisions | |
| css3-regions/Overview.src.html | file | annotate | diff | comparison | revisions |
1.1 --- a/css3-regions/Overview.html Thu Sep 27 14:53:18 2012 +0200 1.2 +++ b/css3-regions/Overview.html Thu Sep 27 15:20:14 2012 -0700 1.3 @@ -2,15 +2,27 @@ 1.4 "http://www.w3.org/TR/html4/strict.dtd"> 1.5 1.6 <html lang=en> 1.7 - <head profile="http://www.w3.org/2006/03/hcard"><meta 1.8 - content="text/html; charset=utf-8" http-equiv=Content-Type> 1.9 - 1.10 + <head 1.11 + profile="http://dublincore.org/documents/2008/08/04/dc-html/ http://www.w3.org/2006/03/hcard"> 1.12 + <meta content="text/html; charset=utf-8" http-equiv=Content-Type> 1.13 <title>CSS Regions Module Level 3</title> 1.14 + 1.15 + <link href="http://purl.org/dc/terms/" rel=schema.DC> 1.16 + <meta content="CSS Regions Module Level 3" name=DC.title> 1.17 + <meta content=text name=DC.type> 1.18 + <meta content=2012-09-27 name=DC.issued> 1.19 + <meta content="Vincent Hardy" name=DC.creator> 1.20 + <meta content="Alex Mogilevsky" name=DC.creator> 1.21 + <meta content="Alan Stearns" name=DC.creator> 1.22 + <meta content=W3C name=DC.publisher> 1.23 + <meta content="http://www.w3.org/TR/2012/ED-css3-regions-20120927/" 1.24 + name=DC.identifier> 1.25 + <link href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" 1.26 + rel=DC.rights> 1.27 <link href="../shared/style/default.css" rel=stylesheet type="text/css"> 1.28 - <script defer 1.29 - src="http://test.csswg.org/harness/annotate.js#CSS3-REGIONS_DEV" 1.30 - type="text/javascript"></script> 1.31 - 1.32 + <script defer=defer 1.33 + src="http://test.csswg.org/harness/annotate.js#CSS3-REGIONS_DEV" 1.34 + type="text/javascript"></script> 1.35 <style type="text/css"> 1.36 #region-style-example p, #region-style-example pre { 1.37 clear: both; 1.38 @@ -22,10 +34,10 @@ 1.39 } 1.40 </style> 1.41 <link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet 1.42 - type="text/css"> 1.43 + type="text/css"> 1.44 <link href="../shared/style/issues.css" rel=stylesheet type="text/css"> 1.45 <link href="../shared/style/alternate-spec-style.css" id=st rel=stylesheet 1.46 - title="alternate spec style" type="text/css"> 1.47 + title="alternate spec style" type="text/css"> 1.48 1.49 <body> 1.50 <div class=head id=div-head> 1.51 @@ -34,17 +46,18 @@ 1.52 <!--begin-logo--> 1.53 1.54 <p><a href="http://www.w3.org/"><img alt=W3C height=48 1.55 - src="http://www.w3.org/Icons/w3c_home" width=72></a> <!--end-logo--></p> 1.56 + src="http://www.w3.org/Icons/w3c_home" width=72></a> <!--end-logo--> 1.57 1.58 <h1 id=css-regions-module>CSS Regions Module Level 3</h1> 1.59 1.60 - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 August 2012</h2> 1.61 + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 27 September 1.62 + 2012</h2> 1.63 1.64 <dl> 1.65 <dt>This version: 1.66 1.67 <dd><a 1.68 - href="http://www.w3.org/TR/2012/ED-css3-regions-20120829/">http://www.w3.org/csswg/css3-regions</a> 1.69 + href="http://www.w3.org/TR/2012/ED-css3-regions-20120927/">http://www.w3.org/csswg/css3-regions</a> 1.70 1.71 <dt>Latest version: 1.72 1.73 @@ -202,8 +215,8 @@ 1.74 ‘<code class=property>break-after</code>’, ‘<code 1.75 class=property>break-inside</code>’</a> 1.76 1.77 - <li><a href="#the-region-overflow-property"><span class=secno>3.4. 1.78 - </span>The region-overflow property</a> 1.79 + <li><a href="#the-region-fragment-property"><span class=secno>3.4. 1.80 + </span>The region-fragment property</a> 1.81 1.82 <li><a href="#the-at-region-style-rule"><span class=secno>3.5. 1.83 </span>The @region rule</a> 1.84 @@ -362,10 +375,10 @@ 1.85 1.86 <div class=issue-marker data-bug_id=15733 data-bug_status=NEW> <a 1.87 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15733">Issue-15733</a> 1.88 - 1.89 + 1.90 <div class=issue-details> 1.91 <p class=short-desc>Should the region specification define a mechanism to 1.92 - create blocks that can be regions with CSS syntax?</p> 1.93 + create blocks that can be regions with CSS syntax? 1.94 </div> 1.95 </div> 1.96 1.97 @@ -387,7 +400,7 @@ 1.98 <div class=figure> <img 1.99 alt="multiple chained regions which should receive content from a flow" 1.100 src="images/intro-example-layout.svg" width=400> 1.101 - <p class=caption>Layout requiring sophisticated content flow</p> 1.102 + <p class=caption>Layout requiring sophisticated content flow 1.103 </div> 1.104 1.105 <p>The designer's intent is to position an image in box ‘<code 1.106 @@ -405,7 +418,7 @@ 1.107 <div class=figure> <img 1.108 alt="Sample rendering showing a single thread of text flowing through a chain of regions" 1.109 src="images/regions-intro-rendering.png" width=450> 1.110 - <p class=caption>Sample rendering for desired layout</p> 1.111 + <p class=caption>Sample rendering for desired layout 1.112 </div> 1.113 1.114 <p>There is no existing mechanism in CSS to associate the content with 1.115 @@ -450,15 +463,15 @@ 1.116 1.117 <div class=issue-marker data-bug_id=16858 data-bug_status=ASSIGNED> <a 1.118 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16858">Issue-16858</a> 1.119 - 1.120 + 1.121 <div class=issue-details> 1.122 <p class=short-desc>Should creation of regions from elements be 1.123 - disallowed?</p> 1.124 + disallowed? 1.125 </div> 1.126 </div> 1.127 1.128 <div class=note><span class=note-prefix>Note </span> 1.129 - <p><strong>CSS Regions are independent from layout</strong></p> 1.130 + <p><strong>CSS Regions are independent from layout</strong> 1.131 1.132 <p>Any of the CSS layout facilities can be used to create, position and 1.133 size boxes that can become CSS Regions. Using a grid layout <a 1.134 @@ -466,17 +479,17 @@ 1.135 rel=biblioentry>[CSS3-GRID-LAYOUT]<!--{{CSS3-GRID-LAYOUT}}--></a> is just 1.136 an example. The example could use a flexible box layout <a 1.137 href="#CSS3-FLEXBOX" 1.138 - rel=biblioentry>[CSS3-FLEXBOX]<!--{{CSS3-FLEXBOX}}--></a> instead.</p> 1.139 + rel=biblioentry>[CSS3-FLEXBOX]<!--{{CSS3-FLEXBOX}}--></a> instead. 1.140 1.141 <p>The CSS regions specification does not define a layout mechanism and is 1.142 - meant to integrate with existing and future CSS layout facilities.</p> 1.143 - 1.144 - <p><strong>CSS Regions do not have to be elements</strong></p> 1.145 + meant to integrate with existing and future CSS layout facilities. 1.146 + 1.147 + <p><strong>CSS Regions do not have to be elements</strong> 1.148 1.149 <p>The CSS regions module is independent of the layout of boxes and the 1.150 mechanism used to create them. For simplicity, our example code in <a 1.151 href="#intro-example-code">Appendix A</a> uses elements to define the 1.152 - boxes.</p> 1.153 + boxes. 1.154 1.155 <p>While the example uses elements for CSS Regions (since <a 1.156 href="#CSS3-GRID-LAYOUT" 1.157 @@ -490,7 +503,7 @@ 1.158 The CSS page template module (see <a href="#CSS3-PAGE-TEMPLATE" 1.159 rel=biblioentry>[CSS3-PAGE-TEMPLATE]<!--{{CSS3-PAGE-TEMPLATE}}--></a>) 1.160 proposes another mechanism to create stylable boxes that can become CSS 1.161 - Regions with the <code class=css>@slot</code> syntax.</p> 1.162 + Regions with the <code class=css>@slot</code> syntax. 1.163 </div> 1.164 1.165 <h3 id=region-styling><span class=secno>1.2. </span>CSS Region names and 1.166 @@ -498,9 +511,9 @@ 1.167 1.168 <div class=issue-marker data-bug_id=16859 data-bug_status=NEW> <a 1.169 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16859">Issue-16859</a> 1.170 - 1.171 + 1.172 <div class=issue-details> 1.173 - <p class=short-desc>Reconsider using @rule for region styling</p> 1.174 + <p class=short-desc>Reconsider using @rule for region styling 1.175 </div> 1.176 </div> 1.177 1.178 @@ -536,7 +549,7 @@ 1.179 <div class=figure> <img 1.180 alt="Illustrate how changing region styling affects the flow of content." 1.181 src="images/region-styling.png" width=450> 1.182 - <p class=caption>Different rendering with a different region styling</p> 1.183 + <p class=caption>Different rendering with a different region styling 1.184 </div> 1.185 1.186 <h2 id=css-regions-concepts><span class=secno>2. </span>CSS regions 1.187 @@ -547,20 +560,20 @@ 1.188 <div class="issue-marker wrapper"> 1.189 <div class=issue-marker data-bug_id=15186 data-bug_status=NEW> <a 1.190 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15186">Issue-15186</a> 1.191 - 1.192 + 1.193 <div class=issue-details> 1.194 <p class=short-desc>Is a mechanism to auto-generate regions necessary in 1.195 - order to support reusable style sheets?</p> 1.196 + order to support reusable style sheets? 1.197 </div> 1.198 </div> 1.199 1.200 <div class=issue-marker data-bug_id=15187 data-bug_status=NEW> <a 1.201 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15187">Issue-15187</a> 1.202 - 1.203 + 1.204 <div class=issue-details> 1.205 <p class=short-desc>Explain how regions and pages interact. How can 1.206 regions be placed onto certain pages, and how can they be positiond 1.207 - wrt. pages.</p> 1.208 + wrt. pages. 1.209 </div> 1.210 </div> 1.211 </div> 1.212 @@ -621,8 +634,8 @@ 1.213 href="#current-region" title=current-region>current region</a>. If there 1.214 are no more <a href="#css-region">region</a>s in the region chain and 1.215 there is still content in the flow, the positioning of the remaining 1.216 - content is controlled by the ‘<a href="#region-overflow"><code 1.217 - class=property>region-overflow</code></a>’ property on the last <a 1.218 + content is controlled by the ‘<a href="#region-fragment"><code 1.219 + class=property>region-fragment</code></a>’ property on the last <a 1.220 href="#css-region">region</a> in the chain. 1.221 1.222 <p>The CSS regions module follows the fragmentation rules defined in the 1.223 @@ -638,25 +651,25 @@ 1.224 <div class="issue-marker wrapper"> 1.225 <div class=issue-marker data-bug_id=15811 data-bug_status=NEW> <a 1.226 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15811">Issue-15811</a> 1.227 - 1.228 + 1.229 <div class=issue-details> 1.230 - <p class=short-desc>Creating a named flow from external resource</p> 1.231 + <p class=short-desc>Creating a named flow from external resource 1.232 </div> 1.233 </div> 1.234 1.235 <div class=issue-marker data-bug_id=16002 data-bug_status=NEW> <a 1.236 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16002">Issue-16002</a> 1.237 - 1.238 + 1.239 <div class=issue-details> 1.240 - <p class=short-desc>flow-into and anonymous blocks or fix-ups</p> 1.241 + <p class=short-desc>flow-into and anonymous blocks or fix-ups 1.242 </div> 1.243 </div> 1.244 1.245 <div class=issue-marker data-bug_id=16527 data-bug_status=ASSIGNED> <a 1.246 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16527">Issue-16527</a> 1.247 - 1.248 + 1.249 <div class=issue-details> 1.250 - <p class=short-desc>[Shadow]: getFlowByName and shadow DOM</p> 1.251 + <p class=short-desc>[Shadow]: getFlowByName and shadow DOM 1.252 </div> 1.253 </div> 1.254 </div> 1.255 @@ -782,22 +795,22 @@ 1.256 <div class=note><span class=note-prefix>Note </span> 1.257 <p>The ‘<a href="#flow-into"><code 1.258 class=property>flow-into</code></a>’ property moves an element into the 1.259 - flow and the interplay with selectors should be considered carefully.</p> 1.260 - 1.261 - <p>For example,</p> 1.262 + flow and the interplay with selectors should be considered carefully. 1.263 + 1.264 + <p>For example, 1.265 1.266 <pre>table {flow-into: table-content}</pre> 1.267 1.268 <p>will move all tables in the ‘<code 1.269 class=property>table-content</code>’ <a href="#named-flow0">named 1.270 - flow</a>. However, the</p> 1.271 + flow</a>. However, the 1.272 1.273 <pre>table > * {flow-into: table-content} ...</pre> 1.274 1.275 <p>selector will move all immediate children of all table elements into 1.276 the ‘table-content’ <a href="#named-flow0">named flow</a> (which may 1.277 be useful as it will usually result, if the immediate children are rows, 1.278 - in merging rows of multiple tables), but the</p> 1.279 + in merging rows of multiple tables), but the 1.280 1.281 <pre>table * {flow-into: table-content}</pre> 1.282 1.283 @@ -812,7 +825,7 @@ 1.284 2.1‘<code class=css>s anonymous table objects</code></a>). This note 1.285 illustrates how authors must exercise caution when choosing a particular 1.286 selector for setting the ’flow-into' property to avoid unintended 1.287 - results.</p> 1.288 + results. 1.289 </div> 1.290 1.291 <h3 id=the-flow-from-property><span class=secno>3.2. </span>The ‘<a 1.292 @@ -900,10 +913,10 @@ 1.293 1.294 <div class=issue-marker data-bug_id=16819 data-bug_status=ASSIGNED> <a 1.295 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16819">Issue-16819</a> 1.296 - 1.297 + 1.298 <div class=issue-details> 1.299 <p class=short-desc>No display when combining flow-from and flow-into is 1.300 - bad</p> 1.301 + bad 1.302 </div> 1.303 </div> 1.304 1.305 @@ -915,7 +928,7 @@ 1.306 <div class=note><span class=note-prefix>Note </span> 1.307 <p>An block container becomes a <span>CSS Region</span> when its 1.308 ’flow-from' property is set to a valid <ident> value, even if 1.309 - there is no content contributing to the referenced flow. For example:</p> 1.310 + there is no content contributing to the referenced flow. For example: 1.311 1.312 <pre> 1.313 <style> 1.314 @@ -949,34 +962,34 @@ 1.315 <div class="issue-marker wrapper"> 1.316 <div class=issue-marker data-bug_id=15189 data-bug_status=NEW> <a 1.317 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15189">Issue-15189</a> 1.318 - 1.319 + 1.320 <div class=issue-details> 1.321 - <p class=short-desc>Should regions be non-breakable?</p> 1.322 + <p class=short-desc>Should regions be non-breakable? 1.323 </div> 1.324 </div> 1.325 1.326 <div class=issue-marker data-bug_id=15824 data-bug_status=NEW> <a 1.327 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15824</a> 1.328 - 1.329 + 1.330 <div class=issue-details> 1.331 - <p class=short-desc>Should regions not create a new stacking context?</p> 1.332 + <p class=short-desc>Should regions not create a new stacking context? 1.333 </div> 1.334 </div> 1.335 1.336 <div class=issue-marker data-bug_id=15827 data-bug_status=NEW> <a 1.337 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15824">Issue-15827</a> 1.338 - 1.339 + 1.340 <div class=issue-details> 1.341 <p class=short-desc>Specify behavior of stacking contexts that are split 1.342 - between regions</p> 1.343 + between regions 1.344 </div> 1.345 </div> 1.346 1.347 <div class=issue-marker data-bug_id=16636 data-bug_status=NEW> <a 1.348 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16636">Issue-16636</a> 1.349 - 1.350 + 1.351 <div class=issue-details> 1.352 - <p class=short-desc>Should re-introduce region order</p> 1.353 + <p class=short-desc>Should re-introduce region order 1.354 </div> 1.355 </div> 1.356 </div> 1.357 @@ -997,7 +1010,7 @@ 1.358 the fragments are rendered. Since each <span>CSS Region</span> creates a 1.359 new stacking context, it is clear that each fragment is rendered 1.360 separately and their rendering order follows the regular CSS rendering 1.361 - model.</p> 1.362 + model. 1.363 </div> 1.364 1.365 <p>Floats or other exclusions (see <a href="#CSS3-EXCLUSIONS" 1.366 @@ -1185,15 +1198,15 @@ 1.367 the behavior of page breaks with regards to pages, as defined in the <a 1.368 href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>. 1.369 1.370 - <h3 id=the-region-overflow-property><span class=secno>3.4. </span>The 1.371 - region-overflow property</h3> 1.372 + <h3 id=the-region-fragment-property><span class=secno>3.4. </span>The 1.373 + region-fragment property</h3> 1.374 1.375 <table class=propdef summary="break-after property definition"> 1.376 <tbody> 1.377 <tr> 1.378 <td><a href="#dom-named-flow-name"><em>Name:</em></a> 1.379 1.380 - <td><dfn id=region-overflow>region-overflow</dfn> 1.381 + <td><dfn id=region-fragment>region-fragment</dfn> 1.382 1.383 <tr> 1.384 <td><em>Value:</em> 1.385 @@ -1231,27 +1244,8 @@ 1.386 <td>specified value 1.387 </table> 1.388 1.389 - <div class="issue-marker wrapper"> 1.390 - <div class=issue-marker data-bug_id=15832 data-bug_status=ASSIGNED> <a 1.391 - href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15832">Issue-15832</a> 1.392 - 1.393 - <div class=issue-details> 1.394 - <p class=short-desc>Should we have region-overflow:nobreak and have 1.395 - region-overflow apply to all regions, not just the last?</p> 1.396 - </div> 1.397 - </div> 1.398 - 1.399 - <div class=issue-marker data-bug_id=16622 data-bug_status=NEW> <a 1.400 - href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16622">Issue-16622</a> 1.401 - 1.402 - <div class=issue-details> 1.403 - <p class=short-desc>Should we rename region-overflow to flow-overset?</p> 1.404 - </div> 1.405 - </div> 1.406 - </div> 1.407 - 1.408 - <p>The ‘<a href="#region-overflow"><code 1.409 - class=property>region-overflow</code></a>’ property controls the 1.410 + <p>The ‘<a href="#region-fragment"><code 1.411 + class=property>region-fragment</code></a>’ property controls the 1.412 behavior of the <em id=last-region>last region</em> associated with a <a 1.413 href="#named-flow0">named flow</a>. 1.414 1.415 @@ -1272,18 +1266,18 @@ 1.416 Region</em>, the content breaks as if flow was going to continue in a 1.417 subsequent region. See the <a 1.418 href="#regions-flow-breaking-rules">breaking rules</a> section. A forced 1.419 - region break takes precedence over a natural break point.</p> 1.420 - 1.421 - <p>Flow content that follows the last break in the last region, if any is 1.422 - not rendered.</p> 1.423 + region break takes precedence over a natural break point. 1.424 + 1.425 + <p>Flow content that follows the last break in the last region is not 1.426 + rendered. 1.427 </dl> 1.428 1.429 - <p>The ‘<a href="#region-overflow"><code 1.430 - class=property>region-overflow</code></a>’ property does not influence 1.431 + <p>The ‘<a href="#region-fragment"><code 1.432 + class=property>region-fragment</code></a>’ property does not influence 1.433 the size of the region it applies to. 1.434 1.435 <p>The following code sample illustrates the usage of the ‘<a 1.436 - href="#region-overflow"><code class=property>region-overflow</code></a>’ 1.437 + href="#region-fragment"><code class=property>region-fragment</code></a>’ 1.438 property. 1.439 1.440 <div class=example> 1.441 @@ -1295,7 +1289,7 @@ 1.442 1.443 #region_1, #region_2 { 1.444 flow-from: article; 1.445 - <strong>region-overflow: break;</strong> /* or auto */ 1.446 + <strong>region-fragment: break;</strong> /* or auto */ 1.447 <strong>overflow: visible;</strong> /* or hidden */ 1.448 } 1.449 1.450 @@ -1311,7 +1305,7 @@ 1.451 1.452 <div class=figure> 1.453 <table style="border: 1px solid gray;width: 100%;" 1.454 - summary="Different values for the region-overflow property - Illustration."> 1.455 + summary="Different values for the region-fragment property - Illustration."> 1.456 <tbody> 1.457 <tr> 1.458 <td>‘<code class=css>flow-into: "article"</code>’ 1.459 @@ -1319,7 +1313,7 @@ 1.460 <td><code class=html>region_1</code> and <code 1.461 class=html>region_2</code> 1.462 1.463 - <td>‘<code class=css>region-overflow: auto</code>’<br> 1.464 + <td>‘<code class=css>region-fragment: auto</code>’<br> 1.465 ‘<code class=css>overflow:visible</code>’ 1.466 1.467 <tr> 1.468 @@ -1334,9 +1328,9 @@ 1.469 src="images/region-overflow-auto-overflow-visible.png"> 1.470 1.471 <tr> 1.472 - <td>‘<code class=css>region-overflow: break</code>’ 1.473 - 1.474 - <td>‘<code class=css>region-overflow: auto</code>’<br> 1.475 + <td>‘<code class=css>region-fragment: break</code>’ 1.476 + 1.477 + <td>‘<code class=css>region-fragment: auto</code>’<br> 1.478 ‘<code class=css>overflow:hidden</code>’ 1.479 1.480 <tr> 1.481 @@ -1347,7 +1341,7 @@ 1.482 src="images/region-overflow-auto-overflow-hidden.png"> 1.483 </table> 1.484 1.485 - <p class=caption>Different values for the region-overflow property</p> 1.486 + <p class=caption>Different values for the region-fragment property 1.487 </div> 1.488 1.489 <div class=note><span class=note-prefix>Note </span> 1.490 @@ -1356,7 +1350,7 @@ 1.491 the last line, the ‘<code class=property>overflow</code>’ property 1.492 controls the visibility of the overflowing content. See the ‘<code 1.493 class=property>overflow</code>’ property definition (<a href="#CSS21" 1.494 - rel=biblioentry>[CSS21]<!--{{CSS21}}--></a>).</p> 1.495 + rel=biblioentry>[CSS21]<!--{{CSS21}}--></a>). 1.496 </div> 1.497 1.498 <h3 id=the-at-region-style-rule><span class=secno>3.5. </span>The @region 1.499 @@ -1385,9 +1379,9 @@ 1.500 1.501 <div class=issue-marker data-bug_id=15713 data-bug_status=NEW> <a 1.502 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15713">Issue-15713</a> 1.503 - 1.504 + 1.505 <div class=issue-details> 1.506 - <p class=short-desc>Model for styling element fragments</p> 1.507 + <p class=short-desc>Model for styling element fragments 1.508 </div> 1.509 </div> 1.510 1.511 @@ -1401,18 +1395,18 @@ 1.512 <div class="issue-marker wrapper"> 1.513 <div class=issue-marker data-bug_id=15190 data-bug_status=NEW> <a 1.514 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15190">Issue-15190</a> 1.515 - 1.516 + 1.517 <div class=issue-details> 1.518 - <p class=short-desc>List of region style properties</p> 1.519 + <p class=short-desc>List of region style properties 1.520 </div> 1.521 </div> 1.522 1.523 <div class=issue-marker data-bug_id=16921 data-bug_status=REOPENED> <a 1.524 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16921">Issue-16921</a> 1.525 - 1.526 + 1.527 <div class=issue-details> 1.528 <p class=short-desc>Should text-align be added to region styling 1.529 - properties</p> 1.530 + properties 1.531 </div> 1.532 </div> 1.533 </div> 1.534 @@ -1483,7 +1477,7 @@ 1.535 <div class=example id=region-style-example> 1.536 <p>In the following example, the <a href="#named-flow0">named flow</a> 1.537 ‘<code class=css>article_flow</code>’ flows through ‘<code 1.538 - class=css>region_1</code>’ and ‘<code class=css>region_2</code>’.</p> 1.539 + class=css>region_1</code>’ and ‘<code class=css>region_2</code>’. 1.540 1.541 <pre> 1.542 <style> 1.543 @@ -1539,36 +1533,36 @@ 1.544 1.545 <p>The region style ‘<code class=css>RSA</code>’ applies to flow 1.546 content that is laid out in either ‘<code class=css>region_1</code>’ 1.547 - or ‘<code class=css>region_2</code>’.</p> 1.548 + or ‘<code class=css>region_2</code>’. 1.549 1.550 <p>The first rule set ‘<code class=css>div {...}</code>’ applies to 1.551 all <code class=html><div></code> elements that fit partially or 1.552 fully into ‘<code class=css>region_1</code>’ or ‘<code 1.553 class=css>region_2</code>’. <code class=html>div_1</code> is split 1.554 between ‘<code class=css>region_1</code>’ and ‘<code 1.555 - class=css>region_2</code>’ and gets the style from this style rule.</p> 1.556 + class=css>region_2</code>’ and gets the style from this style rule. 1.557 1.558 <p>The second rule set ‘<code class=css>p {...}</code>’ applies to all 1.559 <code class=html><p></code> elements that fit into ‘<code 1.560 class=css>region_1</code>’ or ‘<code class=css>region_2</code>’. In 1.561 our example, both <code class=html>p_1</code> and <code 1.562 - class=html>p_2</code> are selected.</p> 1.563 + class=html>p_2</code> are selected. 1.564 1.565 <p>The region style ‘<code class=css>RSB</code>’ applies to flow 1.566 - content that fits in ‘<code class=css>region_1</code>’.</p> 1.567 + content that fits in ‘<code class=css>region_1</code>’. 1.568 1.569 <p>The first rule set ‘<code class=css>p {...}</code>’ matches <code 1.570 class=html>p_1</code> and <code class=html>p_2</code> because these 1.571 paragraphs flow into ‘<code class=css>region_1</code>’. Only the 1.572 fragment of <code class=html>p_2</code> that flows into <code 1.573 - class=html>region_1</code> is styled with this rule.</p> 1.574 + class=html>region_1</code> is styled with this rule. 1.575 </div> 1.576 1.577 <div class=issue-marker data-bug_id=15734 data-bug_status=NEW> <a 1.578 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15734">Issue-15734</a> 1.579 - 1.580 + 1.581 <div class=issue-details> 1.582 - <p class=short-desc>@region and specificity</p> 1.583 + <p class=short-desc>@region and specificity 1.584 </div> 1.585 </div> 1.586 1.587 @@ -1616,7 +1610,7 @@ 1.588 balance the fragments of content that would flow through its columns. 1.589 1.590 <div class=example> 1.591 - <p>The following example:</p> 1.592 + <p>The following example: 1.593 1.594 <pre> 1.595 <style> 1.596 @@ -1637,7 +1631,7 @@ 1.597 <div id="multicol"></div> 1.598 <div id="remainder"></div></pre> 1.599 1.600 - <p>is equivalent in rendering to, for example:</p> 1.601 + <p>is equivalent in rendering to, for example: 1.602 1.603 <pre> 1.604 <style> 1.605 @@ -1679,10 +1673,10 @@ 1.606 1.607 <div class=issue-marker data-bug_id=15188 data-bug_status=NEW> <a 1.608 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15188">Issue-15188</a> 1.609 - 1.610 + 1.611 <div class=issue-details> 1.612 <p class=short-desc>add functionality for having textual description like 1.613 - "continued here" or "continued on page x" to regions.</p> 1.614 + "continued here" or "continued on page x" to regions. 1.615 </div> 1.616 </div> 1.617 1.618 @@ -1730,17 +1724,17 @@ 1.619 <div class=issue-marker-wrapper> 1.620 <div class=issue-marker data-bug_id=15679 data-bug_status=NEW> <a 1.621 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15679">Issue-15679</a> 1.622 - 1.623 + 1.624 <div class=issue-details> 1.625 - <p class=short-desc>elementFromPoint and CSS regions</p> 1.626 + <p class=short-desc>elementFromPoint and CSS regions 1.627 </div> 1.628 </div> 1.629 1.630 <div class=issue-marker data-bug_id=15933 data-bug_status=ASSIGNED> <a 1.631 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15933">Issue-15933</a> 1.632 - 1.633 + 1.634 <div class=issue-details> 1.635 - <p class=short-desc>Terms in WebIDL snippets inconsistently linked</p> 1.636 + <p class=short-desc>Terms in WebIDL snippets inconsistently linked 1.637 </div> 1.638 </div> 1.639 </div> 1.640 @@ -1974,9 +1968,9 @@ 1.641 1.642 <div class=issue-marker data-bug_id=16382 data-bug_status=ASSIGNED> <a 1.643 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16382">Issue-16382</a> 1.644 - 1.645 + 1.646 <div class=issue-details> 1.647 - <p class=short-desc>Should we have a NamedFlow.getRegionsByFlowRanges?</p> 1.648 + <p class=short-desc>Should we have a NamedFlow.getRegionsByFlowRanges? 1.649 </div> 1.650 </div> 1.651 1.652 @@ -2025,8 +2019,8 @@ 1.653 href="http://www.w3.org/TR/CSS21/visufx.html#overflow"><code 1.654 class=idl>overflow</code></a> property value can be used to control the 1.655 visibility of the overflowing content and the ‘<a 1.656 - href="#region-overflow"><code 1.657 - class=property>region-overflow</code></a>’ property controls whether or 1.658 + href="#region-fragment"><code 1.659 + class=property>region-fragment</code></a>’ property controls whether or 1.660 not fragmentation happens on the content that overflows the last region. 1.661 1.662 <dt>‘<code class=property>fit</code>’ 1.663 @@ -2107,7 +2101,7 @@ 1.664 <span>CSS Region</span> (following how <a 1.665 href="http://dev.w3.org/csswg/cssom/#extensions-to-the-window-interface"><code 1.666 class=idl>getComputedStyle</code></a> works with elements not contained 1.667 - in the window's document).</p> 1.668 + in the window's document). 1.669 </div> 1.670 1.671 <p>A <a href="#css-region"><code class=idl>Region</code></a> instance may 1.672 @@ -2240,9 +2234,9 @@ 1.673 1.674 <div class=issue-marker data-bug_id=16391 data-bug_status=ASSIGNED> <a 1.675 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16391">Issue-16391</a> 1.676 - 1.677 + 1.678 <div class=issue-details> 1.679 - <p class=short-desc>regionLayoutUpdate needs to be async</p> 1.680 + <p class=short-desc>regionLayoutUpdate needs to be async 1.681 </div> 1.682 </div> 1.683 1.684 @@ -2378,7 +2372,7 @@ 1.685 <div class=figure> <img 1.686 alt="The ::before, RFCB and ::after boxes contained in the Region Box" 1.687 src="images/RFCB.svg" width=600px> 1.688 - <p class=caption>The Region Flow Content Box (RFCB)</p> 1.689 + <p class=caption>The Region Flow Content Box (RFCB) 1.690 </div> 1.691 1.692 <p>Laying out a <a href="#css-region">region</a> box follows the same 1.693 @@ -2447,7 +2441,7 @@ 1.694 <div class=figure> <img 1.695 alt="visual representation of the three-step process" 1.696 src="images/regions-layout-three-steps.svg" width=600px> 1.697 - <p class=caption>Regions visual formatting steps</p> 1.698 + <p class=caption>Regions visual formatting steps 1.699 </div> 1.700 1.701 <h4 id=rfcb-flow-fragment-height-resolution><span class=secno>7.2.1. 1.702 @@ -2535,7 +2529,7 @@ 1.703 words, it will not fit tightly. The model prevents having circular 1.704 dependencies in the layout model. Implementations may decide to apply 1.705 further layout steps to ensure that the whole flow content is displayed 1.706 - to the user, even in edge cases.</p> 1.707 + to the user, even in edge cases. 1.708 </div> 1.709 1.710 <h3 id=regions-visual-formatting-implementation-note><span class=secno>7.3. 1.711 @@ -2646,7 +2640,7 @@ 1.712 <div class=figure> <img 1.713 alt="Step 1 - Phase 1: Layout RFBCs with used heights of 0" 1.714 src="images/flow-fragment-height-phase-1.png" width=500px> 1.715 - <p class=caption>Step 1 - Phase 1: Layout RFBCs with used heights of 0</p> 1.716 + <p class=caption>Step 1 - Phase 1: Layout RFBCs with used heights of 0 1.717 </div> 1.718 1.719 <h4 id=step-1--phase-2-layout-flow-to-compute-t><span class=secno>7.4.2. 1.720 @@ -2686,7 +2680,7 @@ 1.721 <div class=figure> <img 1.722 alt="Step 1 - Phase 2: Measure flow fragments heights" 1.723 src="images/flow-fragment-height-phase-2.png" width=370px> 1.724 - <p class=caption>Step 1 - Phase 2: Measure flow fragments heights</p> 1.725 + <p class=caption>Step 1 - Phase 2: Measure flow fragments heights 1.726 </div> 1.727 1.728 <h4 id=step-2-layout-document-and-regions-witho><span class=secno>7.4.3. 1.729 @@ -2720,7 +2714,7 @@ 1.730 alt="Step 2: Layout document and regions without named flows" 1.731 src="images/regions-visual-formatting-step-2.png" width=370px> 1.732 <p class=caption>Step 2: Layout document and regions without <a 1.733 - href="#named-flow0">named flows</a></p> 1.734 + href="#named-flow0">named flows</a> 1.735 </div> 1.736 1.737 <h4 id=step-3-named-flows-layout><span class=secno>7.4.4. </span>Step 3: 1.738 @@ -2752,7 +2746,7 @@ 1.739 alt="Step 3: Final result after laying out named flows in regions" 1.740 src="images/regions-visual-formatting-step-3.png" width=370px> 1.741 <p class=caption>Step 3: Final result after laying out named flows in 1.742 - regions</p> 1.743 + regions 1.744 </div> 1.745 1.746 <h2 id=relation-to-document-events><span class=secno>8. </span>Relation to 1.747 @@ -2816,6 +2810,8 @@ 1.748 <ul> 1.749 <li>Changed NamedFlowCollection getters to return undefined when there is 1.750 no NamedFlow. 1.751 + 1.752 + <li>Changed region-overflow property to region-fragment. 1.753 </ul> 1.754 1.755 <h3 id="changes_from_May_03_2012"><span class=secno>12.2. </span>Changes 1.756 @@ -2879,8 +2875,7 @@ 1.757 behavior. Removed the discussion about how the ‘<code 1.758 class=property>overflow</code>’ property applies to content flown in 1.759 regions from the break section, since this is covered in the section on 1.760 - ‘<a href="#region-overflow"><code 1.761 - class=property>region-overflow</code></a>’ already. See <a 1.762 + ‘<code class=property>region-overflow</code>’ already. See <a 1.763 href="http://lists.w3.org/Archives/Public/www-style/2011Dec/0477.html">mailing 1.764 list feedback.</a> 1.765 1.766 @@ -3020,7 +3015,7 @@ 1.767 1.768 <li>Following a working group <a 1.769 href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a>: 1.770 - 1.771 + 1.772 <ul> 1.773 <li>Turned the first issue in the "Extensions to the Element interface" 1.774 into a note explaining that the NamedFlow interface can be used when 1.775 @@ -3050,8 +3045,7 @@ 1.776 get reserved</a>. 1.777 1.778 <li>Added to the definition of ‘<code class=property>auto</code>’ on 1.779 - ‘<a href="#region-overflow"><code 1.780 - class=property>region-overflow</code></a>’ specifying that region 1.781 + ‘<code class=property>region-overflow</code>’ specifying that region 1.782 breaks must be ignored. 1.783 1.784 <li>Renamed ‘<code class=css>Document.flowWithName</code>’ to ‘<code 1.785 @@ -3353,16 +3347,16 @@ 1.786 <div class=note><span class=note-prefix>Note </span> 1.787 <p> Note that a multi-column element is used for #region2, which is a bit 1.788 gratuitous here (because grid cells could be used). The reason to use a 1.789 - multi-column element is to illustrate that regions can be multi-column.</p> 1.790 + multi-column element is to illustrate that regions can be multi-column. 1.791 </div> 1.792 1.793 <h2 class=no-num id=references>References</h2> 1.794 1.795 <div class=issue-marker data-bug_id=16404 data-bug_status=ASSIGNED> <a 1.796 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16404">Issue-16404</a> 1.797 - 1.798 + 1.799 <div class=issue-details> 1.800 - <p class=short-desc>Fix specification dependencies</p> 1.801 + <p class=short-desc>Fix specification dependencies 1.802 </div> 1.803 </div> 1.804 1.805 @@ -3381,7 +3375,7 @@ 1.806 Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 June 1.807 2011. W3C Recommendation. URL: <a 1.808 href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a> 1.809 - </dd> 1.810 + </dd> 1.811 <!----> 1.812 1.813 <dt id=CSS3-BREAK>[CSS3-BREAK] 1.814 @@ -3391,7 +3385,7 @@ 1.815 Fragmentation Module Level 3.</cite></a> 23 August 2012. W3C Working 1.816 Draft. (Work in progress.) URL: <a 1.817 href="http://www.w3.org/TR/2012/WD-css3-break-20120823/">http://www.w3.org/TR/2012/WD-css3-break-20120823/</a> 1.818 - </dd> 1.819 + </dd> 1.820 <!----> 1.821 1.822 <dt id=CSS3-WRITING-MODES>[CSS3-WRITING-MODES] 1.823 @@ -3401,7 +3395,7 @@ 1.824 Writing Modes Module Level 3.</cite></a> 1 May 2012. W3C Working Draft. 1.825 (Work in progress.) URL: <a 1.826 href="http://www.w3.org/TR/2012/WD-css3-writing-modes-20120501/">http://www.w3.org/TR/2012/WD-css3-writing-modes-20120501/</a> 1.827 - </dd> 1.828 + </dd> 1.829 <!----> 1.830 1.831 <dt id=CSS3COL>[CSS3COL] 1.832 @@ -3411,7 +3405,7 @@ 1.833 Multi-column Layout Module.</cite></a> 12 April 2011. W3C Candidate 1.834 Recommendation. (Work in progress.) URL: <a 1.835 href="http://www.w3.org/TR/2011/CR-css3-multicol-20110412">http://www.w3.org/TR/2011/CR-css3-multicol-20110412</a> 1.836 - </dd> 1.837 + </dd> 1.838 <!----> 1.839 1.840 <dt id=CSSOM>[CSSOM] 1.841 @@ -3420,7 +3414,7 @@ 1.842 href="http://www.w3.org/TR/2011/WD-cssom-20110712/"><cite>CSSOM.</cite></a> 1.843 12 July 2011. W3C Working Draft. (Work in progress.) URL: <a 1.844 href="http://www.w3.org/TR/2011/WD-cssom-20110712/">http://www.w3.org/TR/2011/WD-cssom-20110712/</a> 1.845 - </dd> 1.846 + </dd> 1.847 <!----> 1.848 1.849 <dt id=DOM>[DOM] 1.850 @@ -3429,17 +3423,17 @@ 1.851 href="http://www.w3.org/TR/2012/WD-dom-20120405/"><cite>DOM4.</cite></a> 1.852 5 April 2012. W3C Working Draft. (Work in progress.) URL: <a 1.853 href="http://www.w3.org/TR/2012/WD-dom-20120405/">http://www.w3.org/TR/2012/WD-dom-20120405/</a> 1.854 - </dd> 1.855 + </dd> 1.856 <!----> 1.857 1.858 <dt id=DOM-LEVEL-3-EVENTS>[DOM-LEVEL-3-EVENTS] 1.859 1.860 <dd>Travis Leithead; et al. <a 1.861 - href="http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120614/"><cite>Document 1.862 - Object Model (DOM) Level 3 Events Specification.</cite></a> 14 June 2012. 1.863 - W3C Working Draft. (Work in progress.) URL: <a 1.864 - href="http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120614/">http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120614/</a> 1.865 - </dd> 1.866 + href="http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120906/"><cite>Document 1.867 + Object Model (DOM) Level 3 Events Specification.</cite></a> 6 September 1.868 + 2012. W3C Working Draft. (Work in progress.) URL: <a 1.869 + href="http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120906/">http://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120906/</a> 1.870 + </dd> 1.871 <!----> 1.872 1.873 <dt id=HTML5>[HTML5] 1.874 @@ -3448,7 +3442,7 @@ 1.875 href="http://www.w3.org/TR/2011/WD-html5-20110525/"><cite>HTML5.</cite></a> 1.876 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a 1.877 href="http://www.w3.org/TR/2011/WD-html5-20110525/">http://www.w3.org/TR/2011/WD-html5-20110525/</a> 1.878 - </dd> 1.879 + </dd> 1.880 <!----> 1.881 1.882 <dt id=SELECT>[SELECT] 1.883 @@ -3457,7 +3451,7 @@ 1.884 href="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/"><cite>Selectors 1.885 Level 3.</cite></a> 29 September 2011. W3C Recommendation. URL: <a 1.886 href="http://www.w3.org/TR/2011/REC-css3-selectors-20110929/">http://www.w3.org/TR/2011/REC-css3-selectors-20110929/</a> 1.887 - </dd> 1.888 + </dd> 1.889 <!----> 1.890 </dl> 1.891 <!--end-normative--> 1.892 @@ -3477,7 +3471,7 @@ 1.893 Exclusions and Shapes Module Level 3.</cite></a> 3 May 2012. W3C Working 1.894 Draft. (Work in progress.) URL: <a 1.895 href="http://www.w3.org/TR/2012/WD-css3-exclusions-20120503/">http://www.w3.org/TR/2012/WD-css3-exclusions-20120503/</a> 1.896 - </dd> 1.897 + </dd> 1.898 <!----> 1.899 1.900 <dt id=CSS3-FLEXBOX>[CSS3-FLEXBOX] 1.901 @@ -3487,7 +3481,7 @@ 1.902 Flexible Box Layout Module.</cite></a> 12 June 2012. W3C Working Draft. 1.903 (Work in progress.) URL: <a 1.904 href="http://www.w3.org/TR/2012/WD-css3-flexbox-20120612/">http://www.w3.org/TR/2012/WD-css3-flexbox-20120612/</a> 1.905 - </dd> 1.906 + </dd> 1.907 <!----> 1.908 1.909 <dt id=CSS3-GRID-LAYOUT>[CSS3-GRID-LAYOUT] 1.910 @@ -3497,7 +3491,7 @@ 1.911 Grid Layout.</cite></a> 22 March 2012. W3C Working Draft. (Work in 1.912 progress.) URL: <a 1.913 href="http://www.w3.org/TR/2012/WD-css3-grid-layout-20120322/">http://www.w3.org/TR/2012/WD-css3-grid-layout-20120322/</a> 1.914 - </dd> 1.915 + </dd> 1.916 <!----> 1.917 1.918 <dt id=CSS3-LINE-GRID>[CSS3-LINE-GRID] 1.919 @@ -3506,7 +3500,7 @@ 1.920 Line Grid Module.</cite></a> Proposal for a CSS module. (Retrieved 26 1.921 October 2011) URL: <a 1.922 href="http://dev.w3.org/csswg/css-line-grid/">http://dev.w3.org/csswg/css-line-grid/</a> 1.923 - </dd> 1.924 + </dd> 1.925 <!----> 1.926 1.927 <dt id=CSS3-PAGE-TEMPLATE>[CSS3-PAGE-TEMPLATE] 1.928 @@ -3516,7 +3510,7 @@ 1.929 Templates Module Level 3.</cite></a> Proposal for a CSS module. 1.930 (Retrieved 4 April 2012) URL: <a 1.931 href="http://dev.w3.org/csswg/css3-page-template/">http://dev.w3.org/csswg/css3-page-template/</a> 1.932 - </dd> 1.933 + </dd> 1.934 <!----> 1.935 1.936 <dt id=CSS3GRID>[CSS3GRID] 1.937 @@ -3526,7 +3520,7 @@ 1.938 Positioning Module Level 3.</cite></a> 5 September 2007. W3C Working 1.939 Draft. (Work in progress.) URL: <a 1.940 href="http://www.w3.org/TR/2007/WD-css3-grid-20070905">http://www.w3.org/TR/2007/WD-css3-grid-20070905</a> 1.941 - </dd> 1.942 + </dd> 1.943 <!----> 1.944 1.945 <dt id=CSS3LAYOUT>[CSS3LAYOUT] 1.946 @@ -3536,7 +3530,7 @@ 1.947 Template Layout Module.</cite></a> 29 April 2010. W3C Working Draft. 1.948 (Work in progress.) URL: <a 1.949 href="http://www.w3.org/TR/2010/WD-css3-layout-20100429">http://www.w3.org/TR/2010/WD-css3-layout-20100429</a> 1.950 - </dd> 1.951 + </dd> 1.952 <!----> 1.953 1.954 <dt id=CSS3PAGE>[CSS3PAGE] 1.955 @@ -3546,7 +3540,7 @@ 1.956 Paged Media.</cite></a> 10 October 2006. W3C Working Draft. (Work in 1.957 progress.) URL: <a 1.958 href="http://www.w3.org/TR/2006/WD-css3-page-20061010">http://www.w3.org/TR/2006/WD-css3-page-20061010</a> 1.959 - </dd> 1.960 + </dd> 1.961 <!----> 1.962 1.963 <dt id=MEDIAQ>[MEDIAQ] 1.964 @@ -3555,7 +3549,7 @@ 1.965 href="http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/"><cite>Media 1.966 Queries.</cite></a> 19 June 2012. W3C Recommendation. URL: <a 1.967 href="http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/">http://www.w3.org/TR/2012/REC-css3-mediaqueries-20120619/</a> 1.968 - </dd> 1.969 + </dd> 1.970 <!----> 1.971 </dl> 1.972 <!--end-informative--> 1.973 @@ -3654,7 +3648,6 @@ 1.974 1.975 <li><a href="#dom-named-flow-overset"><code class=idl>overset</code></a>, 1.976 <a href="#dom-named-flow-overset" title=overset><strong>6.1.</strong></a> 1.977 - 1.978 1.979 <li>region, <a href="#css-region" title=region><strong>2.1.</strong></a> 1.980 1.981 @@ -3664,13 +3657,13 @@ 1.982 <li>region flow content box, <a href="#region-flow-content-box" 1.983 title="region flow content box"><strong>7.1.</strong></a> 1.984 1.985 + <li>region-fragment, <a href="#region-fragment" 1.986 + title=region-fragment><strong>3.4.</strong></a> 1.987 + 1.988 <li><a href="#css-region"><code class=idl>Region</code></a> interface, <a 1.989 href="#region-interface" 1.990 title="Region interface"><strong>6.2.</strong></a> 1.991 1.992 - <li>region-overflow, <a href="#region-overflow" 1.993 - title=region-overflow><strong>3.4.</strong></a> 1.994 - 1.995 <li><a href="#dom-region-regionoverset"><code 1.996 class=idl>regionOverset</code></a>, <a href="#dom-region-regionoverset" 1.997 title=regionOverset><strong>6.2.</strong></a> 1.998 @@ -3793,7 +3786,7 @@ 1.999 <td>visual 1.1000 1.1001 <tr> 1.1002 - <th><a class=property href="#region-overflow">region-overflow</a> 1.1003 + <th><a class=property href="#region-fragment">region-fragment</a> 1.1004 1.1005 <td>auto | break 1.1006 1.1007 @@ -3810,24 +3803,23 @@ 1.1008 <!--end-properties--> 1.1009 <!-- template markup for issues pulled from Bugzilla --> 1.1010 <!-- template markup for issues pulled from Bugzilla --> 1.1011 + 1.1012 <script id=issue-template type="text/template"> 1.1013 </script> 1.1014 - 1.1015 <div class=issue-marker data-bug_id="{{bug_id}}" 1.1016 data-bug_status="{{bug_status}}"> <a 1.1017 href="https://www.w3.org/Bugs/Public/show_bug.cgi?id={{bug_id}}">Issue-{{bug_id}}</a> 1.1018 - 1.1019 + 1.1020 <div class=issue-details> 1.1021 - <p class=short-desc>{{short_desc}}</p> 1.1022 + <p class=short-desc>{{short_desc}} 1.1023 </div> 1.1024 </div> 1.1025 + 1.1026 <script src="../shared/scripts/BugzillaTrackerUtil.js" 1.1027 - type="text/javascript"></script> 1.1028 - <script src="../shared/scripts/BugzillaTracker.js" 1.1029 - type="text/javascript"></script> 1.1030 + type="text/javascript"></script> 1.1031 + <script src="../shared/scripts/BugzillaTracker.js" type="text/javascript"></script> 1.1032 <script type="text/javascript"> 1.1033 checkSpecificationIssues(‘</script> 1.1034 - 1.1035 <p><code class=property>CSS</code>’, ‘<a href="#css-region"><code 1.1036 class=property>Regions</code></a>’); 1.1037 </html>
2.1 --- a/css3-regions/Overview.src.html Thu Sep 27 14:53:18 2012 +0200 2.2 +++ b/css3-regions/Overview.src.html Thu Sep 27 15:20:14 2012 -0700 2.3 @@ -411,7 +411,7 @@ 2.4 in the region chain 2.5 and there is still content in the flow, 2.6 the positioning of the remaining content 2.7 - is controlled by the 'region-overflow' property 2.8 + is controlled by the 'region-fragment' property 2.9 on the last <span>region</span> in the chain.</p> 2.10 2.11 <p>The CSS regions module follows 2.12 @@ -1033,13 +1033,13 @@ 2.13 <p>The behavior of region breaks with regards to regions is identical to the behavior 2.14 of page breaks with regards to pages, as defined in the [[!CSS21]].</p> 2.15 2.16 - <h3 id="the-region-overflow-property">The region-overflow property</h3> 2.17 + <h3 id="the-region-fragment-property">The region-fragment property</h3> 2.18 2.19 <table class="propdef" summary="break-after property definition"> 2.20 <tr> 2.21 <td><em>Name:</em></td> 2.22 2.23 - <td><dfn>region-overflow</dfn></td> 2.24 + <td><dfn>region-fragment</dfn></td> 2.25 </tr> 2.26 2.27 <tr> 2.28 @@ -1085,22 +1085,7 @@ 2.29 </tr> 2.30 </table> 2.31 2.32 - <div class="issue-marker wrapper"> 2.33 - <div class="issue-marker" data-bug_id="15832" data-bug_status="ASSIGNED"> 2.34 - <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15832">Issue-15832</a> 2.35 - <div class="issue-details"> 2.36 - <p class="short-desc">Should we have region-overflow:nobreak and have region-overflow apply to all regions, not just the last?</p> 2.37 - </div> 2.38 - </div> 2.39 - <div class="issue-marker" data-bug_id="16622" data-bug_status="NEW"> 2.40 - <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=16622">Issue-16622</a> 2.41 - <div class="issue-details"> 2.42 - <p class="short-desc">Should we rename region-overflow to flow-overset?</p> 2.43 - </div> 2.44 - </div> 2.45 - </div> 2.46 - 2.47 - <p>The 'region-overflow' property controls the behavior of the <em id= 2.48 + <p>The 'region-fragment' property controls the behavior of the <em id= 2.49 "last-region">last region</em> associated with a <span>named 2.50 flow</span>.</p> 2.51 2.52 @@ -1122,17 +1107,17 @@ 2.53 "#regions-flow-breaking-rules">breaking rules</a> section. A forced region break takes precedence over 2.54 a natural break point.</p> 2.55 2.56 - <p>Flow content that follows the last break in the last region, if any is not rendered.</p> 2.57 + <p>Flow content that follows the last break in the last region is not rendered.</p> 2.58 2.59 2.60 </dd> 2.61 </dl> 2.62 2.63 - <p>The 'region-overflow' property does not influence 2.64 + <p>The 'region-fragment' property does not influence 2.65 the size of the region it applies to.</p> 2.66 2.67 <p>The following code sample illustrates 2.68 - the usage of the 'region-overflow' property.</p> 2.69 + the usage of the 'region-fragment' property.</p> 2.70 2.71 <div class="example"> 2.72 <pre> 2.73 @@ -1143,7 +1128,7 @@ 2.74 2.75 #region_1, #region_2 { 2.76 flow-from: article; 2.77 - <strong>region-overflow: break;</strong> /* or auto */ 2.78 + <strong>region-fragment: break;</strong> /* or auto */ 2.79 <strong>overflow: visible;</strong> /* or hidden */ 2.80 } 2.81 2.82 @@ -1159,14 +1144,14 @@ 2.83 2.84 <div class="figure"> 2.85 <table style="border: 1px solid gray;width: 100%;" summary= 2.86 - "Different values for the region-overflow property - Illustration."> 2.87 + "Different values for the region-fragment property - Illustration."> 2.88 <tr> 2.89 <td>''flow-into: "article"''</td> 2.90 2.91 <td><code class="html">region_1</code> and <code class= 2.92 "html">region_2</code></td> 2.93 2.94 - <td>''region-overflow: auto''<br> 2.95 + <td>''region-fragment: auto''<br> 2.96 ''overflow:visible''</td> 2.97 </tr> 2.98 2.99 @@ -1183,9 +1168,9 @@ 2.100 </tr> 2.101 2.102 <tr> 2.103 - <td>''region-overflow: break''</td> 2.104 + <td>''region-fragment: break''</td> 2.105 2.106 - <td>''region-overflow: auto''<br> 2.107 + <td>''region-fragment: auto''<br> 2.108 ''overflow:hidden''</td> 2.109 </tr> 2.110 2.111 @@ -1198,7 +1183,7 @@ 2.112 </tr> 2.113 </table> 2.114 2.115 - <p class="caption">Different values for the region-overflow 2.116 + <p class="caption">Different values for the region-fragment 2.117 property</p> 2.118 </div> 2.119 2.120 @@ -1807,7 +1792,7 @@ 2.121 "http://www.w3.org/TR/CSS21/visufx.html#overflow"><code class= 2.122 "idl">overflow</code></a> property value can be used to control the 2.123 visibility of the overflowing content and the 2.124 - 'region-overflow' property controls whether or not fragmentation happens 2.125 + 'region-fragment' property controls whether or not fragmentation happens 2.126 on the content that overflows the last region.</dd> 2.127 2.128 <dt>'fit'</dt> 2.129 @@ -2451,6 +2436,7 @@ 2.130 2.131 <ul> 2.132 <li>Changed NamedFlowCollection getters to return undefined when there is no NamedFlow.</li> 2.133 + <li>Changed region-overflow property to region-fragment.</li> 2.134 </ul> 2.135 2.136 <h3 id="changes_from_May_03_2012">Changes from <a href="http://www.w3.org/TR/2012/WD-css3-regions-20120503/">May 3<sup>rd</sup> 2012</a> version</h3>
