csswg-drafts/css-gcpm-4/Overview.html at 38bcadd2b50c8cf03f48dcee9ebc579692160ee2 · w3c/csswg-drafts · GitHub

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
<!DOCTYPE html><html lang=en><head>
  <meta content="text/html; charset=utf-8" http-equiv=Content-Type>
  <title>CSS Generated Content for Paged Media Module Level 4</title>
  <link href=../default.css rel=stylesheet type=text/css>
  <link href=../csslogo.ico rel="shortcut icon" type=image/x-icon>
  <style>
  body {
    background: url("https://www.w3.org/StyleSheets/TR/logo-ED") top left no-repeat white;
    background-attachment: fixed;
    color: black;
    font-family: sans-serif;
    margin: 0 auto;
    max-width: 50em;
    padding: 2em 1em 2em 70px;
  }
  :link { color: #00C; background: transparent }
  :visited { color: #609; background: transparent }
  a[href]:active { color: #C00; background: transparent }
  a[href]:hover { background: #ffa }

  a[href] img { border-style: none }

  h1, h2, h3, h4, h5, h6 { text-align: left }
  h1, h2, h3 { color: #005A9C; }
  h1 { font: 170% sans-serif }
  h2 { font: 140% sans-serif }
  h3 { font: 120% sans-serif }
  h4 { font: bold 100% sans-serif }
  h5 { font: italic 100% sans-serif }
  h6 { font: small-caps 100% sans-serif }

  .hide { display: none }

  div.head { margin-bottom: 1em }
  div.head h1 { margin-top: 2em; clear: both }
  div.head table { margin-left: 2em; margin-top: 2em }

  p.copyright { font-size: small }
  p.copyright small { font-size: small }

  pre { margin-left: 2em }
  dt { font-weight: bold }

  ul.toc, ol.toc {
    list-style: none;
  }
  </style>
</head>
<body class=h-entry>
<div class=head>
  <p data-fill-with=logo><a class=logo href=http://www.w3.org/>
    <img alt=W3C height=48 src=https://www.w3.org/Icons/w3c_home width=72>
</a>
</p>
  <h1 class="p-name no-ref" id=title>CSS Generated Content for Paged Media Module Level 4</h1>
  <h2 class="no-num no-toc no-ref heading settled heading" id=subtitle><span class=content>Editor’s Draft,
    <span class=dt-updated><span class=value-title title=20140910>10 September 2014</span></span></span></h2>
  <div data-fill-with=spec-metadata><dl>
	<dt>This version:
	<dd><a class=u-url href=http://dev.w3.org/csswg/css-gcpm-4/>http://dev.w3.org/csswg/css-gcpm-4/</a>
	<dt>Feedback:
	<dd><a href="mailto:www-style@w3.org?subject=%5Bcss-gcpm-4%5D%20feedback">www-style@w3.org</a>
            with subject line
            “<kbd>[css-gcpm-4] <var>… message topic …</var></kbd>”(<a href=http://lists.w3.org/Archives/Public/www-style/ rel=discussion>archives</a>)
	<dt>Editors:
	<dd><dd class="p-author h-card vcard"><a class="p-name fn u-email email" href=mailto:dauwhe@gmail.com>Dave Cramer</a> (<span class="p-org org">Hachette Livre</span>)
	<dd><dd class="p-author h-card vcard"><a class="p-name fn u-email email" href=mailto:daniel.glazman@disruptive-innovations.com>Daniel Glazman</a> (<span class="p-org org">Disruptive Innovations</span>)
	<dt>Issue Tracking:
	<dd><a href="https://www.w3.org/Bugs/Public/enter_bug.cgi?product=CSS&amp;component=Generated%20Content%20for%20Paged%20Media">W3C Bugzilla</a>
</dl>
</div>
  <div data-fill-with=warning><details class=annoying-warning open>
	<summary>Not Ready For Implementation</summary>
	<p>
		This spec is not yet ready for implementation.
		It exists in this repository to record the ideas and promote discussion.

	<p>
		Before attempting to implement this spec,
		please contact the CSSWG at www-style@w3.org.
</details>
</div>
  <p class=copyright data-fill-with=copyright><a href=http://www.w3.org/Consortium/Legal/ipr-notice#Copyright>Copyright</a> © 2014 <a href=http://www.w3.org/><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href=http://www.csail.mit.edu/><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href=http://www.ercim.eu/><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href=http://www.keio.ac.jp/>Keio</a>, <a href=http://ev.buaa.edu.cn/>Beihang</a>), All Rights Reserved. W3C <a href=http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer>liability</a>, <a href=http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks>trademark</a> and <a href=http://www.w3.org/Consortium/Legal/copyright-documents>document use</a> rules apply.
</p>
  <hr title="Separat
8000
or for header">
</div>

<h2 class="no-num no-toc no-ref heading settled heading" id=abstract><span class=content>Abstract</span></h2>
<div class=p-summary data-fill-with=abstract><p>Level 4 of GCPM proposes a region-based approach to footnotes and running heads.</p>

<a href=http://www.w3.org/TR/CSS/>CSS</a> is a language for describing the rendering of structured documents
(such as HTML and XML)
on screen, on paper, in speech, etc.</div>

<h2 class="no-num no-toc no-ref heading settled heading" id=status><span class=content>Status of this document</span></h2>
<div data-fill-with=status><p>
	This is a public copy of the editors’ draft.
	It is provided for discussion only and may change at any moment.
	Its publication here does not imply endorsement of its contents by W3C.
	Don’t cite this document other than as work in progress.

<p>
	The (<a href=http://lists.w3.org/Archives/Public/www-style/>archived</a>) public mailing list
	<a href="mailto:www-style@w3.org?Subject=%5Bcss-gcpm-4%5D%20PUT%20SUBJECT%20HERE">www-style@w3.org</a>
	(see <a href=http://www.w3.org/Mail/Request>instructions</a>)
	is preferred for discussion of this specification.
	When sending e-mail,
	please put the text “css-gcpm-4” in the subject,
	preferably like this:
	“[css-gcpm-4] <em>…summary of comment…</em>”

<p>
	This document was produced by the <a href=http://www.w3.org/Style/CSS/members>CSS Working Group</a>
	(part of the <a href=http://www.w3.org/Style/>Style Activity</a>).

<p>
	This document was produced by a group operating under
	the <a href=http://www.w3.org/Consortium/Patent-Policy-20040205/>5 February 2004 W3C Patent Policy</a>.
	W3C maintains a <a href=http://www.w3.org/2004/01/pp-impl/32061/status rel=disclosure>public list of any patent disclosures</a>
	made in connection with the deliverables of the group;
	that page also includes instructions for disclosing a patent.
	An individual who has actual knowledge of a patent which the individual believes contains <a href=http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential>Essential Claim(s)</a>
	must disclose the information in accordance with <a href=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure>section 6 of the W3C Patent Policy</a>.</div>
<div data-fill-with=at-risk></div>

<h2 class="no-num no-toc no-ref heading settled heading" id=contents><span class=content>Table of Contents</span></h2>
<div data-fill-with=table-of-contents><ul class=toc>
	<li><a href=#introduction><span class=secno></span>  	Introduction </a>
	<li><a href=#running-headers-and-footers><span class=secno>1</span>  	Running headers and footers </a>
		<ul class=toc>
		<li><a href=#flow-policy-heading><span class=secno>1.1</span> Copying a flow: the <span class=property data-link-type=propdesc title=flow-policy>flow-policy</span> property</a>
		<li><a href=#flow-persist-heading><span class=secno>1.2</span> Making “sticky” headers: the <span class=property data-link-type=propdesc title=flow-persist>flow-persist</span> property</a></ul>
	<li><a href=#page-area-head><span class=secno>2</span> Creating Page Areas</a>
	<li><a href=#footnotes><span class=secno>3</span>  	Footnotes </a>
		<ul class=toc>
		<li><a href=#footnote-terms><span class=secno>3.1</span> Terminology</a>
		<li><a href=#footnotes-as-regions><span class=secno>3.2</span> Footnotes as Regions</a></ul>
	<li><a href=#acknowledgments><span class=secno></span>  Acknowledgments </a>
	<li><a href=#conformance><span class=secno></span>  Conformance</a>
		<ul class=toc>
		<li><a href=#conventions><span class=secno></span>  Document conventions</a>
		<li><a href=#conformance-classes><span class=secno></span>  Conformance classes</a>
		<li><a href=#partial><span class=secno></span>  Partial implementations</a>
		<li><a href=#experimental><span class=secno></span>  Experimental implementations</a>
		<li><a href=#testing><span class=secno></span>  Non-experimental implementations</a></ul>
	<li><a href=#references><span class=secno></span>  References</a>
		<ul class=toc>
		<li><a href=#normative><span class=secno></span>  Normative References</a>
		<li><a href=#informative><span class=secno></span>  Informative References</a></ul>
	<li><a href=#index><span class=secno></span>  Index</a>
	<li><a href=#property-index><span class=secno></span>  Property index</a>
	<li><a href=#issues-index><span class=secno></span> Issues Index</a></ul></div>


<h2 class="no-num heading settled heading" id=introduction><span class=content>
	Introduction
</span></h2>

<p>There have been many proposals for using CSS to move document content, often motivated by the desire for magazine- or book-style layout of footnotes, running heads, pull quotes, sidebars, and so on. <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3gcpm title=biblio-CSS3GCPM>[CSS3GCPM]</a> used float: footnote and position: running(). The now-abandoned <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3gencon title=biblio-CSS3GENCON>[CSS3GENCON]</a> Working Draft used content: footnote. PrinceXML (and older GCPM drafts) has content: flow() and flow: static(). WHATWG CSS Books has flow: area().</p>

<p>This module proposes a unified approach to paginated layout based on <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3-regions title=biblio-CSS3-REGIONS>[CSS3-REGIONS]</a> and <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3-page-template title=biblio-CSS3-PAGE-TEMPLATE>[CSS3-PAGE-TEMPLATE]</a>. Additional properties will be introduced as necessary.</p>


<h2 class="heading settled heading" data-level=1 id=running-headers-and-footers><span class=secno>1 </span><span class=content>
	Running headers and footers
</span><a class=self-link href=#running-headers-and-footers></a></h2>
<a data-biblio-type=informative data-link-type=biblio href=#biblio-css3page title=biblio-CSS3PAGE>[CSS3PAGE]</a> describes the sixteen page margin boxes which can be used for running headers and footers, but does not describe a mechanism for inserting content in those boxes.

<p><a data-biblio-type=informative data-link-type=biblio href=#biblio-css3gcpm title=biblio-CSS3GCPM>[CSS3GCPM]</a> provides for copying the string values of elements into the existing page margin boxes.</p>

<p>The existing mechanisms do not cover many use cases.</p>


<h3 class="heading settled heading" data-level=1.1 id=flow-policy-heading><span class=secno>1.1 </span><span class=content>Copying a flow: the <a class=property data-link-type=propdesc href=#propdef-flow-policy title=flow-policy>flow-policy</a> property</span><a class=self-link href=#flow-policy-heading></a></h3>

<p>Headers often contain document content, and it is desirable to both display that content normally (for example, as an <code>h1</code>) and to use the content in a running head. <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3-regions title=biblio-CSS3-REGIONS>[CSS3-REGIONS]</a> only allows for an element to be moved to a <span class=css data-link-type=maybe title="named flow">named flow</span>, so we add the <a class=property data-link-type=propdesc href=#propdef-flow-policy title=flow-policy>flow-policy</a> property to allow the same element to serve two roles.</p>

<p class=note>Use cases for running heads can be found in [[LATINREQ] http://w3c.github.io/dpub-pagination/#content</p>


<table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-flow-policy>flow-policy<a class=self-link href=#propdef-flow-policy></a></dfn><tr><th>Value:<td class=prod>extract <a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#comb-one title=|>|</a> copy<tr><th>Initial:<td>extract<tr><th>Applies to:<td>all elements with a value of <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-regions-1/#propdef-flow-into title=flow-into>flow-into</a> other than none.<tr><th>Inherited:<td>no<tr><th>Media:<td>visual<tr><th>Computed value:<td>as specified</table>

<dl>

<dt>extract</dt>
<dd>the element is taken out of its parent’s flow and placed into the named flow set by the value of the <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-regions-1/#propdef-flow-into title=flow-into>flow-into</a> property.</dd>

<dt>copy</dt>

<dd>the element remains into it’s normal parent’s flow but a copy of the element is also extracted from there and placed into the named flow set by the value of the <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-regions-1/#propdef-flow-into title=flow-into>flow-into</a> property.</dd>

</dl>

<div class=example>
<pre>h1 {
  flow-into: chapter-title element;
  flow-policy: copy;
  font-size: 1.5em;
}

@page {
  @top-center {
    flow-from: chapter-title;
    font-size: .9em;
    font-variant: small-caps;
    }
}
</pre>
</div>


<h3 class="heading settled heading" data-level=1.2 id=flow-persist-heading><span class=secno>1.2 </span><span class=content>Making “sticky” headers: the <a class=property data-link-type=propdesc href=#propdef-flow-persist title=flow-persist>flow-persist</a> property</span><a class=self-link href=#flow-persist-heading></a></h3>

<p>An element flowed into a running head should appear on every page until the value of the element changes, at which point the new value should be used. We define the <a class=property data-link-type=propdesc href=#propdef-flow-persist title=flow-persist>flow-persist</a> property to control how content is rendered in region chains (????).</p>


<p>We also need to specify which element is used in a running head, when there are multiple possibilities. <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3gcpm title=biblio-CSS3GCPM>[CSS3GCPM]</a> defines start, first, last, and first-except values.</p>


<table class="definition propdef"><tr><th>Name:<td><dfn class=css-code data-dfn-type=property data-export="" id=propdef-flow-persist>flow-persist<a class=self-link href=#propdef-flow-persist></a></dfn><tr><th>Value:<td class=prod>( normal <a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#comb-one title=|>|</a> persist <a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#comb-one title=|>|</a> static )<a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#comb-comma title=,>,</a> ( start <a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#comb-one title=|>|</a> first <a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#comb-one title=|>|</a> last <a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#comb-one title=|>|</a> first-except)<a class=prod-punc data-link-type=grammar href=http://dev.w3.org/csswg/css-values-3/#mult-opt title=?>?</a><tr><th>Initial:<td>normal<tr><th>Applies to:<td>all elements with a value of <a class=property data-link-type=propdesc href=http://dev.w3.org/csswg/css-regions-1/#propdef-flow-from title=flow-from>flow-from</a> other than none.<tr><th>Inherited:<td>no<tr><th>Media:<td>visual<tr><th>Computed value:<td>as specified</table>

<dl>

<dt>normal</dt>
<dd>Content from the named flow is rendered as described in <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3-regions title=biblio-CSS3-REGIONS>[CSS3-REGIONS]</a>.</dd>

<dt>persist</dt>

<dd>Eligible content from the named flow is placed into the first box of the region chain as usual. If there is no eligible content on subsequent pages, the last-used content is used in the region box until new eligible content appears.

</dd>

<p class=issue id=issue-f9ac7b46><a class=self-link href=#issue-f9ac7b46></a>“That is not what I meant at all; That is not it, at all.”   —T.S. Eliot</p>


<dt>static</dt>

<dd>The first instance of the element is used in every region associated with the region chain (this is the equivalent of flow-options: static in <a data-biblio-type=informative data-link-type=biblio href=#biblio-pgt title=biblio-PGT>[PGT]</a>).</dd>

</dl>

<p class=issue id=issue-24246d23><a class=self-link href=#issue-24246d23></a>Above definitions need work</p>

<dl>

<dt>first</dt>
<dd>The value of the first assignment on the page is used. If there is no assignment on the page, the entry value is used. first is the default value.</dd>

<dt>start</dt>

<dd>If the element is the first element on the page, the value of the first assignment is used. Otherwise the entry value is used. The entry value may be empty if the element hasn’t yet appeared. </dd>

<dt>last</dt>

<dd>The exit value is used.</dd>

<dt>first-except</dt>

<dd>This is identical to first, except that the empty string is used on the page where the value is assigned.</dd>

</dl>


<div class=example>

<pre>h1 {
  flow-into: chapter-title element;
  flow-policy: copy;
}

@page {
  @top-center {
    flow-from: chapter-title;
    flow-persist: persist start;
    }
}

</pre>

<p>The @top-center margin box will be populated with the content of the <code>h1</code>. The <code>h1</code> will also appear in the document in its normal place.
</div><p></p>

<h2 class="heading settled heading" data-level=2 id=page-area-head><span class=secno>2 </span><span class=content>Creating Page Areas</span><a class=self-link href=#page-area-head></a></h2>


<p><a data-biblio-type=informative data-link-type=biblio href=#biblio-css3-page-template title=biblio-CSS3-PAGE-TEMPLATE>[CSS3-PAGE-TEMPLATE]</a> introduces @template and @slot rules. We propose to allow the use of @slot in the @page context, to allow greater flexibility than the page margin boxes in <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3page title=biblio-CSS3PAGE>[CSS3PAGE]</a>. These slots can also be used for sidenotes, pull quotes, footnotes, and many other document features.</p>


<div class=example>

<pre>
@page body {
  @slot center-header {
    top: 0px;
    left: 1em;
    right: 1em;
    height: 2em;
    flow-from: header;
    flow-persist: persist;
    wrap-flow: clear;
  }
}

</pre>


</div>


<p class=issue id=issue-de25de6c><a class=self-link href=#issue-de25de6c></a>Is there a need for both @page and @template?</p>


<h2 class="heading settled heading" data-level=3 id=footnotes><span class=secno>3 </span><span class=content>
	Footnotes
</span><a class=self-link href=#footnotes></a></h2>
Ancillary content may be moved to the bottom or side of a page. A footnote is created when such content moves to the bottom of the page, leaving a reference indicator.


<h3 class="heading settled heading" data-level=3.1 id=footnote-terms><span class=secno>3.1 </span><span class=content>Terminology</span><a class=self-link href=#footnote-terms></a></h3>

<p>Footnotes are complex objects, so it will be helpful to define some terms before proceeding.</p>

<figure>


<p><img alt="page with footnotes" src=images/footnote-diagram.001.jpg width=480>
</p><figcaption>Footnote terminology</figcaption>
</figure><p></p>

<dl>


<dt>footnote element</dt>
<dd>The element containing the content of the footnote, which will be removed from the flow and displayed as a footnote.</dd>

<dt>footnote marker (also known as footnote number)</dt>
<dd>A number or symbol adjacent to the footnote body, identifying the particular footnote. The footnote marker should use the same number or symbol as the corresponding footnote call, although the marker may contain additional punctuation.</dd>

<dt>footnote body</dt>
<dd>The footnote marker is placed before the footnote element, and together they represent the footnote body, which will be placed in the footnote area.</dd>

<dt>footnote call (also known as footnote reference)</dt>
<dd>A number or symbol, found in the main text, which points to the footnote body.</dd>


<dt>footnote area</dt>
<dd>The page area used to display footnotes.</dd>

<dt>footnote rule (also known as footnote separator)</dt>
<dd>A horizontal rule is often used to separate the footnote area from the rest of the page. The separator (and the entire footnote area) cannot be rendered on a page with no footnotes.</dd>

</dl>

<h3 class="heading settled heading" data-level=3.2 id=footnotes-as-regions><span class=secno>3.2 </span><span class=content>Footnotes as Regions</span><a class=self-link href=#footnotes-as-regions></a></h3>


<div class=example>
HTML:
<pre style="word-wrap: break-word; white-space: pre-wrap;">&lt;p&gt;Though the body was erect, the head was thrown back so that the closed eyes were pointed towards the needle of the tell-tale that swung from a beam in the ceiling..&lt;span class="reference"&gt;&lt;span class="footnote"&gt;The cabin-compass is called the tell-tale, because without going to the compass at the helm, the Captain, while below, can inform himself of the course of the ship.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
</pre>
<p>CSS:
<pre>span.footnote {
  flow-into: footnote;
  flow-policy: copy;
  display: block;
}

span.footnote::before {
  content: counter(footnote) '. ';
}

span.reference::before {
  content: counter(footnote);
  font-variant-position: super;
}

@page {
  @slot footnote {
    flow-from: footnote;
    required-flow: footnote;
    position: absolute;
    left: 54pt;
    bottom: 0pt;
    width: 352pt;
    height: auto;
    border-top: .25pt solid black;
    vertical-align: bottom;
    wrap-flow: clear;
  }
}
</pre><p></p>

</div>

<p class=issue id=issue-5b376f66><a class=self-link href=#issue-5b376f66></a>The above HTML contains two nested spans for the footnote, as CSS has no mechanism to leave a reference object where something was removed from the flow.</p>

<p class=issue id=issue-12a3563a><a class=self-link href=#issue-12a3563a></a>Would it be possible to specify <code>flow-into: none</code> on <code>span.footnote::after</code>? <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3-regions title=biblio-CSS3-REGIONS>[CSS3-REGIONS]</a> forbids the flow-into property on pseudo-elements, but should that be changed?</p>


<div class=example>
Inline footnote
<pre>span.footnote {
  flow-into: footnote;
  display: inline;
}
</pre>
</div>


<p></p>


<h2 class="no-num heading settled heading" id=acknowledgments><span class=content>
Acknowledgments
</span><a class=self-l
77EC
ink href=#acknowledgments></a></h2>

<p>Tab Atkins, Jr., Håkon Wium Lie, Liam Quin, Peter Sorotokin, Alan Stearns</p>


<h2 class="no-ref no-num heading settled heading" id=conformance><span class=content>
Conformance</span><a class=self-link href=#conformance></a></h2>

<h3 class="no-ref heading settled heading" id=conventions><span class=content>
Document conventions</span><a class=self-link href=#conventions></a></h3>

    <p>Conformance requirements are expressed with a combination of
    descriptive assertions and RFC 2119 terminology. The key words "MUST",
    "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
    "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
    document are to be interpreted as described in RFC 2119.
    However, for readability, these words do not appear in all uppercase
    letters in this specification.

    <p>All of the text of this specification is normative except sections
    explicitly marked as non-normative, examples, and notes. <a data-biblio-type=normative data-link-type=biblio href=#biblio-rfc2119 title=biblio-RFC2119>[RFC2119]</a></p>

    <p>Examples in this specification are introduced with the words "for example"
    or are set apart from the normative text with <code>class="example"</code>,
    like this:

    <div class=example>
        <p>This is an example of an informative example.</p>
    </div>

    <p>Informative notes begin with the word "Note" and are set apart from the
    normative text with <code>class="note"</code>, like this:

    <p class=note>Note, this is an informative note.</p>

    <p>Advisements are normative sections styled to evoke special attention and are
    set apart from other normative text with <code>&lt;strong class="advisement"&gt;</code>, like
    this:

    <strong class=advisement>
        UAs MUST provide an accessible alternative.
    </strong>

<h3 class="no-ref heading settled heading" id=conformance-classes><span class=content>
Conformance classes</span><a class=self-link href=#conformance-classes></a></h3>

    <p>Conformance to this specification
    is defined for three conformance classes:
    <dl>
        <dt>style sheet
            <dd>A <a href=http://www.w3.org/TR/CSS21/conform.html#style-sheet>CSS
            style sheet</a>.
        <dt>renderer
            <dd>A <a href=http://www.w3.org/TR/CSS21/conform.html#user-agent>UA</a>
            that interprets the semantics of a style sheet and renders
            documents that use them.
        <dt>authoring tool
            <dd>A <a href=http://www.w3.org/TR/CSS21/conform.html#user-agent>UA</a>
            that writes a style sheet.
    </dl>

    <p>A style sheet is conformant to this specification
    if all of its statements that use syntax defined in this module are valid
    according to the generic CSS grammar and the individual grammars of each
    feature defined in this module.

    <p>A renderer is conformant to this specification
    if, in addition to interpreting the style sheet as defined by the
    appropriate specifications, it supports all the features defined
    by this specification by parsing them correctly
    and rendering the document accordingly. However, the inability of a
    UA to correctly render a document due to limitations of the device
    does not make the UA non-conformant. (For example, a UA is not
    required to render color on a monochrome monitor.)

    <p>An authoring tool is conformant to this specification
    if it writes style sheets that are syntactically correct according to the
    generic CSS grammar and the individual grammars of each feature in
    this module, and meet all other conformance requirements of style sheets
    as described in this module.

<h3 class="no-ref heading settled heading" id=partial><span class=content>
Partial implementations</span><a class=self-link href=#partial></a></h3>

    <p>So that authors can exploit the forward-compatible parsing rules to
    assign fallback values, CSS renderers <strong>must</strong>
    treat as invalid (and <a href=http://www.w3.org/TR/CSS21/conform.html#ignore>ignore
    as appropriate</a>) any at-rules, properties, property values, keywords,
    and other syntactic constructs for which they have no usable level of
    support. In particular, user agents <strong>must not</strong> selectively
    ignore unsupported component values and honor supported values in a single
    multi-value property declaration: if any value is considered invalid
    (as unsupported values must be), CSS requires that the entire declaration
    be ignored.</p>

<h3 class="no-ref heading settled heading" id=experimental><span class=content>
Experimental implementations</span><a class=self-link href=#experimental></a></h3>

    <p>To avoid clashes with future CSS features, the CSS2.1 specification
    reserves a <a href=http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords>prefixed
    syntax</a> for proprietary and experimental extensions to CSS.

    <p>Prior to a specification reaching the Candidate Recommendation stage
    in the W3C process, all implementations of a CSS feature are considered
    experimental. The CSS Working Group recommends that implementations
    use a vendor-prefixed syntax for such features, including those in
    W3C Working Drafts. This avoids incompatibilities with future changes
    in the draft.
    </p>

<h3 class="no-ref heading settled heading" id=testing><span class=content>

    <p>Once a specification reaches the Candidate Recommendation stage,
    non-experimental implementations are possible, and implementors should
    release an unprefixed implementation of any CR-level feature they
    can demonstrate to be correctly implemented according to spec.

    <p>To establish and maintain the interoperability of CSS across
    implementations, the CSS Working Group requests that non-experimental
    CSS renderers submit an implementation report (and, if necessary, the
    testcases used for that implementation report) to the W3C before
    releasing an unprefixed implementation of any CSS features. Testcases
    submitted to W3C are subject to review and correction by the CSS
    Working Group.

    <p>Further information on submitting testcases and implementation reports
    can be found from on the CSS Working Group’s website at
    <a href=http://www.w3.org/Style/CSS/Test/>http://www.w3.org/Style/CSS/Test/</a>.
    Questions should be directed to the
    <a href=http://lists.w3.org/Archives/Public/public-css-testsuite>public-css-testsuite@w3.org</a>
    mailing list.

<h2 class="no-num no-ref heading settled heading" id=references><span class=content>
References</span><a class=self-link href=#references></a></h2>

<h3 class="no-num no-ref heading settled heading" id=normative><span class=content>
Normative References</span><a class=self-link href=#normative></a></h3>
<div data-fill-with=normative-references><dl>
<dt id=biblio-rfc2119 title=RFC2119><a class=self-link href=#biblio-rfc2119></a>[RFC2119]<dd>S. Bradner. <a href=http://www.ietf.org/rfc/rfc2119.txt>Key words for use in RFCs to Indicate Requirement Levels</a>. URL: <a href=http://www.ietf.org/rfc/rfc2119.txt>http://www.ietf.org/rfc/rfc2119.txt</a></dd>
</dl></div>

<h3 class="no-num no-ref heading settled heading" id=informative><span class=content>
Informative References</span><a class=self-link href=#informative></a></h3>
<div data-fill-with=informative-references><dl>
<dt id=biblio-css3-page-template title=CSS3-PAGE-TEMPLATE><a class=self-link href=#biblio-css3-page-template></a>[CSS3-PAGE-TEMPLATE]<dd>Alan Stearns. <a href=http://dev.w3.org/csswg/css3-page-template/>CSS Pagination Templates Module Level 3</a>. Proposal for a CSS module. (Retrieved 4 April 2012) URL: <a href=http://dev.w3.org/csswg/css3-page-template/>http://dev.w3.org/csswg/css3-page-template/</a></dd>
<dt id=biblio-css3-regions title=CSS3-REGIONS><a class=self-link href=#biblio-css3-regions></a>[CSS3-REGIONS]<dd>Vincent Hardy; Rossen Atanassov; Alan Stearns. <a href=http://www.w3.org/TR/2013/WD-css3-regions-20130528/>CSS Regions Module Level 1</a>. 28 May 2013. W3C Working Draft. (Work in progress.) URL: <a href=http://www.w3.org/TR/2013/WD-css3-regions-20130528/>http://www.w3.org/TR/2013/WD-css3-regions-20130528/</a></dd>
<dt id=biblio-css3gcpm title=CSS3GCPM><a class=self-link href=#biblio-css3gcpm></a>[CSS3GCPM]<dd>Håkon Wium Lie. <a href=http://www.w3.org/TR/2011/WD-css3-gcpm-20111129/>CSS Generated Content for Paged Media Module</a>. 29 November 2011. W3C Working Draft. (Work in progress.) URL: <a href=http://www.w3.org/TR/2011/WD-css3-gcpm-20111129/>http://www.w3.org/TR/2011/WD-css3-gcpm-20111129/</a></dd>
<dt id=biblio-css3gencon title=CSS3GENCON><a class=self-link href=#biblio-css3gencon></a>[CSS3GENCON]<dd>Ian Hickson. <a href=http://www.w3.org/TR/2003/WD-css3-content-20030514>CSS3 Generated and Replaced Content Module</a>. 14 May 2003. W3C Working Draft. (Work in progress.) URL: <a href=http://www.w3.org/TR/2003/WD-css3-content-20030514>http://www.w3.org/TR/2003/WD-css3-content-20030514</a></dd>
<dt id=biblio-css3page title=CSS3PAGE><a class=self-link href=#biblio-css3page></a>[CSS3PAGE]<dd>Melinda Grant; et al. <a href=http://www.w3.org/TR/2013/WD-css3-page-20130314/>CSS Paged Media Module Level 3</a>. 14 March 2013. W3C Working Draft. (Work in progress.) URL: <a href=http://www.w3.org/TR/2013/WD-css3-page-20130314/>http://www.w3.org/TR/2013/WD-css3-page-20130314/</a></dd>
</dl></div>

<h2 class="no-num no-ref heading settled heading" id=index><span class=content>
Index</span><a class=self-link href=#index></a></h2>
<div data-fill-with=index><ul class=indexlist>
<li>flow-persist, <a href=#propdef-flow-persist title="section 1.2">1.2</a>
<li>flow-policy, <a href=#propdef-flow-policy title="section 1.1">1.1</a>
</ul></div>

<h2 class="no-num no-ref heading settled heading" id=property-index><span class=content>
Property index</span><a class=self-link href=#property-index></a></h2>
<div data-fill-with=property-index><table class="proptable data"><thead><tr><th scope=col>Name<th scope=col>Value<th scope=col>Initial<th scope=col>Applies to<th scope=col>Inh.<th scope=col>%ages<th scope=col>Media<th scope=col>Computed value<tbody>
<tr><th scope=row><a class=css-code data-link-type=property href=#propdef-flow-policy title=flow-policy>flow-policy</a><td>extract | copy<td>extract<td>all elements with a value of flow-into other than none.<td>no<td><td>visual<td>as specified
<tr><th scope=row><a class=css-code data-link-type=property href=#propdef-flow-persist title=flow-persist>flow-persist</a><td>( normal | persist | static ), ( start | first | last | first-except)?<td>normal<td>all elements with a value of flow-from other than none.<td>no<td><td>visual<td>as specified</table></div>


<h2 class="no-num heading settled" id=issues-index><span class=content>Issues Index</span><a class=self-link href=#issues-index></a></h2><div style="counter-reset: issue"><div class=issue>“That is not what I meant at all; That is not it, at all.”   —T.S. Eliot<a href=#issue-f9ac7b46> ↵ </a></div><div class=issue>Above definitions need work<a href=#issue-24246d23> ↵ </a></div><div class=issue>Is there a need for both @page and @template?<a href=#issue-de25de6c> ↵ </a></div><div class=issue>The above HTML contains two nested spans for the footnote, as CSS has no mechanism to leave a reference object where something was removed from the flow.<a href=#issue-5b376f66> ↵ </a></div><div class=issue>Would it be possible to specify <code>flow-into: none</code> on <code>span.footnote::after</code>? <a data-biblio-type=informative data-link-type=biblio href=#biblio-css3-regions title=biblio-CSS3-REGIONS>[CSS3-REGIONS]</a> forbids the flow-into property on pseudo-elements, but should that be changed?<a href=#issue-12a3563a> ↵ </a></div></div>