css-overflow/Overview.src.html@ecc3593f6bc6
css-overflow/Overview.src.html
Mon, 10 Feb 2014 00:07:22 -0800
- author
- L. David Baron <dbaron@dbaron.org>
- date
- Mon, 10 Feb 2014 00:07:22 -0800
- changeset 9966
- ecc3593f6bc6
- parent 9865
- 625d8c1b183a
- child 14821
- db327947a378
- permissions
- -rw-r--r--
[css-overflow] Another issue about preserve-3d overflow handling.
1 <!DOCTYPE html>
2 <html lang="en">
3 <head>
4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
5 <title>CSS Overflow Module Level 3</title>
6 <link rel=contents href="#contents">
7 <link rel=index href="#index">
8 <link rel="stylesheet" type="text/css" href="../default.css">
9 <link rel="stylesheet" type="text/css"
10 href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS].css">
11 <style>
12 table.source-demo-pair {
13 width: 100%;
14 }
16 .in-cards-demo {
17 width: 13em;
18 height: 8em;
20 padding: 4px;
21 border: medium solid blue;
22 margin: 6px;
24 font: medium/1.3 Times New Roman, Times, serif;
25 white-space: nowrap;
26 }
28 .bouncy-columns-demo {
29 width: 6em;
30 height: 10em;
31 float: left;
32 margin: 1em;
33 font: medium/1.25 Times New Roman, Times, serif;
34 white-space: nowrap;
35 }
36 .bouncy-columns-demo.one {
37 background: aqua; color: black;
38 transform: rotate(-3deg);
39 }
40 .bouncy-columns-demo.two {
41 background: yellow; color: black;
42 transform: rotate(3deg);
43 }
45 .article-font-inherit-demo {
46 font: 1em/1.25 Times New Roman, Times, serif;
47 white-space: nowrap;
48 }
49 .article-font-inherit-demo.one {
50 width: 12em;
51 font-size: 1.5em;
52 margin-bottom: 1em;
53 height: 4em;
54 }
55 .article-font-inherit-demo.two {
56 width: 11em;
57 margin-left: 5em;
58 margin-right: 2em;
59 }
61 .dark-columns-demo {
62 width: 6em;
63 height: 10em;
64 float: left;
65 margin-right: 1em;
66 font: medium/1.25 Times New Roman, Times, serif;
67 white-space: nowrap;
68 }
69 .dark-columns-demo.one {
70 background: aqua; color: black;
71 }
72 .dark-columns-demo.one :link {
73 color: blue;
74 }
75 .dark-columns-demo.one :visited {
76 color: purple;
77 }
78 .dark-columns-demo.two {
79 background: navy; color: white;
80 }
81 .dark-columns-demo.two :link {
82 color: aqua;
83 }
84 .dark-columns-demo.two :visited {
85 color: fuchsia;
86 }
88 .article-max-lines-demo {
89 font: 1em/1.25 Times New Roman, Times, serif;
90 white-space: nowrap;
91 }
92 .article-max-lines-demo.one::first-letter {
93 font-size: 2em;
94 line-height: 0.9;
95 }
96 .article-max-lines-demo.one {
97 font-size: 1.5em;
98 width: 16em;
99 }
100 .article-max-lines-demo.two {
101 width: 11.5em;
102 float: left; margin-right: 1em;
103 }
104 .article-max-lines-demo.three {
105 width: 11.5em;
106 float: left;
107 }
108 </style>
109 </head>
111 <div class="head">
112 <!--logo-->
114 <h1>CSS Overflow Module Level 3</h1>
116 <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
117 <dl>
118 <dt>This version:
119 <dd><a href="[VERSION]">[VERSION]</a>
121 <dt>Latest version:
122 <dd><a href="http://www.w3.org/TR/css-overflow-3/">http://www.w3.org/TR/css-overflow-3/</a>
124 <dt>Editor's draft:
125 <dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">http://dev.w3.org/csswg/[SHORTNAME]/</a>
126 (<a href="https://dvcs.w3.org/hg/csswg/log/tip/css-overflow/Overview.src.html">change log</a>,
127 <a href="https://dvcs.w3.org/hg/csswg/log/tip/css3-overflow/Overview.src.html">older change log</a>)
129 <dt>Previous version:
130 <dd><a href="http://www.w3.org/TR/2013/WD-css-overflow-3-20130418/">http://www.w3.org/TR/2013/WD-css-overflow-3-20130418/</a>
132 <dt>Editors:
133 <dd class="h-card vcard">
134 <a class="p-name fn u-url url" rel="author"
135 href="http://dbaron.org/">L. David Baron</a>,
136 <a class="p-org org" href="http://www.mozilla.org/">Mozilla</a>
138 <dt>Issue Tracking:</dt>
139 <dd>Maintained in document (only editor's draft is current)
141 <dt>Feedback:</dt>
142 <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-overflow%5D%20feedback"
143 >www-style@w3.org</a>
144 with subject line “<kbd>[css-overflow]
145 <var>… message topic …</var></kbd>”
146 (<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/"
147 >archives</a>)
149 <dt>Test suite:
150 <dd>none yet
151 </dl>
153 <!--copyright-->
155 <hr title="Separator for header">
156 </div>
158 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
160 <p>
161 <a href="http://www.w3.org/TR/CSS/">CSS</a> is
162 a language for describing
163 the rendering of structured documents (such as HTML and XML)
164 on screen, on paper, in speech, etc.
165 This module contains the features of CSS
166 relating to new mechanisms of overflow handling in visual media (e.g., screen or paper).
167 In interactive media,
168 it describes features that allow the overflow
169 from a fixed size container
170 to be handled by pagination (displaying one page at a time).
171 It also describes features, applying to all visual media,
172 that allow the contents of an element
173 to be spread across multiple fragments,
174 allowing the contents to flow across multiple regions
175 or to have different styles for different fragments.
176 </p>
178 <h2 class="no-num no-toc" id="status">Status of this document</h2>
180 <!--status-->
182 <p>The following features are at risk: …
184 <h2 class="no-num no-toc" id="contents">
185 Table of contents</h2>
187 <!--toc-->
189 <h2 id="intro">
190 Introduction</h2>
192 <p>
193 In CSS Level 1 [[CSS1]], placing more content than would fit
194 inside an element with a specified size
195 was generally an authoring error.
196 Doing so caused the content to extend
197 outside the bounds of the element,
198 which would likely cause
199 that content to overlap with other elements.
200 </p>
202 <p>
203 CSS Level 2 [[CSS21]] introduced the 'overflow' property,
204 which allows authors to have overflow be handled by scrolling,
205 which means it is no longer an authoring error.
206 It also allows authors to specify
207 that overflow is handled by clipping,
208 which makes sense when the author's intent
209 is that the content not be shown.
210 </p>
212 <p>
213 However, scrolling is not the only way
214 to present large amounts of content,
215 and may even not be the optimal way.
216 After all, the codex replaced the scroll
217 as the common format for large written works
218 because of its advantages.
219 </p>
221 <p>
222 This specification introduces
223 a mechanism for Web pages to specify
224 that an element of a page should handle overflow
225 through pagination rather than through scrolling.
226 </p>
228 <p>
229 This specification also extends the concept of overflow
230 in another direction.
231 Instead of requiring that authors specify a single area
232 into which the content of an element must flow,
233 this specification allows authors to specify multiple fragments,
234 each with their own dimensions and styles,
235 so that the content of the element can flow from one to the next,
236 using as many as needed to place the content without overflowing.
237 </p>
239 <p>
240 In both of these cases, implementations must
241 break the content in the block-progression dimension.
242 Implementations must do this is described
243 in the CSS Fragmentation Module [[!CSS3-BREAK]].
244 </p>
246 <h2 id="overflow-concepts">Types of overflow</h2>
248 <p>
249 CSS uses the term <dfn>overflow</dfn> to describe
250 the contents of a box
251 that extend outside that one of that box's edges
252 (i.e., its <i>content edge</i>, <i>padding edge</i>,
253 <i>border edge</i>, or <i>margin edge</i>).
254 The overflow might be described as the elements or features
255 that cause this overflow,
256 the non-rectangular region occupied by these features,
257 or, more commonly,
258 as the minimal rectangle that bounds that region.
259 A box's overflow is computed based on the boxes and styles
260 of the box and of all its descendants whose containing block chain
261 <span class="issue">undefined term?</span>
262 includes the box.
263 </p>
265 <p>
266 In most cases, any of these types of overflow
267 can be computed for any box
268 from the bounds and properties of that box,
269 and from the overflow (of that type)
270 of each of its children.
271 However, this is not always the case; for example,
272 when ''transform-style: preserve-3d'' [[CSS3-TRANSFORMS]] is used on
273 some of the children, their descendants with
274 ''transform-style: preserve-3d'' must also be examined.
275 </p>
277 <h3 id="ink-overflow">Ink overflow</h3>
279 <p>
280 The <dfn>ink overflow</dfn> of a box
281 is the part of that box and its contents that
282 creates a visual effect outside of
283 the box's border box.
284 </p>
286 <p>
287 Since some effects in CSS (for example, the blurs in
288 'text-shadow' [[CSS3TEXT]] and 'box-shadow' [[CSS3BG]])
289 do not define what visual extent they cover, the extent
290 of the <i>ink overflow</i> is undefined.
291 </p>
293 <p class="issue">
294 Should we try to define it at all and just leave pieces undefined?
295 </p>
297 <p>
298 The <dfn>ink overflow region</dfn> is the non-rectangular region
299 occupied by the <i>ink overflow</i>, and the
300 <dfn>ink overflow rectangle</dfn> is
301 the minimal rectangle whose axis is aligned to the box's axes
302 and contains the <i>ink overflow region</i>.
303 Note that the <i>ink overflow rectangle</i> is a rectangle
304 in the box's coordinate system, but might be non-rectangular
305 in other coordinate systems due to transforms [[CSS3-TRANSFORMS]].
306 </p>
308 <h3 id="scrollable-overflow">Scrollable overflow</h3>
310 <p>
311 The <dfn>scrollable overflow</dfn> of a box is the
312 set of things extending outside of that box's padding edge
313 for which a scrolling mechanism needs to be provided.
314 </p>
316 <p class="issue">
317 The following definition should be rewritten to use
318 the concept of <a href="http://dev.w3.org/csswg/css-transforms/#3d-rendering-context">3D rendering context</a> [[!CSS3-TRANSFORMS]]
319 and related terms,
320 particularly once those concepts stabilize following changes
321 proposed in the CSS WG meeting on the morning of 2014-01-28.
322 </p>
324 <p>
325 Given the following definitions
326 <span class="issue">which belong in [[CSS3-TRANSFORMS]]</span>:
327 </p>
329 <dl>
330 <dt><dfn>3d-preserving child</dfn></dt>
331 <dd>
332 A child box B of a containing block C is a 3d-preserving
333 child if it has ''transform-style: preserve-3d''
334 and the user-agent is not required to flatten it
335 based on the <a href="http://www.w3.org/TR/css3-transforms/#transform-style-property">requirements</a> in [[!CSS3-TRANSFORMS]].
336 </dt>
337 <dt><dfn>non-3d-preserving child</dfn></dt>
338 <dd>
339 A child C of a box P is a non-3d-preserving-child if
340 it is not a <i>3d-preserving child</i>.
341 </dd>
342 <dt><dfn>3d-preserving descendant</dfn></dt>
343 <dd>
344 Box D is a 3d-preserving descendant of box A if A is
345 an ancestor of D, and D and all of the boxes (if any)
346 in the containing block chain from D to A
347 are <i>3d-preserving child</i> boxes.
348 </dd>
349 </dl>
351 <p>The scrollable overflow of a box is the union of the following things,
352 all adjusted for transforms <span class="issue">undefined concept!</span> into the box's coordinate space:</p>
354 <ul>
355 <li>
356 for the box and all of its <i>3d-preserving descendant</i> boxes:
357 <ul>
358 <li>the box's own padding edge (for the box itself) or border edge (for <i>3d-preserving descendant</i> boxes)</li>
359 <li>the bounds <span class="issue">undefined term!</span> of any text directly in the box</li>
360 <li><span class="issue">MORE HERE!</span>
361 </ul>
362 <li>
363 for all the <i>non-3d-preserving child</i> boxes of the
364 box and its <i>3d-preserving descendant</i> boxes,
365 the scrollable overflow of the box
366 </li>
367 </ul>
369 <p class="issue">
370 I wrote this definition off the top of my head,
371 so it can't possibly be right.
372 It's missing tons of pieces!
373 </p>
375 <p class="issue">
376 The handling of preserve-3d subtrees here is probably wrong;
377 the elements should probably count
378 only towards the overflow of the element that flattens them.
379 </p>
381 <p>
382 The <dfn>scrollable overflow region</dfn> is the non-rectangular region
383 occupied by the <i>scrollable overflow</i>, and the
384 <dfn>scrollable overflow rectangle</dfn> is
385 the minimal rectangle whose axis is aligned to the box's axes
386 and contains the <i>scrollable overflow region</i>.
387 Note that the <i>scrollable overflow rectangle</i> is a rectangle
388 in the box's coordinate system, but might be non-rectangular
389 in other coordinate systems due to transforms [[CSS3-TRANSFORMS]].
390 </p>
392 <h3 id="border-box-overflow">Border box overflow</h3>
394 <p class="issue">
395 This concept has been proposed for some uses, such as for
396 determining what the 'outline' property goes around, and
397 as the basis of a coordinate system for specifying clips and masks,
398 but it's not clear if it's needed.
399 </p>
401 <p>
402 The <dfn>border-box overflow</dfn> of a box is the
403 union of the box's border edge and the border edges of
404 the box's descendants.</p>
405 </p>
407 <p class="issue">
408 If needed, define more formally, as for scrollable overflow above.
409 (Maybe even share the definitions in an appropriate way!)
410 </p>
412 <p>
413 The <dfn>border-box overflow region</dfn> is the non-rectangular region
414 occupied by the <i>border-box overflow</i>, and the
415 <dfn>border-box overflow rectangle</dfn> is
416 the minimal rectangle whose axis is aligned to the box's axes
417 and contains the <i>border-box overflow region</i>.
418 Note that the <i>border-box overflow rectangle</i> is a rectangle
419 in the box's coordinate system, but might be non-rectangular
420 in other coordinate systems due to transforms [[CSS3-TRANSFORMS]].
421 </p>
423 <h2 id="overflow-properties">Overflow properties</h2>
425 <p>
426 The ''overflow-x'' property specifies
427 the handling of overflow in the horizontal direction
428 (i.e., overflow from the left and right sides of the box),
429 and the ''overflow-y'' property specifies the handling
430 of overflow in the vertical direction
431 (i.e., overflow from the top and bottom sides of the box)
432 </p>
434 <table class=propdef>
435 <tr>
436 <th>Name:
437 <td><dfn>overflow-x</dfn>, <dfn>overflow-y</dfn>
438 <tr>
439 <th><a href="#values">Value</a>:
440 <td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
441 <tr>
442 <th>Initial:
443 <td>visible
444 <tr>
445 <th>Applies to:
446 <td>block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
447 <tr>
448 <th>Inherited:
449 <td>no
450 <tr>
451 <th>Percentages:
452 <td>N/A
453 <tr>
454 <th>Media:
455 <td>visual
456 <tr>
457 <th>Computed value:
458 <td>see below
459 <tr>
460 <th>Animatable:
461 <td>no
462 <tr>
463 <th>Canonical order:
464 <td><abbr title="follows order of property value definition">per grammar</abbr>
465 </table>
467 <p>
468 The 'overflow' property is a shorthand property
469 that sets the specified values of both 'overflow-x' and 'overflow-y'
470 to the value specified for 'overflow'.
471 </p>
473 <table class=propdef>
474 <tr>
475 <th>Name:
476 <td><dfn>overflow</dfn>
477 <tr>
478 <th><a href="#values">Value</a>:
479 <td>visible | hidden | scroll | auto | paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
480 <tr>
481 <th>Initial:
482 <td>see individual properties
483 <tr>
484 <th>Applies to:
485 <td>block containers [[!CSS21]], flex containers [[!CSS3-FLEXBOX]], and grid containers [[!CSS3-GRID-LAYOUT]]
486 <tr>
487 <th>Inherited:
488 <td>no
489 <tr>
490 <th>Percentages:
491 <td>N/A
492 <tr>
493 <th>Media:
494 <td>visual
495 <tr>
496 <th>Computed value:
497 <td>see individual properties
498 <tr>
499 <th>Animatable:
500 <td>no
501 <tr>
502 <th>Canonical order:
503 <td><abbr title="follows order of property value definition">per grammar</abbr>
504 </table>
506 <p>The values of these properties are:</p>
508 <dl>
509 <dt><dfn>visible</dfn>
510 <dd>
511 There is no special handling of overflow, that is, it
512 may be rendered outside the block container.
513 </dd>
514 <dt><dfn>hidden</dfn>
515 <dt><dfn>scroll</dfn>
516 <dt><dfn>auto</dfn>
517 <dd>
518 These values are collectively the <dfn>scrolling values</dfn>;
519 they are defined in the section on
520 <a href="#scrolling-overflow">scrolling and hidden overflow</a>.
521 </dd>
522 <dt><dfn>paged-x</dfn>
523 <dt><dfn>paged-y</dfn>
524 <dt><dfn>paged-x-controls</dfn>
525 <dt><dfn>paged-y-controls</dfn>
526 <dt><dfn>fragments</dfn>
527 <dd>
528 These values are collectively the <dfn>fragmenting values</dfn>;
529 they are defined in the sections on
530 <a href="#paginated-overflow">paginated overflow</a> and
531 <a href="#fragment-overflow">fragment overflow</a>.
532 </dd>
533 </dl>
535 <div id="overflow-computed-values">
536 <p>The computed values of 'overflow-x' and 'overflow-y'
537 are determined from the cascaded values [[!CSS3CASCADE]]
538 based on the following rules:</p>
540 <ol>
541 <li>
542 If one or both of the cascaded values are
543 <i>fragmenting values</i>, then:
544 <ol>
545 <li>
546 If one of the cascaded values is one of the
547 <i>fragmenting values</i>
548 and the other is not,
549 then the computed values are
550 the same as the cascaded values.
551 </li>
552 <li>
553 If both of the cascaded values are <i>fragmenting values</i>, then:
554 <ol>
555 <li>
556 for horizontal writing mode [[!CSS3-WRITING-MODES]],
557 the computed value for ''overflow-y'' is the cascaded value
558 and the computed value for ''overflow-x'' is ''hidden'', or
559 </li>
560 <li>
561 for vertical writing mode [[!CSS3-WRITING-MODES]],
562 the computed value for ''overflow-x'' is the cascaded value
563 and the computed value for ''overflow-y'' is ''hidden''.
564 </li>
565 </ol>
566 </li>
567 </ol>
568 </li>
569 <li>
570 Otherwise, if one cascaded values is
571 one of the <i>scrolling values</i>
572 and the other is ''visible'',
573 then computed values are the cascaded values
574 with ''visible'' changed to ''hidden''.
575 </li>
576 <li>
577 Otherwise, the computed values are as specified.
578 </li>
579 </ol>
580 </div>
582 <p class="issue">
583 Are all 4 of the ''paged-*'' values really needed?
584 </p>
586 <p>
587 When the <i>fragmenting values</i> are used,
588 the overflow from the fragments themselves
589 treats the fragmenting value as ''hidden''.
590 <span class="issue">Is this the right behavior?</span>
591 <span class="issue">Give example.</span>
592 </p>
594 <p class="issue">
595 [[CSS3-MARQUEE]] describes an 'overflow-style' property,
596 but it has not picked up implementation experience
597 that the working group is aware of.
598 Should this document treat 'overflow-style' as a defunct proposal,
599 or should this document describe the 'overflow-style' property
600 and attempt to revive it,
601 despite that implementations have implemented
602 'overflow-x' and 'overflow-y' instead?
603 </p>
605 <p class="issue">
606 There are <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussions</a>
607 about how overflow, overflow-style, overflow-x and overflow-y
608 should work and interact with each other.
609 Until consensus on this topic is reached,
610 it is not completely clear which of these
611 should be used for
612 paged-x | paged-y | paged-x-controls | paged-y-controls | fragments
613 </p>
615 <h2 id="scrolling-overflow">Scrolling and hidden overflow</h2>
617 <p class="issue">
618 Move material from [[CSS21]] and [[CSS3BOX]] here.
619 </p>
621 <h2 id="paginated-overflow">Paginated overflow</h2>
623 <p class="issue">overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as [[CSS3GCPM]] has?)</p>
625 <p class="issue">Ability to display N pages at once
626 rather than just one page at once?</p>
628 <p class="issue">
629 The current implementation of paginated overflow uses
630 the 'overflow'/'overflow-x'/'overflow-y' properties
631 rather than the 'overflow-style' property as proposed
632 in the [[CSS3GCPM]] draft
633 (which also matches the [[CSS3-MARQUEE]] proposal).
634 We should probably switch away from 'overflow-style',
635 but that's not 100% clear.
636 </p>
638 <h2 id="fragment-overflow">Fragment overflow</h2>
640 <p>
641 This section introduces and defines the meaning of
642 the new ''fragments'' value of the 'overflow' property.
643 </p>
645 <p>
646 When the computed value of 'overflow' for an element is ''fragments'',
647 and implementations would otherwise have created a box for the element,
648 then implementations must create a sequence of <dfn>fragment box</dfn>es
649 for that element.
650 (It is possible for an element with ''overflow: fragments''
651 to generate only one <i>fragment box</i>.
652 However, if an element's computed 'overflow' is not ''fragments'',
653 then its box is not a <i>fragment box</i>.)
654 Every <i>fragment box</i> is a fragmentation container,
655 and any overflow
656 that would cause that fragmentation container to fragment
657 causes another <i>fragment box</i> created as a next sibling
658 of the previous one.
659 <span class="issue">Or is it as though it's a next sibling of
660 the element? Need to figure out exactly how this interacts with
661 other box-level fixup.</span>
662 Additionally, if the <i>fragment box</i> is also
663 a multi-column box (as defined in [[!CSS3COL]]
664 <span class="issue">though it defines <i>multi-column element</i></span>)
665 any content that would lead to the creation of <i>overflow columns</i> [[!CSS3COL]]
666 instead is flown into an additional fragment box.
667 However, fragment boxes may themselves be broken
668 (due to fragmentation in a fragmentation context outside of them,
669 such as pages, columns, or other fragment boxes);
670 such breaking leads to fragments of the same fragment box
671 rather than multiple fragment boxes.
672 (This matters because fragment boxes may be styled by their index;
673 such breaking leads to multiple fragments of a fragment box
674 with a single index.
675 This design choice is so that
676 breaking a fragment box across pages does not break
677 the association of indices to particular pieces of content.)
678 <span class="issue">Should a forced break that breaks to
679 an outer fragmentation context cause a new fragment of a single
680 fragment box or a new fragment box?</span>
681 <span class="issue">Should we find a term other than
682 <i>fragment box</i> here to make this a little less confusing?</span>
683 </p>
685 <p class="issue">
686 What if we want to be able to style the pieces of an element
687 split within another type of fragmentation context?
688 These rules prevent ever using ''::nth-fragment()'' for that,
689 despite that the name seems the most logical name for such a feature.
690 </p>
692 <div class="example">
693 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML>
694 <title>Breaking content into
695 equal-sized cards</title>
696 <style>
697 .in-cards {
698 overflow: fragments;
700 width: 13em;
701 height: 8em;
703 padding: 4px;
704 border: medium solid blue;
705 margin: 6px;
707 font: medium/1.3 Times New
708 Roman, Times, serif;
709 }
710 </style>
711 <div class="in-cards">
712 In this example, the text in the div
713 is broken into a series of cards.
714 These cards all have the same style.
715 The presence of enough content to
716 overflow one of the cards causes
717 another one to be created. The second
718 card is created just like it's the
719 next sibling of the first.
720 </div></pre></td><td>
721 <div class="in-cards-demo">In this example, the text in the<br>div is broken into a series of<br>cards. These cards all have the<br>same style. The presence of<br>enough content to overflow<br>one of the cards causes another</div>
722 <div class="in-cards-demo">one to be created. The second<br>card is created just like it's the<br>next sibling of the first.</div>
723 </td></tr></table>
724 </div>
726 <p class="issue">
727 We should specify that ''overflow: fragments'' does not apply
728 to at least some table parts,
729 and perhaps other elements as well.
730 We need to determine exactly which ones.
731 </p>
733 <p class="issue">
734 This specification needs to say which type of
735 fragmentation context is created
736 so that it's clear which values of the 'break' property
737 cause breaks within this context.
738 We probably want ''break: regions'' to apply.
739 </p>
741 <p class="issue">
742 This specification needs a processing model
743 that will apply in cases where the layout containing the
744 fragments has characteristics that use the intrinsic size of the fragments
745 to change the amount of space available for them,
746 such as [[CSS3-GRID-LAYOUT]].
747 There has already been some work on such a processing model
748 in [[CSS3-REGIONS]],
749 and the work done on a model there,
750 and the editors of that specification,
751 should inform what happens in this specification.
752 </p>
754 <h3 id="fragment-styling">Fragment styling</h3>
756 <h4 id="fragment-pseudo-element">The ::nth-fragment() pseudo-element</h4>
758 <p>
759 The ::nth-fragment() pseudo-element is a pseudo-element
760 that describes some of the <i>fragment box</i>es generated by an element.
761 The argument to the pseudo-element takes the same syntax
762 as the argument to the :nth-child() pseudo-class
763 defined in [[!SELECT]], and has the same meaning
764 except that the number is relative to
765 <i>fragment box</i>es generated by the element
766 instead of siblings of the element.
767 </p>
769 <p class="note">
770 Selectors that allow addressing fragments
771 by counting from the end rather than the start
772 are intentionally not provided.
773 Such selectors would interfere with determining
774 the number of fragments.
775 </p>
777 <p class="issue">
778 Depending on future discussions,
779 this ''::nth-fragment(<var>an+b</var>)'' syntax
780 may be replaced with
781 the new ''::fragment:nth(<var>an+b</var>)'' syntax.
782 </p>
784 <h4 id="style-of-fragments">Styling of fragments</h4>
786 <p class="issue">
787 Should this apply to fragment overflow only,
788 or also to paginated overflow?
789 (If it applies,
790 then stricter property restrictions would be needed
791 for paginated overflow.)
792 </p>
794 <p>
795 In the absence of rules with ''::nth-fragment()'' pseudo-elements,
796 the computed style for each <i>fragment box</i>
797 is the computed style for the element
798 for which the <i>fragment box</i> was created.
799 However, the style for a <i>fragment box</i> is also influenced
800 by rules whose selector's <i>subject</i> [[!SELECT]]
801 has an ''::nth-fragment()'' pseudo-element,
802 if the 1-based number of the <i>fragment box</i> matches
803 that ''::nth-fragment()'' pseudo-element
804 and the selector (excluding the ''::nth-fragment()'' pseudo-element)
805 matches the element generating the fragments.
806 </p>
808 <p>
809 When determining the style of the <i>fragment box</i>,
810 these rules that match the fragment pseudo-element
811 cascade together with the rules that match the element,
812 with the fragment pseudo-element adding the specificity
813 of a pseudo-class to the specificity calculation.
814 <span class="issue">Does this need to be specified in
815 the cascading module as well?</span>
816 </p>
818 <div class="example">
819 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML>
820 <style>
821 .bouncy-columns {
822 overflow: fragments;
823 width: 6em;
824 height: 10em;
825 float: left;
826 margin: 1em;
827 font: medium/1.25 Times New
828 Roman, Times, serif;
829 }
830 .bouncy-columns::nth-fragment(1) {
831 background: aqua; color: black;
832 transform: rotate(-3deg);
833 }
834 .bouncy-columns::nth-fragment(2) {
835 background: yellow; color: black;
836 transform: rotate(3deg);
837 }
838 </style>
839 <div class="bouncy-columns">
840 <i>...</i>
841 </div></pre></td><td>
842 <div class="bouncy-columns-demo one">In this<br>example, the<br>text in the div<br>is broken into<br>a series of<br>columns. The<br>author<br>probably</div>
843 <div class="bouncy-columns-demo two">intended the<br>text to fill two<br>columns. But<br>if it happens to<br>fill three<br>columns, the<br>third column is<br>still created. It</div>
844 <div class="bouncy-columns-demo">just doesn't<br>have any<br>fragment-specific<br>styling because<br>the author<br>didn't give it<br>any.</div>
845 </td></tr></table>
846 </div>
848 <p>
849 Styling an ''::nth-fragment()'' pseudo-element with the 'overflow'
850 property does take effect;
851 if a <i>fragment box</i> has a
852 computed value of 'overflow' other than ''fragments''
853 then that fragment box is the last fragment.
854 However, overriding ''overflow'' on the first fragment
855 does not cause the <i>fragment box</i> not to exist;
856 whether there are fragment boxes at all is determined by
857 the computed value of overflow for the element.
858 <span class="issue">Need to reword this to refer to the
859 appropriate choice of ''overflow-x'' or ''overflow-y'',
860 and then point to rule about the handling of the other one
861 of ''overflow-x'' or ''overflow-y''.</span>
862 </p>
864 <p>
865 Styling an ''::nth-fragment()'' pseudo-element with the 'content'
866 property has no effect;
867 the computed value of 'content' for the fragment box
868 remains the same as the computed value of content for the element.
869 </p>
871 <p>
872 Specifying ''display: none'' for a <i>fragment box</i> causes
873 the fragment box with that index not to be generated.
874 However, in terms of the indices
875 used for matching ''::nth-fragment()'' pseudo-elements
876 of later fragment boxes,
877 it still counts as though it was generated.
878 However, since it is not generated, it does not contain any content.
879 </p>
881 <p>
882 Specifying other values of 'display', 'position',
883 or 'float' is permitted, but is not allowed to change
884 the computed value of 'display-inside'.
885 (Since 'overflow', 'overflow-x', and 'overflow-y' only
886 apply to block containers, flex containers, and grid containers
887 the computed value of 'display-inside' is always
888 ''block'', ''flex'' or ''grid''.
889 <span class="issue">Need to specify exactly how this works,
890 but it depends on
891 having 'display-inside' and 'display-outside' specified.</span>
892 </p>
894 <p>
895 To match the model for other pseudo-elements
896 where the pseudo-elements live inside their corresponding element,
897 declarations in ''::nth-fragment()'' pseudo-elements override
898 declarations in rules without the pseudo-element.
899 The relative priority within such declarations is determined
900 by normal cascading order (see [[!CSS21]]).
901 </p>
903 <p>
904 Styles specified on ''::nth-fragment()'' pseudo-elements
905 do affect inheritance to content within the <i>fragment box</i>.
906 In other words, the content within the <i>fragment box</i> must
907 inherit from the fragment box's style (i.e., the pseudo-element style)
908 rather than directly from the element.
909 This means that elements split between fragment boxes may
910 have different styles for different parts of the element.
911 </p>
913 <p class="issue">
914 This inheritance rule allows specifying styles indirectly
915 (by using explicit ''inherit'' or using default inheritance
916 on properties that don't apply to '':first-letter'')
917 that can't be specified directly
918 (based on the rules in the next section).
919 This is a problem.
920 The restrictions that apply to styling inside fragments
921 should also apply to inheritance from fragments.
922 </p>
924 <div class="example">
925 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML>
926 <style>
927 .article {
928 overflow: fragments;
929 }
930 .article::nth-fragment(1) {
931 font-size: 1.5em;
932 margin-bottom: 1em;
933 height: 4em;
934 }
935 .article::nth-fragment(2) {
936 margin-left: 5em;
937 margin-right: 2em;
938 }
939 </style>
940 <div class="article">
941 The <code>font-size</code> property<i>...</i>
942 </div></pre></td><td>
943 <div class="article-font-inherit-demo one">The <code>font-size</code> property<br>specified on the fragment<br>is inherited into the</div>
944 <div class="article-font-inherit-demo two">descendants of the fragment.<br>This means that inherited<br>properties can be used<br>reliably on a fragment, as in<br>this example.</div>
945 </td></tr></table>
946 </div>
948 <h4 id="style-in-fragments">Styling inside fragments</h4>
950 <p class="issue">
951 Should this apply to fragment overflow only,
952 or also to paginated overflow,
953 or even to pagination across pages?
954 </p>
956 <p>
957 The ''::nth-fragment()'' pseudo-element
958 can also be used to style
959 content inside of a <i>fragment box</i>.
960 Unlike the ''::first-line'' and ''::first-letter'' pseudo-elements,
961 the ''::nth-fragment()'' pseudo-element can be applied
962 to parts of the selector other than the subject:
963 in particular, it can match ancestors of the subject.
964 However, the only CSS properties applied
965 by rules with such selectors
966 are those that apply
967 to the ''::first-letter'' pseudo-element.
968 </p>
970 <p>
971 To be more precise,
972 when a rule's selector has ''::nth-fragment()'' pseudo-elements
973 attached to parts of the selector other than the subject,
974 the declarations in that rule apply to
975 a fragment (or pseudo-element thereof) when:
976 </p>
977 <ol>
978 <li>
979 the declarations are for properties that apply to the
980 ''::first-letter'' pseudo-element,
981 </li>
982 <li>
983 the declarations would apply to
984 that fragment (or pseudo-element thereof)
985 had those ''::nth-fragment()'' pseudo-elements been removed,
986 with a particular association between
987 each sequence of simple selectors and the element it matched,
988 and
989 </li>
990 <li>
991 for each removed ''::nth-fragment()'' pseudo-element,
992 the fragment lives within a <i>fragment box</i>
993 of the element associated in that association
994 with the selector that the pseudo-element was attached to,
995 and whose index matches the pseudo-element.
996 </li>
997 </ol>
999 <div class="example">
1000 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML>
1001 <style>
1002 .dark-columns {
1003 overflow: fragments;
1004 width: 6em;
1005 height: 10em;
1006 float: left;
1007 margin-right: 1em;
1008 font: medium/1.25 Times New
1009 Roman, Times, serif;
1010 }
1011 .dark-columns::nth-fragment(1) {
1012 background: aqua; color: black;
1013 }
1014 .dark-columns::nth-fragment(1) :link {
1015 color: blue;
1016 }
1017 .dark-columns::nth-fragment(1) :visited {
1018 color: purple;
1019 }
1020 .dark-columns::nth-fragment(2) {
1021 background: navy; color: white;
1022 }
1023 .dark-columns::nth-fragment(2) :link {
1024 color: aqua;
1025 }
1026 .dark-columns::nth-fragment(2) :visited {
1027 color: fuchsia;
1028 }
1029 </style>
1030 <div class="dark-columns">
1031 <i>...</i>
1032 </div></pre></td><td>
1033 <div class="dark-columns-demo one">In this<br><a href="http://en.wiktionary.org/wiki/example">example</a>, the<br>text flows<br>from one<br>light-colored<br>fragment into<br>another<br>dark-colored</div>
1034 <div class="dark-columns-demo two">fragment. We<br>therefore want<br>different styles<br>for <a href="http://www.w3.org/Provider/Style/IntoContext.html">hyperlinks</a><br>in the different<br>fragments.</div>
1035 </td></tr></table>
1036 </div>
1039 <h3 id="max-lines">The 'max-lines' property</h3>
1041 <p>
1042 Authors may wish to style the opening lines of an element
1043 with different styles
1044 by putting those opening lines in a separate fragment.
1045 However, since it may be difficult to predict the exact height
1046 occupied by those lines
1047 in order to restrict the first fragment to that height,
1048 this specification introduces a 'max-lines' property
1049 that forces a fragment to break
1050 after a specified number of lines.
1051 This forces a break after the given number of lines
1052 contained within the element or its descendants,
1053 as long as those lines are in the same block formatting context.
1054 </p>
1056 <table class=propdef>
1057 <tr>
1058 <th>Name:
1059 <td><dfn>max-lines</dfn>
1060 <tr>
1061 <th><a href="#values">Value</a>:
1062 <td>none | <integer>
1063 <tr>
1064 <th>Initial:
1065 <td>none
1066 <tr>
1067 <th>Applies to:
1068 <td>fragment boxes
1069 <tr>
1070 <th>Inherited:
1071 <td>no
1072 <tr>
1073 <th>Animatable:
1074 <td>as <a href="http://www.w3.org/TR/css3-transitions/#animatable-types">integer</a>
1075 <tr>
1076 <th>Percentages:
1077 <td>N/A
1078 <tr>
1079 <th>Media:
1080 <td>visual
1081 <tr>
1082 <th>Computed value:
1083 <td>specified value
1084 <tr>
1085 <th>Canonical order:
1086 <td><abbr title="follows order of property value definition">per grammar</abbr>
1087 </table>
1089 <dl>
1090 <dt>none
1091 <dd>
1092 <p>
1093 Breaks occur only as specified elsewhere.
1094 </p>
1095 </dd>
1097 <dt><integer>
1098 <dd>
1099 <p>
1100 In addition to any breaks specified elsewhere,
1101 a break is forced before any line that would exceed
1102 the given number of lines
1103 being placed inside the element
1104 (excluding lines that are in
1105 a different block formatting context from
1106 the block formatting context to which
1107 an unstyled child of the element would belong).
1108 </p>
1110 <p class="issue">
1111 If there are multiple boundaries between this line
1112 and the previous, where exactly (in terms of element
1113 boundaries) is the break forced?
1114 </p>
1116 <p>
1117 Only positive integers are accepted.
1118 Zero or negative integers are a parse error.
1119 </p>
1120 </dd>
1121 </dl>
1123 <p class="issue">Should this apply to fragment overflow only, or also
1124 to pagination?</p>
1126 <div class="example">
1127 <table class="source-demo-pair"><tr><td><pre><!DOCTYPE HTML>
1128 <style>
1129 .article {
1130 overflow: fragments;
1131 }
1132 .article::first-letter {
1133 font-size: 2em;
1134 line-height: 0.9;
1135 }
1136 .article::nth-fragment(1) {
1137 font-size: 1.5em;
1138 max-lines: 3;
1139 }
1140 .article::nth-fragment(2) {
1141 column-count: 2;
1142 }
1143 </style>
1144 <div class="article">
1145 <i>...</i>
1146 </div></pre></td><td>
1147 <div class="article-max-lines-demo one">The max-lines property allows<br>authors to use a larger font for the first<br>few lines of an article. Without the</div>
1148 <div class="article-max-lines-demo two">max-lines property, authors<br>might have to use the<br>'height' property instead, but<br>that would leave a slight gap<br>if the author miscalculated<br>how much height a given<br>number of lines would<br>occupy (which might be</div>
1149 <div class="article-max-lines-demo three">particularly hard if the author<br>didn't know what text would<br>be filling the space, exactly<br>what font would be used, or<br>exactly which platform's font<br>rendering would be used to<br>display the font).</div>
1150 </td></tr></table>
1151 </div>
1153 <h2 id="static-media">Overflow in static media</h2>
1155 <p class="issue">
1156 This specification should define useful behavior
1157 for all values of 'overflow'
1158 in static media (such as print).
1159 Current implementation behavior is quite poor and
1160 produces unexpected results when authors have not considered
1161 what will happen when
1162 the content they produce for interactive media
1163 is printed.
1164 </p>
1166 <h2 id="conformance">
1167 Conformance</h2>
1169 <h3 id="placement">
1170 Module interactions</h3>
1172 <p>This module extends the 'overflow'
1173 feature defined in [[CSS21]] section 11.1.1. It defines additional
1174 overflow handling mechanisms that implementations must implement as
1175 described in this module in order to conform to this module.</p>
1177 <p>No properties in this module apply to the <code>::first-line</code> or
1178 <code>::first-letter</code> pseudo-elements.</p>
1180 <h3 id="values">
1181 Values</h3>
1183 <p>This specification follows the
1184 <a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
1185 definition conventions</a> from [[!CSS21]]. Value types not defined in
1186 this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
1187 Other CSS modules may expand the definitions of these value types: for
1188 example [[CSS3COLOR]], when combined with this module, expands the
1189 definition of the <color> value type as used in this specification.</p>
1191 <p>In addition to the property-specific values listed in their definitions,
1192 all properties defined in this specification also accept the
1193 <a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
1194 keyword as their property value. For readability it has not been repeated
1195 explicitly.
1198 <h3 id="conventions">
1199 Document conventions</h3>
1201 <p>Conformance requirements are expressed with a combination of
1202 descriptive assertions and RFC 2119 terminology. The key words “MUST”,
1203 “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
1204 “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
1205 document are to be interpreted as described in RFC 2119.
1206 However, for readability, these words do not appear in all uppercase
1207 letters in this specification.
1209 <p>All of the text of this specification is normative except sections
1210 explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
1212 <p>Examples in this specification are introduced with the words “for example”
1213 or are set apart from the normative text with <code>class="example"</code>,
1214 like this:
1216 <div class="example">
1217 <p>This is an example of an informative example.</p>
1218 </div>
1220 <p>Informative notes begin with the word “Note” and are set apart from the
1221 normative text with <code>class="note"</code>, like this:
1223 <p class="note">Note, this is an informative note.</p>
1225 <h3 id="conformance-classes">
1226 Conformance classes</h3>
1228 <p>Conformance to CSS Overflow Module Level 3
1229 is defined for three conformance classes:
1230 <dl>
1231 <dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
1232 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
1233 style sheet</a>.
1234 <dt><dfn>renderer</dfn></dt>
1235 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
1236 that interprets the semantics of a style sheet and renders
1237 documents that use them.
1238 <dt><dfn id="authoring-tool">authoring tool</dfn></dt>
1239 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
1240 that writes a style sheet.
1241 </dl>
1243 <p>A style sheet is conformant to CSS Overflow Module Level 3
1244 if all of its statements that use syntax defined in this module are valid
1245 according to the generic CSS grammar and the individual grammars of each
1246 feature defined in this module.
1248 <p>A renderer is conformant to CSS Overflow Module Level 3
1249 if, in addition to interpreting the style sheet as defined by the
1250 appropriate specifications, it supports all the features defined
1251 by CSS Overflow Module Level 3 by parsing them correctly
1252 and rendering the document accordingly. However, the inability of a
1253 UA to correctly render a document due to limitations of the device
1254 does not make the UA non-conformant. (For example, a UA is not
1255 required to render color on a monochrome monitor.)
1257 <p>An authoring tool is conformant to CSS Overflow Module Level 3
1258 if it writes style sheets that are syntactically correct according to the
1259 generic CSS grammar and the individual grammars of each feature in
1260 this module, and meet all other conformance requirements of style sheets
1261 as described in this module.
1263 <h3 id="partial">
1264 Partial implementations</h3>
1266 <p>So that authors can exploit the forward-compatible parsing rules to
1267 assign fallback values, CSS renderers <strong>must</strong>
1268 treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
1269 as appropriate</a>) any at-rules, properties, property values, keywords,
1270 and other syntactic constructs for which they have no usable level of
1271 support. In particular, user agents <strong>must not</strong> selectively
1272 ignore unsupported component values and honor supported values in a single
1273 multi-value property declaration: if any value is considered invalid
1274 (as unsupported values must be), CSS requires that the entire declaration
1275 be ignored.</p>
1277 <h3 id="experimental">
1278 Experimental implementations</h3>
1280 <p>To avoid clashes with future CSS features, the CSS2.1 specification
1281 reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
1282 syntax</a> for proprietary and experimental extensions to CSS.
1284 <p>Prior to a specification reaching the Candidate Recommendation stage
1285 in the W3C process, all implementations of a CSS feature are considered
1286 experimental. The CSS Working Group recommends that implementations
1287 use a vendor-prefixed syntax for such features, including those in
1288 W3C Working Drafts. This avoids incompatibilities with future changes
1289 in the draft.
1290 </p>
1292 <h3 id="testing">
1293 Non-experimental implementations</h3>
1295 <p>Once a specification reaches the Candidate Recommendation stage,
1296 non-experimental implementations are possible, and implementors should
1297 release an unprefixed implementation of any CR-level feature they
1298 can demonstrate to be correctly implemented according to spec.
1300 <p>To establish and maintain the interoperability of CSS across
1301 implementations, the CSS Working Group requests that non-experimental
1302 CSS renderers submit an implementation report (and, if necessary, the
1303 testcases used for that implementation report) to the W3C before
1304 releasing an unprefixed implementation of any CSS features. Testcases
1305 submitted to W3C are subject to review and correction by the CSS
1306 Working Group.
1308 <p>Further information on submitting testcases and implementation reports
1309 can be found from on the CSS Working Group's website at
1310 <a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
1311 Questions should be directed to the
1312 <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
1313 mailing list.
1315 <h3 id="cr-exit-criteria">
1316 CR exit criteria</h3>
1318 <p class=issue>[Change or remove the following CR exit criteria if
1319 the spec is not a module, but, e.g., a Note or a profile. This text was <a
1320 href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on 2008-06-04.</a>]</p>
1322 <p>
1323 For this specification to be advanced to Proposed Recommendation,
1324 there must be at least two independent, interoperable implementations
1325 of each feature. Each feature may be implemented by a different set of
1326 products, there is no requirement that all features be implemented by
1327 a single product. For the purposes of this criterion, we define the
1328 following terms:
1330 <dl>
1331 <dt>independent <dd>each implementation must be developed by a
1332 different party and cannot share, reuse, or derive from code
1333 used by another qualifying implementation. Sections of code that
1334 have no bearing on the implementation of this specification are
1335 exempt from this requirement.
1337 <dt>interoperable <dd>passing the respective test case(s) in the
1338 official CSS test suite, or, if the implementation is not a Web
1339 browser, an equivalent test. Every relevant test in the test
1340 suite should have an equivalent test created if such a user
1341 agent (UA) is to be used to claim interoperability. In addition
1342 if such a UA is to be used to claim interoperability, then there
1343 must one or more additional UAs which can also pass those
1344 equivalent tests in the same way for the purpose of
1345 interoperability. The equivalent tests must be made publicly
1346 available for the purposes of peer review.
1348 <dt>implementation <dd>a user agent which:
1350 <ol class=inline>
1351 <li>implements the specification.
1353 <li>is available to the general public. The implementation may
1354 be a shipping product or other publicly available version
1355 (i.e., beta version, preview release, or “nightly build”).
1356 Non-shipping product releases must have implemented the
1357 feature(s) for a period of at least one month in order to
1358 demonstrate stability.
1360 <li>is not experimental (i.e., a version specifically designed
1361 to pass the test suite and is not intended for normal usage
1362 going forward).
1363 </ol>
1364 </dl>
1366 <p>The specification will remain Candidate Recommendation for at least
1367 six months.
1369 <h2 class=no-num id="acknowledgments">
1370 Acknowledgments</h2>
1372 <p>
1373 Thanks especially to the feedback from
1374 Rossen Atanassov,
1375 Bert Bos,
1376 Tantek Çelik,
1377 John Daggett,
1378 fantasai,
1379 Daniel Glazman,
1380 Vincent Hardy,
1381 Håkon Wium Lie,
1382 Peter Linss,
1383 Robert O'Callahan,
1384 Florian Rivoal,
1385 Alan Stearns,
1386 Steve Zilles,
1387 and all the rest of the
1388 <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> community.
1389 </p>
1391 <h2 class=no-num id="references">
1392 References</h2>
1394 <h3 class="no-num" id="normative-references">
1395 Normative references</h3>
1396 <!--normative-->
1398 <h3 class="no-num" id="other-references">
1399 Other references</h3>
1400 <!--informative-->
1402 <h2 class="no-num" id="index">
1403 Index</h2>
1404 <!--index-->
1406 <h2 class="no-num" id="property-index">
1407 Property index</h2>
1408 <!-- properties -->
1410 </body>
1411 </html>
1412 <!-- Keep this comment at the end of the file
1413 Local variables:
1414 mode: sgml
1415 sgml-declaration:"~/SGML/HTML4.decl"
1416 sgml-default-doctype-name:"html"
1417 sgml-minimize-attributes:t
1418 sgml-nofill-elements:("pre" "style" "br")
1419 sgml-live-element-indicator:t
1420 sgml-omittag:nil
1421 sgml-shorttag:nil
1422 sgml-namecase-general:t
1423 sgml-general-insert-case:lower
1424 sgml-always-quote-attributes:t
1425 sgml-indent-step:nil
1426 sgml-indent-data:t
1427 sgml-parent-document:nil
1428 sgml-exposed-tags:nil
1429 sgml-local-catalogs:nil
1430 sgml-local-ecat-files:nil
1431 End:
1432 -->
