changeset
[css-regions] move generated content issue to page-templates
Fri, 19 Oct 2012 13:17:29 -0700
- author
- Alan Stearns <stearns@adobe.com>
- date
- Fri, 19 Oct 2012 13:17:29 -0700
- changeset 6906
- d1915207dba4
- parent 6905
- f5bfb5b4217d
- child 6907
- d627bb2e0f56
[css-regions] move generated content issue to page-templates
1.1 --- a/css3-page-template/Overview.html Fri Oct 19 12:55:58 2012 -0700 1.2 +++ b/css3-page-template/Overview.html Fri Oct 19 13:17:29 2012 -0700 1.3 @@ -1,15 +1,26 @@ 1.4 <!DOCTYPE html> 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 + <head profile="http://www.w3.org/2006/03/hcard"> 1.10 + <meta content="text/html; charset=UTF-8" http-equiv=Content-Type> 1.11 + <title>CSS Pagination Templates Module Level 3</title> 1.12 + <!-- 1.13 + <link href="http://purl.org/dc/terms/" rel="schema.dcterms"> 1.14 + <link href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" rel="dcterms.rights"> 1.15 + --> 1.16 1.17 - <title>CSS Pagination Templates Module Level 3</title> 1.18 - <link href="../shared/style/default.css" rel=stylesheet type="text/css"> 1.19 - <!--link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"--> 1.20 + <meta content="CSS Pagination Templates Module Level 3" name=dcterms.title> 1.21 + <meta content=text name=dcterms.type> 1.22 + <meta content=2012-10-19 name=dcterms.issued> 1.23 + <meta content="http://dev.w3.org/csswg/css3-page-template/ <!--" 1.24 + name=dcterms.creator> 1.25 + <meta content=W3C name=dcterms.publisher> 1.26 + <meta content="http://www.w3.org/TR/2012/ED-css3-page-template-20121019/" 1.27 + name=dcterms.identifier> 1.28 + <link href="../shared/style/default.css" rel=stylesheet type="text/css"><!--link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED.css"--> 1.29 + 1.30 <link href="http://www.w3.org/StyleSheets/TR/w3c-unofficial.css" 1.31 - rel=stylesheet type="text/css"> 1.32 - 1.33 + rel=stylesheet type="text/css"> 1.34 <style type="text/css"> 1.35 body { 1.36 counter-reset: issue; 1.37 @@ -17,7 +28,7 @@ 1.38 </style> 1.39 <link href="../shared/style/issues.css" rel=stylesheet type="text/css"> 1.40 <link href="../shared/style/alternate-spec-style.css" id=st rel=stylesheet 1.41 - title="alternate spec style" type="text/css"> 1.42 + title="alternate spec style" type="text/css"> 1.43 1.44 <body> 1.45 <div class=head> <!--begin-logo--> 1.46 @@ -26,24 +37,21 @@ 1.47 1.48 <h1>CSS Pagination Templates Module Level 3</h1> 1.49 1.50 - <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 8 May 2012</h2> 1.51 + <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 19 October 1.52 + 2012</h2> 1.53 1.54 <dl> 1.55 <dt>This version: 1.56 - <!--<dd><a href="http://www.w3.org/TR/2012/ED-css3-page-template-20120508/">http://www.w3.org/TR/2012/ED-css3-page-template-20120508/</a>--> 1.57 - 1.58 + <!--<dd><a href="http://www.w3.org/TR/2012/ED-css3-page-template-20121019/">http://www.w3.org/TR/2012/ED-css3-page-template-20121019/</a>--> 1.59 1.60 <dd><a 1.61 href="//dev.w3.org/csswg/css3-page-template/">http://dev.w3.org/csswg/css3-page-template/</a> 1.62 - 1.63 1.64 <dt>Latest version: 1.65 <!--<dd><a href="http://www.w3.org/TR/css3-page-template/">http://www.w3.org/TR/css3-page-template/</a>--> 1.66 - 1.67 1.68 <dd><a 1.69 href="//www.w3.org/TR/css3-page-template/">http://www.w3.org/TR/css3-page-template/</a> 1.70 - 1.71 1.72 <dt>Editor's draft: 1.73 1.74 @@ -54,7 +62,6 @@ 1.75 <dd><a href="http://www.w3.org/PreviousVersionURI"> 1.76 http://www.w3.org/PreviousVersionURI</a> 1.77 --> 1.78 - 1.79 1.80 <dt>Editors: 1.81 1.82 @@ -64,8 +71,8 @@ 1.83 <!--begin-copyright--> 1.84 <p class=copyright><a 1.85 href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" 1.86 - rel=license>Copyright</a> © 2012 <a href="http://www.w3.org/"><abbr 1.87 - title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a 1.88 + rel=license>Copyright</a> © 2012 <a href="http://www.w3.org/"><abbr 1.89 + title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a 1.90 href="http://www.csail.mit.edu/"><abbr 1.91 title="Massachusetts Institute of Technology">MIT</abbr></a>, <a 1.92 href="http://www.ercim.eu/"><abbr 1.93 @@ -104,9 +111,8 @@ 1.94 www-style@w3.org</a> (see <a 1.95 href="http://www.w3.org/Mail/Request">instructions</a>) is preferred for 1.96 discussion of this specification. When sending e-mail, please put the text 1.97 - “css3-page-template” in the subject, preferably like this: 1.98 - “[<!---->css3-page-template<!---->] <em>…summary of 1.99 - comment…</em>” 1.100 + “css3-page-template” in the subject, preferably like this: 1.101 + “[<!---->css3-page-template<!---->] <em>…summary of comment…</em>” 1.102 1.103 <p>This document was produced by the <a href="/Style/CSS/members">CSS 1.104 Working Group</a> (part of the <a href="/Style/">Style Activity</a>). 1.105 @@ -176,13 +182,12 @@ 1.106 1.107 <p>This module describes how to define pagination templates in CSS. In CSS 1.108 2.1 content displayed on-screen is assumed to be a single continuous 1.109 - canvas. Pagination templates provide a mechanism for a ‘<code 1.110 - class=property>paginated</code>’ experience that applies to 1.111 - on-screen presentation as well as printed media. Pagination templates 1.112 - define boxes in CSS where content is displayed as the user moves from page 1.113 - to page on screen or prints the document. When content is laid out using 1.114 - pagination templates, pages are generated as needed to accommodate all the 1.115 - content. 1.116 + canvas. Pagination templates provide a mechanism for a ‘<code 1.117 + class=property>paginated</code>’ experience that applies to on-screen 1.118 + presentation as well as printed media. Pagination templates define boxes 1.119 + in CSS where content is displayed as the user moves from page to page on 1.120 + screen or prints the document. When content is laid out using pagination 1.121 + templates, pages are generated as needed to accommodate all the content. 1.122 1.123 <div class="issue-marker wrapper"> 1.124 <div class=issue-marker> 1.125 @@ -194,14 +199,21 @@ 1.126 </div> 1.127 1.128 <div class=issue-marker> 1.129 - <div class=issue-details>The terms ‘<code 1.130 - class=property>template</code>’ and ‘<code 1.131 - class=property>page</code>’ are overloaded in CSS, but they are 1.132 - the words that most clearly describe the concept. Some alternates for 1.133 - the main @ rule: template, page-template, view-template, page-master, 1.134 + <div class=issue-details>The terms ‘<code 1.135 + class=property>template</code>’ and ‘<code 1.136 + class=property>page</code>’ are overloaded in CSS, but they are the 1.137 + words that most clearly describe the concept. Some alternates for the 1.138 + main @ rule: template, page-template, view-template, page-master, 1.139 master-template, master. Other suggestions are welcome, but only if they 1.140 are more helpful than onelook.com (which suggested "Captain Submarine").</div> 1.141 </div> 1.142 + 1.143 + <div class=issue-marker> 1.144 + <div class=issue-details>This specification may be the best place to 1.145 + define "continued here" or "continued on page x" generated content, 1.146 + since this spec defines ways to skip pages (that basic pagination may 1.147 + not).</div> 1.148 + </div> 1.149 </div> 1.150 1.151 <p>Pagination templates consist of anonymous boxes called slots created by 1.152 @@ -236,8 +248,8 @@ 1.153 <p>An @template rule defines and names a pagination template. Pagination 1.154 templates contain one or more slots to display content. These slots create 1.155 boxes for each page generated from a pagination template. An element can 1.156 - use pagination templates if its ‘<code 1.157 - class=property>overflow-style</code>’ property is set to any of the 1.158 + use pagination templates if its ‘<code 1.159 + class=property>overflow-style</code>’ property is set to any of the 1.160 paged-* values defined in css3-gcpm. If a document defines no pagination 1.161 templates, then there is an implicit pagination template with a single 1.162 slot containing the paginated element's contents. 1.163 @@ -245,9 +257,8 @@ 1.164 <div class=issue-marker> 1.165 <div class=issue-details>Instead of a dependency on GCPM, this spec could 1.166 define what happens with a paginated view, without specifying how the 1.167 - paginated view comes into existence. What happens when you apply 1.168 - ‘<code class=css>overflow-style:paged-x</code>’ to an iframe 1.169 - or region?</div> 1.170 + paginated view comes into existence. What happens when you apply ‘<code 1.171 + class=css>overflow-style:paged-x</code>’ to an iframe or region?</div> 1.172 </div> 1.173 1.174 <p>The box created from an @template rule defaults to the size of the 1.175 @@ -285,10 +296,10 @@ 1.176 instantiated. 1.177 1.178 <div class=issue-marker> 1.179 - <div class=issue-details>If there is more than one slot with no 1.180 - ‘<code class=property>content</code>’ or ‘<code 1.181 - class=property>flow-from</code>’ assignment, does the element's 1.182 - content use all of these slots like a region chain, or is only the last 1.183 + <div class=issue-details>If there is more than one slot with no ‘<code 1.184 + class=property>content</code>’ or ‘<code 1.185 + class=property>flow-from</code>’ assignment, does the element's content 1.186 + use all of these slots like a region chain, or is only the last 1.187 unassigned slot used for content?</div> 1.188 </div> 1.189 1.190 @@ -432,13 +443,13 @@ 1.191 1.192 <p>Multiple templates can be defined for a single document. An element that 1.193 uses pagination templates either selects a template from the entire 1.194 - document set or a subset defined by the ‘<code 1.195 - class=property>template-set</code>’ property. Each page view created 1.196 + document set or a subset defined by the ‘<code 1.197 + class=property>template-set</code>’ property. Each page view created 1.198 uses a single template. This template can be chosen from the applicable 1.199 - set using a selector, by matching content to display using the 1.200 - ‘<code class=property>required-flow</code>’ or ‘<code 1.201 - class=property>available-content</code>’ declarations, or just 1.202 - taking the last template found. 1.203 + set using a selector, by matching content to display using the ‘<code 1.204 + class=property>required-flow</code>’ or ‘<code 1.205 + class=property>available-content</code>’ declarations, or just taking 1.206 + the last template found. 1.207 1.208 <div class=issue-marker> 1.209 <div class=issue-details>The following section describes selecting 1.210 @@ -528,24 +539,22 @@ 1.211 <h3 id=selection-from-required-flows><span class=secno>3.2. 1.212 </span>Selecting Templates from Required Flows</h3> 1.213 1.214 - <p>The ‘<code class=property>required-flow</code>’ property can 1.215 - be used in a pagination template to list named flows that must still have 1.216 - content in order for the template to be used. If more than one template 1.217 - has a ‘<code class=property>required-flow</code>’ value that 1.218 - matches the remaining flow content, the last template that matches will be 1.219 - used. 1.220 + <p>The ‘<code class=property>required-flow</code>’ property can be used 1.221 + in a pagination template to list named flows that must still have content 1.222 + in order for the template to be used. If more than one template has a 1.223 + ‘<code class=property>required-flow</code>’ value that matches the 1.224 + remaining flow content, the last template that matches will be used. 1.225 1.226 <div class=example> 1.227 <p>"Continued on" layout. 1.228 1.229 <p>These pagination templates will display an initial page with the 1.230 - beginning of both the ‘<code 1.231 - class=property>lead-story</code>’ flow and a ‘<code 1.232 - class=property>related-article</code>’ flow. If the lead story has 1.233 - more content than will fit on that first page, the next page(s) will show 1.234 - only content from that lead story. When the content from the lead story 1.235 - is exhausted, then pages will follow with content from the related 1.236 - article. 1.237 + beginning of both the ‘<code class=property>lead-story</code>’ flow 1.238 + and a ‘<code class=property>related-article</code>’ flow. If the lead 1.239 + story has more content than will fit on that first page, the next page(s) 1.240 + will show only content from that lead story. When the content from the 1.241 + lead story is exhausted, then pages will follow with content from the 1.242 + related article. 1.243 1.244 <p> <img alt="side-by-side flows on a page" 1.245 src="images/side-by-side-1.png" width=120> <img 1.246 @@ -606,53 +615,49 @@ 1.247 the original order can be discovered in the DOM and used for template 1.248 selection. 1.249 1.250 - <p>Pagination templates have a ‘<code 1.251 - class=property>primary</code>’ content flow. The primary flow for a 1.252 - pagination template is usually the content of the paginated element. If no 1.253 - slot in the template displays the element contents, then the primary flow 1.254 - of the pagination template is the first named flow in its required-flow 1.255 - declaration. 1.256 + <p>Pagination templates have a ‘<code class=property>primary</code>’ 1.257 + content flow. The primary flow for a pagination template is usually the 1.258 + content of the paginated element. If no slot in the template displays the 1.259 + element contents, then the primary flow of the pagination template is the 1.260 + first named flow in its required-flow declaration. 1.261 1.262 <p>When selecting the pagination template for the next page, the primary 1.263 flow in the original markup can be scanned to determine whether any 1.264 out-of-flow content in other named flows was originally related to the 1.265 next page of primary flow. If this is the case, then those named flows 1.266 - have ‘<code class=property>available</code>’ content for the 1.267 - purpose of selecting an appropriate template that can display this 1.268 - content. 1.269 + have ‘<code class=property>available</code>’ content for the purpose 1.270 + of selecting an appropriate template that can display this content. 1.271 1.272 - <p>Pagination templates can have an ‘<code 1.273 - class=property>available-content</code>’ declaration listing the 1.274 - named flows that must have available content for the template to be 1.275 - selected. Templates with more ‘<code 1.276 - class=property>available-content</code>’ flow matches take 1.277 - precedence over fewer or no ‘<code 1.278 - class=property>available-content</code>’ flow matches. If a template 1.279 - with an ‘<code class=property>available-content</code>’ 1.280 - declaration is chosen, only the available content in those flows is 1.281 - displayed in the slots associated with those flows. 1.282 + <p>Pagination templates can have an ‘<code 1.283 + class=property>available-content</code>’ declaration listing the named 1.284 + flows that must have available content for the template to be selected. 1.285 + Templates with more ‘<code class=property>available-content</code>’ 1.286 + flow matches take precedence over fewer or no ‘<code 1.287 + class=property>available-content</code>’ flow matches. If a template 1.288 + with an ‘<code class=property>available-content</code>’ declaration is 1.289 + chosen, only the available content in those flows is displayed in the 1.290 + slots associated with those flows. 1.291 1.292 <div class=example> 1.293 <p>Clarification example (not meant to be a valid use case) 1.294 1.295 <p>Consider an article element that contains images scattered throughout. 1.296 - Assign the images to a flow named ‘<code 1.297 - class=property>images</code>’ and the rest of the article to a flow 1.298 - named ‘<code class=property>text</code>’. Then define two 1.299 - pagination templates - one that has slots only for the ‘<code 1.300 - class=property>text</code>’ flow, and another that has slots for 1.301 - both the ‘<code class=property>text</code>’ and ‘<code 1.302 - class=property>images</code>’ flows. Both templates require the 1.303 - ‘<code class=property>text</code>’ flow, but the second 1.304 - template also requires the ‘<code 1.305 - class=property>images</code>’ flow and has an ‘<code 1.306 - class=property>available-content</code>’ declaration listing the 1.307 - ‘<code class=property>images</code>’ flow. Each time a page 1.308 - is laid out, the original article element is scanned to see whether an 1.309 - image element is in the next page's worth of content (determined by some 1.310 + Assign the images to a flow named ‘<code 1.311 + class=property>images</code>’ and the rest of the article to a flow 1.312 + named ‘<code class=property>text</code>’. Then define two pagination 1.313 + templates - one that has slots only for the ‘<code 1.314 + class=property>text</code>’ flow, and another that has slots for both 1.315 + the ‘<code class=property>text</code>’ and ‘<code 1.316 + class=property>images</code>’ flows. Both templates require the 1.317 + ‘<code class=property>text</code>’ flow, but the second template also 1.318 + requires the ‘<code class=property>images</code>’ flow and has an 1.319 + ‘<code class=property>available-content</code>’ declaration listing 1.320 + the ‘<code class=property>images</code>’ flow. Each time a page is 1.321 + laid out, the original article element is scanned to see whether an image 1.322 + element is in the next page's worth of content (determined by some 1.323 DOM-tree-scanning heuristic – not layout). If so, then that content 1.324 - from the ‘<code class=property>images</code>’ flow is 1.325 - available for the purpose of selecting a template. 1.326 + from the ‘<code class=property>images</code>’ flow is available for 1.327 + the purpose of selecting a template. 1.328 </div> 1.329 1.330 <div class=example> 1.331 @@ -748,32 +753,32 @@ 1.332 1.333 <dt id=CSS3-REGIONS>[CSS3-REGIONS] 1.334 1.335 - <dd>Vincent Hardy; Alex Mogilevsky. <a 1.336 - href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/"><cite>CSS 1.337 - Regions Module Level 3.</cite></a> 29 November 2011. W3C Working Draft. 1.338 + <dd>Vincent Hardy; Alex Mogilevsky; Alan Stearns. <a 1.339 + href="http://www.w3.org/TR/2012/WD-css3-regions-20120823/"><cite>CSS 1.340 + Regions Module Level 3.</cite></a> 23 August 2012. W3C Working Draft. 1.341 (Work in progress.) URL: <a 1.342 - href="http://www.w3.org/TR/2011/WD-css3-regions-20111129/">http://www.w3.org/TR/2011/WD-css3-regions-20111129/</a> 1.343 - </dd> 1.344 + href="http://www.w3.org/TR/2012/WD-css3-regions-20120823/">http://www.w3.org/TR/2012/WD-css3-regions-20120823/</a> 1.345 + </dd> 1.346 <!----> 1.347 1.348 <dt id=CSS3GCPM>[CSS3GCPM] 1.349 1.350 - <dd>Håkon Wium Lie. <a 1.351 + <dd>Håkon Wium Lie. <a 1.352 href="http://www.w3.org/TR/2010/WD-css3-gcpm-20100608"><cite>CSS 1.353 Generated Content for Paged Media Module.</cite></a> 8 June 2010. W3C 1.354 Working Draft. (Work in progress.) URL: <a 1.355 href="http://www.w3.org/TR/2010/WD-css3-gcpm-20100608">http://www.w3.org/TR/2010/WD-css3-gcpm-20100608</a> 1.356 - </dd> 1.357 + </dd> 1.358 <!----> 1.359 1.360 <dt id=CSS3GRID>[CSS3GRID] 1.361 1.362 <dd>Alex Mogilevsky; Markus Mielke. <a 1.363 href="http://www.w3.org/TR/2007/WD-css3-grid-20070905"><cite>CSS Grid 1.364 - Positioning Module Level 3.</cite></a> 5 September 2007. W3C Working 1.365 + Positioning Module Level 3.</cite></a> 5 September 2007. W3C Working 1.366 Draft. (Work in progress.) URL: <a 1.367 href="http://www.w3.org/TR/2007/WD-css3-grid-20070905">http://www.w3.org/TR/2007/WD-css3-grid-20070905</a> 1.368 - </dd> 1.369 + </dd> 1.370 <!----> 1.371 </dl> 1.372 <!--end-informative-->
2.1 --- a/css3-page-template/Overview.src.html Fri Oct 19 12:55:58 2012 -0700 2.2 +++ b/css3-page-template/Overview.src.html Fri Oct 19 13:17:29 2012 -0700 2.3 @@ -81,6 +81,7 @@ 2.4 <div class="issue-marker wrapper"> 2.5 <div class="issue-marker"><div class="issue-details">The draft as it stands requires pagination to present the repeated template layouts. Other methods of repeating template layouts to accommodate content might be specified, but the draft would need to be reviewed to remove all reliances on paged displays.</div></div> 2.6 <div class="issue-marker"><div class="issue-details">The terms 'template' and 'page' are overloaded in CSS, but they are the words that most clearly describe the concept. Some alternates for the main @ rule: template, page-template, view-template, page-master, master-template, master. Other suggestions are welcome, but only if they are more helpful than onelook.com (which suggested "Captain Submarine").</div></div> 2.7 + <div class="issue-marker"><div class="issue-details">This specification may be the best place to define "continued here" or "continued on page x" generated content, since this spec defines ways to skip pages (that basic pagination may not).</div></div> 2.8 </div> 2.9 2.10 <p>Pagination templates consist of anonymous boxes called slots created by CSS to contain content. Layouts that use pagination templates mainly determine the size of these slots from the template definition instead of the size of their content. When content does not fit into a template slot, additional pages are created with more slots to contain the overflow content.
3.1 --- a/css3-regions/Overview.html Fri Oct 19 12:55:58 2012 -0700 3.2 +++ b/css3-regions/Overview.html Fri Oct 19 13:17:29 2012 -0700 3.3 @@ -1692,15 +1692,6 @@ 3.4 3.5 <h2 id="pseudo_elements"><span class=secno>5. </span>Pseudo-elements</h2> 3.6 3.7 - <div class=issue-marker data-bug_id=15188 data-bug_status=NEW> <a 3.8 - href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15188">Issue-15188</a> 3.9 - 3.10 - <div class=issue-details> 3.11 - <p class=short-desc>add functionality for having textual description like 3.12 - "continued here" or "continued on page x" to regions. 3.13 - </div> 3.14 - </div> 3.15 - 3.16 <p>It can be useful to visually mark the content to highlight that a 3.17 content thread is flowing through the region chain. For example, a marker 3.18 such as <em>‘<code class=css>continued below</code>’</em> clearly
4.1 --- a/css3-regions/Overview.src.html Fri Oct 19 12:55:58 2012 -0700 4.2 +++ b/css3-regions/Overview.src.html Fri Oct 19 13:17:29 2012 -0700 4.3 @@ -1510,15 +1510,6 @@ 4.4 [[!CSS3COL]].</p> 4.5 4.6 <h2 id="pseudo_elements">Pseudo-elements</h2> 4.7 - 4.8 - <div class="issue-marker" data-bug_id="15188" data-bug_status="NEW"> 4.9 - <a href= 4.10 - "https://www.w3.org/Bugs/Public/show_bug.cgi?id=15188">Issue-15188</a> 4.11 - 4.12 - <div class="issue-details"> 4.13 - <p class="short-desc">add functionality for having textual description like "continued here" or "continued on page x" to regions.</p> 4.14 - </div> 4.15 - </div> 4.16 4.17 <p>It can be useful 4.18 to visually mark the content
