css3-overflow/Overview.src.html

Thu, 16 Aug 2012 14:25:11 -0700

author
L. David Baron <dbaron@dbaron.org>
date
Thu, 16 Aug 2012 14:25:11 -0700
changeset 6483
ce35838cba90
parent 6482
dd34855b9279
child 6484
4f00e14a11d4
permissions
-rw-r--r--

Rename module per discussion at 2012-08-08 teleconference and at F2F on afternoon of 2012-08-13.

dbaron@6470 1 <!DOCTYPE html>
dbaron@6470 2 <html lang="en">
dbaron@6470 3 <head>
dbaron@6470 4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
dbaron@6483 5 <title>CSS Overflow Module Level 3</title>
dbaron@6470 6 <link rel=contents href="#contents">
dbaron@6470 7 <link rel=index href="#index">
dbaron@6470 8 <link rel="stylesheet" type="text/css" href="../default.css">
dbaron@6470 9 <link rel="stylesheet" type="text/css"
dbaron@6470 10 href="http://www.w3.org/StyleSheets/TR/W3C-[STATUS].css">
dbaron@6475 11 <style>
dbaron@6477 12 table.source-demo-pair {
dbaron@6477 13 width: 100%;
dbaron@6477 14 }
dbaron@6481 15
dbaron@6475 16 .in-cards-demo {
dbaron@6475 17 width: 13em;
dbaron@6475 18 height: 8em;
dbaron@6475 19
dbaron@6475 20 padding: 4px;
dbaron@6475 21 border: medium solid blue;
dbaron@6475 22 margin: 6px;
dbaron@6475 23
dbaron@6475 24 font: medium/1.3 Times New Roman, Times, serif;
dbaron@6475 25 white-space: nowrap;
dbaron@6475 26 }
dbaron@6481 27
dbaron@6477 28 .bouncy-columns-demo {
dbaron@6477 29 width: 6em;
dbaron@6477 30 height: 10em;
dbaron@6477 31 float: left;
dbaron@6477 32 margin: 1em;
dbaron@6477 33 font: medium/1.25 Times New Roman, Times, serif;
dbaron@6477 34 white-space: nowrap;
dbaron@6477 35 }
dbaron@6477 36 .bouncy-columns-demo.one {
dbaron@6477 37 background: aqua; color: black;
dbaron@6477 38 transform: rotate(-3deg);
dbaron@6477 39 }
dbaron@6477 40 .bouncy-columns-demo.two {
dbaron@6477 41 background: yellow; color: black;
dbaron@6477 42 transform: rotate(3deg);
dbaron@6477 43 }
dbaron@6479 44
dbaron@6480 45 .article-font-inherit-demo {
dbaron@6480 46 font: 1em/1.25 Times New Roman, Times, serif;
dbaron@6480 47 white-space: nowrap;
dbaron@6480 48 }
dbaron@6480 49 .article-font-inherit-demo.one {
dbaron@6480 50 width: 12em;
dbaron@6480 51 font-size: 1.5em;
dbaron@6480 52 margin-bottom: 1em;
dbaron@6480 53 height: 4em;
dbaron@6480 54 }
dbaron@6480 55 .article-font-inherit-demo.two {
dbaron@6480 56 width: 11em;
dbaron@6480 57 margin-left: 5em;
dbaron@6480 58 margin-right: 2em;
dbaron@6480 59 }
dbaron@6480 60
dbaron@6481 61 .dark-columns-demo {
dbaron@6481 62 width: 6em;
dbaron@6481 63 height: 10em;
dbaron@6481 64 float: left;
dbaron@6481 65 margin-right: 1em;
dbaron@6481 66 font: medium/1.25 Times New Roman, Times, serif;
dbaron@6481 67 white-space: nowrap;
dbaron@6481 68 }
dbaron@6481 69 .dark-columns-demo.one {
dbaron@6481 70 background: aqua; color: black;
dbaron@6481 71 }
dbaron@6481 72 .dark-columns-demo.one :link {
dbaron@6481 73 color: blue;
dbaron@6481 74 }
dbaron@6481 75 .dark-columns-demo.one :visited {
dbaron@6481 76 color: purple;
dbaron@6481 77 }
dbaron@6481 78 .dark-columns-demo.two {
dbaron@6481 79 background: navy; color: white;
dbaron@6481 80 }
dbaron@6481 81 .dark-columns-demo.two :link {
dbaron@6481 82 color: aqua;
dbaron@6481 83 }
dbaron@6481 84 .dark-columns-demo.two :visited {
dbaron@6481 85 color: fuchsia;
dbaron@6481 86 }
dbaron@6481 87
dbaron@6479 88 .article-max-lines-demo {
dbaron@6479 89 font: 1em/1.25 Times New Roman, Times, serif;
dbaron@6479 90 white-space: nowrap;
dbaron@6479 91 }
dbaron@6479 92 .article-max-lines-demo.one::first-letter {
dbaron@6479 93 font-size: 2em;
dbaron@6479 94 line-height: 0.9;
dbaron@6479 95 }
dbaron@6479 96 .article-max-lines-demo.one {
dbaron@6479 97 font-size: 1.5em;
dbaron@6479 98 width: 16em;
dbaron@6479 99 }
dbaron@6479 100 .article-max-lines-demo.two {
dbaron@6479 101 width: 11.5em;
dbaron@6479 102 float: left; margin-right: 1em;
dbaron@6479 103 }
dbaron@6479 104 .article-max-lines-demo.three {
dbaron@6479 105 width: 11.5em;
dbaron@6479 106 float: left;
dbaron@6479 107 }
dbaron@6475 108 </style>
dbaron@6470 109 </head>
dbaron@6470 110
dbaron@6470 111 <div class="head">
dbaron@6470 112 <!--logo-->
dbaron@6470 113
dbaron@6483 114 <h1>CSS Overflow Module Level 3</h1>
dbaron@6470 115
dbaron@6470 116 <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
dbaron@6470 117 <dl>
dbaron@6470 118 <dt>This version:
dbaron@6483 119 <dd><a href="[VERSION]">http://www.w3.org/TR/[YEAR]/ED-css3-overflow-[CDATE]/</a>
dbaron@6470 120
dbaron@6470 121 <dt>Latest version:
dbaron@6470 122 <dd><a href="http://www.w3.org/TR/[SHORTNAME]/">http://www.w3.org/TR/[SHORTNAME]/</a>
dbaron@6470 123
dbaron@6470 124 <dt>Editor's draft:
dbaron@6470 125 <dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">http://dev.w3.org/csswg/[SHORTNAME]/</a>
dbaron@6470 126
dbaron@6470 127 <!--
dbaron@6470 128 <dt>Previous version:
dbaron@6470 129 <dd><a href="http://www.w3.org/PreviousVersionURI">
dbaron@6470 130 http://www.w3.org/PreviousVersionURI</a>
dbaron@6470 131 -->
dbaron@6470 132
dbaron@6470 133 <dt>Issue Tracking:</dt>
dbaron@6470 134 <dd>Maintained in document (only editor's draft is current)
dbaron@6470 135
dbaron@6470 136 <dt>Feedback:</dt>
dbaron@6470 137 <dd><a href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a> with subject line &ldquo;<kbd>[[SHORTNAME]] <var>&hellip; message topic &hellip;</var></kbd>&rdquo;
dbaron@6470 138
dbaron@6470 139 <dt>Editors:
dbaron@6470 140 <dd class="h-card vcard">
dbaron@6470 141 <a class="p-name fn u-url url" rel="author"
dbaron@6470 142 href="http://dbaron.org/">L. David Baron</a>,
dbaron@6470 143 <a class="p-org org" href="http://www.mozilla.org/">Mozilla</a>
dbaron@6470 144 </dl>
dbaron@6470 145
dbaron@6470 146 <!--copyright-->
dbaron@6470 147
dbaron@6470 148 <hr title="Separator for header">
dbaron@6470 149 </div>
dbaron@6470 150
dbaron@6470 151 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
dbaron@6470 152
dbaron@6470 153 <p>
dbaron@6470 154 <a href="http://www.w3.org/TR/CSS/">CSS</a> is
dbaron@6470 155 a language for describing
dbaron@6470 156 the rendering of structured documents (such as HTML and XML)
dbaron@6470 157 on screen, on paper, in speech, etc.
dbaron@6470 158 This module contains the features of CSS
dbaron@6470 159 relating to new mechanisms of overflow handling in visual media (e.g., screen or paper).
dbaron@6470 160 In interactive media,
dbaron@6470 161 it describes features that allow the overflow
dbaron@6470 162 from a fixed size container
dbaron@6470 163 to be handled by pagination (displaying one page at a time).
dbaron@6470 164 It also describes features, applying to all visual media,
dbaron@6470 165 that allow the contents of an element
dbaron@6470 166 to be spread across multiple containers,
dbaron@6470 167 allowing the contents to flow across multiple regions of a page
dbaron@6470 168 or to have different styles for different parts.
dbaron@6470 169 </p>
dbaron@6470 170
dbaron@6470 171 <h2 class="no-num no-toc" id="status">Status of this document</h2>
dbaron@6470 172
dbaron@6470 173 <!--status-->
dbaron@6470 174
dbaron@6470 175 <p>The following features are at risk: &hellip;
dbaron@6470 176
dbaron@6470 177 <h2 class="no-num no-toc" id="contents">
dbaron@6470 178 Table of contents</h2>
dbaron@6470 179
dbaron@6470 180 <!--toc-->
dbaron@6470 181
dbaron@6470 182 <h2 id="intro">
dbaron@6470 183 Introduction</h2>
dbaron@6470 184
dbaron@6470 185 <p>
dbaron@6470 186 In CSS Level 1 [[CSS1]], placing more content than would fit
dbaron@6470 187 inside an element with a specified size
dbaron@6470 188 was generally an authoring error.
dbaron@6470 189 Doing so caused the content to extend
dbaron@6470 190 outside the bounds of the element,
dbaron@6470 191 which would likely cause
dbaron@6470 192 that content to overlap with other elements.
dbaron@6470 193 </p>
dbaron@6470 194
dbaron@6470 195 <p>
dbaron@6470 196 CSS Level 2 [[CSS21]] introduced the 'overflow' property,
dbaron@6470 197 which allows authors to have overflow be handled by scrolling,
dbaron@6470 198 which means it is no longer an authoring error.
dbaron@6470 199 It also allows authors to specify
dbaron@6470 200 that overflow is handled by clipping,
dbaron@6470 201 which makes sense when the author's intent
dbaron@6470 202 is that the content not be shown.
dbaron@6470 203 </p>
dbaron@6470 204
dbaron@6470 205 <p>
dbaron@6470 206 However, scrolling is not the only way
dbaron@6470 207 to present large amounts of content,
dbaron@6470 208 and may even not be the optimal way.
dbaron@6470 209 After all, the codex replaced the scroll
dbaron@6470 210 as the common format for large written works
dbaron@6470 211 because of its advantages.
dbaron@6470 212 </p>
dbaron@6470 213
dbaron@6470 214 <p>
dbaron@6470 215 This specification introduces
dbaron@6470 216 a mechanism for Web pages to specify
dbaron@6470 217 that a region of a page should handle overflow
dbaron@6470 218 through pagination rather than through scrolling.
dbaron@6470 219 </p>
dbaron@6470 220
dbaron@6470 221 <p>
dbaron@6470 222 This specification also extends the concept of overflow
dbaron@6470 223 in another direction.
dbaron@6470 224 Instead of requiring that authors specify a single region
dbaron@6470 225 into which the content of an element must flow,
dbaron@6470 226 this specification allows authors to specify multiple regions,
dbaron@6470 227 each with their own dimensions and styles,
dbaron@6470 228 so that the content of the element can flow from one to the next,
dbaron@6470 229 using as many as needed to place the content without overflowing.
dbaron@6470 230 </p>
dbaron@6470 231
dbaron@6470 232 <p>
dbaron@6470 233 In both of these cases, implementations must
dbaron@6470 234 break the content in the block-progression dimension.
dbaron@6470 235 Implementations must do this is described
dbaron@6470 236 in the CSS Fragmentation Module [[!CSS3-BREAK]].
dbaron@6470 237 </p>
dbaron@6470 238
dbaron@6483 239 <h2 id="scrolling-overflow">Scrolling and hidden overflow</h2>
dbaron@6483 240
dbaron@6483 241 <p class="issue">
dbaron@6483 242 Move material from [[CSS21]] and [[CSS3BOX]] here.
dbaron@6483 243 </p>
dbaron@6470 244
dbaron@6470 245 <h2 id="paginated-overflow">Paginated overflow</h2>
dbaron@6470 246
dbaron@6470 247 <p class="issue">overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as css3-gcpm has?)</p>
dbaron@6470 248
dbaron@6470 249 <p class="issue">Ability to display N pages at once
dbaron@6470 250 rather than just one page at once?</p>
dbaron@6470 251
dbaron@6470 252 <h2 id="region-overflow">Region overflow</h2>
dbaron@6470 253
dbaron@6470 254 <p>
dbaron@6470 255 This section introduces and defines the meaning of
dbaron@6470 256 the new ''regions'' (<span class="issue">or ''repeat''?</span>)
dbaron@6470 257 value of the 'overflow' property.
dbaron@6470 258 </p>
dbaron@6470 259
dbaron@6470 260 <p>
dbaron@6470 261 When the computed value of 'overflow' for an element is ''regions'',
dbaron@6470 262 and implementations would otherwise have created a box for the element,
dbaron@6470 263 then implementations must create at least one box for that element.
dbaron@6470 264 Each box created for the element is called a <dfn>region box</dfn>
dbaron@6470 265 for that element.
dbaron@6470 266 (If an element with ''overflow: regions'' generates only one box,
dbaron@6470 267 that box is a <i>region box</i>.
dbaron@6470 268 However, if an element's computed 'overflow' is not ''regions'',
dbaron@6470 269 then its box is not a <i>region box</i>.)
dbaron@6470 270 Every <i>region box</i> is a fragmentation container,
dbaron@6471 271 and for each <i>region box</i> which ends with a fragmentation break,
dbaron@6471 272 (which could happen
dbaron@6471 273 because breakable content overflows in the block dimension
dbaron@6471 274 or because of a forced break),
dbaron@6470 275 there must be another <i>region box</i> created as a next sibling
dbaron@6470 276 of the previous one.
dbaron@6470 277 <span class="issue">Or is it as though it's a next sibling of
dbaron@6470 278 the element? Need to figure out exactly how this interacts with
dbaron@6470 279 other box-level fixup.</span>
dbaron@6470 280 (Breakable content might overflow in the box dimension either
dbaron@6470 281 because of a specified size on the region box
dbaron@6470 282 or because the region box is within a fragmentation context
dbaron@6470 283 in which it is being broken.
dbaron@6470 284 In other words, a single region box is never broken
dbaron@6470 285 across columns or pages;
dbaron@6470 286 the pieces that are in separate columns or pages
dbaron@6470 287 are always distinct region boxes.)
dbaron@6470 288 </p>
dbaron@6470 289
dbaron@6470 290 <p class="issue">
dbaron@6476 291 We also want ''::nth-region()'' pseudo-elements
dbaron@6470 292 to be able to apply to the pieces of an element
dbaron@6470 293 split within a fragmentation context.
dbaron@6470 294 Should we require that authors who want to use
dbaron@6476 295 ''::nth-region()'' in this way specify ''overflow:regions''
dbaron@6470 296 (even if they don't specify a constrained height),
dbaron@6470 297 or should it work automatically for all elements
dbaron@6470 298 even if they don't have ''overflow: regions''?
dbaron@6470 299 </p>
dbaron@6470 300
dbaron@6475 301 <div class="example">
dbaron@6477 302 <table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
dbaron@6475 303 &lt;title&gt;Breaking content into
dbaron@6475 304 equal-sized cards&lt;/title&gt;
dbaron@6475 305 &lt;style&gt;
dbaron@6475 306 .in-cards {
dbaron@6475 307 overflow: regions;
dbaron@6475 308
dbaron@6475 309 width: 13em;
dbaron@6475 310 height: 8em;
dbaron@6475 311
dbaron@6475 312 padding: 4px;
dbaron@6475 313 border: medium solid blue;
dbaron@6475 314 margin: 6px;
dbaron@6475 315
dbaron@6475 316 font: medium/1.3 Times New
dbaron@6475 317 Roman, Times, serif;
dbaron@6475 318 }
dbaron@6475 319 &lt;/style&gt;
dbaron@6475 320 &lt;div class="in-cards"&gt;
dbaron@6475 321 In this example, the text in the div
dbaron@6475 322 is broken into a series of cards.
dbaron@6475 323 These cards all have the same style.
dbaron@6475 324 The presence of enough content to
dbaron@6475 325 overflow one of the cards causes
dbaron@6475 326 another one to be created. The second
dbaron@6475 327 card is created just like it's the
dbaron@6475 328 next sibling of the first.
dbaron@6477 329 &lt;/div&gt;</pre></td><td>
dbaron@6475 330 <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>
dbaron@6475 331 <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>
dbaron@6475 332 </td></tr></table>
dbaron@6475 333 </div>
dbaron@6475 334
dbaron@6470 335 <h3 id="region-styling">Region styling</h3>
dbaron@6470 336
dbaron@6470 337 <h4 id="region-pseudo-element">The ::nth-region() pseudo-element</h4>
dbaron@6470 338
dbaron@6470 339 <p>
dbaron@6470 340 The ::nth-region() pseudo-element is a pseudo-element
dbaron@6470 341 that describes some of the region boxes generated by an element.
dbaron@6470 342 The argument to the pseudo-element takes the same syntax
dbaron@6470 343 as the argument to the :nth-child() pseudo-class
dbaron@6470 344 defined in [[!SELECT]], and has the same meaning
dbaron@6470 345 except that the number is relative to
dbaron@6470 346 <i>region boxes</i> generated by the element
dbaron@6470 347 instead of siblings of the element.
dbaron@6470 348 </p>
dbaron@6470 349
dbaron@6470 350 <p class="issue">
dbaron@6470 351 If we go with a name for the 'overflow' value other than
dbaron@6470 352 ''overflow: regions'',
dbaron@6470 353 then we should probably rename this pseudo-element,
dbaron@6470 354 perhaps to ::nth-piece(), ::nth-part(), or ::nth-instance().
dbaron@6470 355 </p>
dbaron@6470 356
dbaron@6470 357 <p class="note">
dbaron@6470 358 Selectors that allow addressing regions
dbaron@6470 359 by counting from the end rather than the start
dbaron@6470 360 are intentionally not provided.
dbaron@6470 361 Such selectors would interfere with determining
dbaron@6470 362 the number of regions.
dbaron@6470 363 </p>
dbaron@6470 364
dbaron@6470 365 <h4 id="style-of-regions">Styling of regions</h4>
dbaron@6470 366
dbaron@6470 367 <p class="issue">
dbaron@6470 368 Should this apply to region overflow only,
dbaron@6470 369 or also to paginated overflow?
dbaron@6470 370 (If it applies,
dbaron@6470 371 then stricter property restrictions would be needed
dbaron@6470 372 for paginated overflow.)
dbaron@6470 373 </p>
dbaron@6470 374
dbaron@6470 375 <p>
dbaron@6470 376 In the absence of rules with ''::nth-region()'' pseudo-elements,
dbaron@6470 377 the computed style for each <i>region box</i>
dbaron@6470 378 is the computed style for the element
dbaron@6470 379 for which the <i>region box</i> was created.
dbaron@6470 380 However, the style for a <i>region box</i> is also influenced
dbaron@6470 381 by rules whose selector's <i>subject</i> [[!SELECT]]
dbaron@6470 382 has an ''::nth-region()'' pseudo-element,
dbaron@6470 383 if the 1-based number of the region box matches
dbaron@6470 384 that ''::nth-region()'' pseudo-element
dbaron@6470 385 and the selector (excluding the ''::nth-region()'' pseudo-element)
dbaron@6470 386 matches the element generating the regions.
dbaron@6470 387 </p>
dbaron@6470 388
dbaron@6477 389 <div class="example">
dbaron@6477 390 <table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
dbaron@6477 391 &lt;style&gt;
dbaron@6477 392 .bouncy-columns {
dbaron@6477 393 overflow: regions;
dbaron@6477 394 width: 6em;
dbaron@6477 395 height: 10em;
dbaron@6477 396 float: left;
dbaron@6477 397 margin: 1em;
dbaron@6477 398 font: medium/1.25 Times New
dbaron@6477 399 Roman, Times, serif;
dbaron@6477 400 }
dbaron@6477 401 .bouncy-columns::nth-region(1) {
dbaron@6477 402 background: aqua; color: black;
dbaron@6477 403 transform: rotate(-3deg);
dbaron@6477 404 }
dbaron@6477 405 .bouncy-columns::nth-region(2) {
dbaron@6477 406 background: yellow; color: black;
dbaron@6477 407 transform: rotate(3deg);
dbaron@6477 408 }
dbaron@6477 409 &lt;/style&gt;
dbaron@6477 410 &lt;div class="bouncy-columns"&gt;
dbaron@6477 411 <i>...</i>
dbaron@6477 412 &lt;/div&gt;</pre></td><td>
dbaron@6477 413 <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>
dbaron@6477 414 <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>
dbaron@6477 415 <div class="bouncy-columns-demo">just doesn't<br>have any<br>region-specific<br>styling because<br>the author<br>didn't give it<br>any.</div>
dbaron@6477 416 </td></tr></table>
dbaron@6477 417 </div>
dbaron@6477 418
dbaron@6470 419 <p>
dbaron@6476 420 Styling an ''::nth-region()'' pseudo-element with the 'overflow'
dbaron@6470 421 property has no effect;
dbaron@6470 422 the computed value of 'overflow' for the region box
dbaron@6470 423 remains the same as the computed value of overflow for the element.
dbaron@6470 424 </p>
dbaron@6470 425
dbaron@6470 426 <p>
dbaron@6470 427 Specifying ''display: none'' for a region box causes
dbaron@6470 428 the region box with that index not to be generated.
dbaron@6470 429 However, in terms of the indices
dbaron@6476 430 used for matching ''::nth-region()'' pseudo-elements
dbaron@6470 431 of later region boxes,
dbaron@6470 432 it still counts as though it was generated.
dbaron@6470 433 However, since it is not generated, it does not contain any content.
dbaron@6470 434 </p>
dbaron@6470 435
dbaron@6470 436 <p class="issue">
dbaron@6470 437 Would it make more sense to forbid ''display:none''?
dbaron@6470 438 Or perhaps to forbid 'display', 'position', 'float',
dbaron@6470 439 and similar (in addition to 'overflow')?
dbaron@6470 440 </p>
dbaron@6470 441
dbaron@6470 442 <p>
dbaron@6470 443 To match the model for other pseudo-elements
dbaron@6470 444 where the pseudo-elements live inside their corresponding element,
dbaron@6470 445 declarations in ''::nth-region()'' pseudo-elements override
dbaron@6470 446 declarations in rules without the pseudo-element.
dbaron@6470 447 The relative priority within such declarations is determined
dbaron@6470 448 by normal cascading order (see [[!CSS21]]).
dbaron@6470 449 </p>
dbaron@6470 450
dbaron@6470 451 <p>
dbaron@6470 452 Styles specified on ''::nth-region()'' pseudo-elements
dbaron@6470 453 do affect inheritance to content within the <i>region box</i>.
dbaron@6470 454 In other words, the content within the <i>region box</i> must
dbaron@6470 455 inherit from the region box's style (i.e., the pseudo-element style)
dbaron@6470 456 rather than directly from the element.
dbaron@6470 457 This means that elements split between region boxes may
dbaron@6470 458 have different styles for different parts of the element.
dbaron@6470 459 </p>
dbaron@6470 460
dbaron@6472 461 <p class="issue">
dbaron@6472 462 This inheritance rule allows specifying styles indirectly
dbaron@6472 463 (by using explicit ''inherit'' or using default inheritance
dbaron@6472 464 on properties that don't apply to '':first-letter'')
dbaron@6472 465 that can't be specified directly
dbaron@6472 466 (based on the rules in the next section).
dbaron@6472 467 This is a problem.
dbaron@6472 468 The restrictions that apply to styling inside regions
dbaron@6472 469 should also apply to inheritance from regions.
dbaron@6472 470 </p>
dbaron@6472 471
dbaron@6480 472 <div class="example">
dbaron@6480 473 <table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
dbaron@6480 474 &lt;style&gt;
dbaron@6480 475 .article {
dbaron@6480 476 overflow: regions;
dbaron@6480 477 }
dbaron@6480 478 .article::nth-region(1) {
dbaron@6480 479 font-size: 1.5em;
dbaron@6480 480 margin-bottom: 1em;
dbaron@6480 481 height: 4em;
dbaron@6480 482 }
dbaron@6480 483 .article::nth-region(n+2) {
dbaron@6480 484 /* 2 and up */
dbaron@6480 485 margin-left: 5em;
dbaron@6480 486 margin-right: 2em;
dbaron@6480 487 }
dbaron@6480 488 &lt;/style&gt;
dbaron@6480 489 &lt;div class="article"&gt;
dbaron@6480 490 The &lt;code&gt;font-size&lt;/code&gt; property<i>...</i>
dbaron@6480 491 &lt;/div&gt;</pre></td><td>
dbaron@6480 492 <div class="article-font-inherit-demo one">The <code>font-size</code> property<br>specified on the region<br>is inherited into the</div>
dbaron@6480 493 <div class="article-font-inherit-demo two">descendants of the region.<br>This means that inherited<br>properties can be used<br>reliably on a region, as in<br>this example.</div>
dbaron@6480 494 </td></tr></table>
dbaron@6480 495 </div>
dbaron@6478 496
dbaron@6470 497 <h4 id="style-in-regions">Styling inside regions</h4>
dbaron@6470 498
dbaron@6470 499 <p class="issue">
dbaron@6470 500 Should this apply to region overflow only,
dbaron@6470 501 or also to paginated overflow,
dbaron@6470 502 or even to pagination across pages?
dbaron@6470 503 </p>
dbaron@6470 504
dbaron@6470 505 <p>
dbaron@6476 506 The ''::nth-region()'' pseudo-element
dbaron@6470 507 can also be used to style
dbaron@6470 508 content inside of a <i>region box</i>.
dbaron@6470 509 Unlike the ''::first-line'' and ''::first-letter'' pseudo-elements,
dbaron@6476 510 the ''::nth-region()'' pseudo-element can be applied
dbaron@6470 511 to parts of the selector other than the subject:
dbaron@6470 512 in particular, it can match ancestors of the subject.
dbaron@6470 513 However, the only CSS properties applied
dbaron@6470 514 by rules with such selectors
dbaron@6470 515 are those that apply
dbaron@6470 516 to the ''::first-letter'' pseudo-element.
dbaron@6470 517 </p>
dbaron@6470 518
dbaron@6470 519 <p>
dbaron@6470 520 To be more precise,
dbaron@6470 521 when a rule's selector has ''::nth-region()'' pseudo-elements
dbaron@6470 522 attached to parts of the selector other than the subject,
dbaron@6470 523 the declarations in that rule apply to
dbaron@6470 524 a fragment (or pseudo-element thereof) when:
dbaron@6470 525 </p>
dbaron@6470 526 <ol>
dbaron@6470 527 <li>
dbaron@6470 528 the declarations are for properties that apply to the
dbaron@6470 529 ''::first-letter'' pseudo-element,
dbaron@6470 530 </li>
dbaron@6470 531 <li>
dbaron@6470 532 the declarations would apply to
dbaron@6470 533 that fragment (or pseudo-element thereof)
dbaron@6470 534 had those ''::nth-region()'' pseudo-elements been removed,
dbaron@6470 535 with a particular association between
dbaron@6470 536 each sequence of simple selectors and the element it matched,
dbaron@6470 537 and
dbaron@6470 538 </li>
dbaron@6470 539 <li>
dbaron@6470 540 for each removed ''::nth-region()'' pseudo-element,
dbaron@6470 541 the fragment lives within a <i>region box</i>
dbaron@6470 542 of the element associated in that association
dbaron@6470 543 with the selector that the pseudo-element was attached to,
dbaron@6470 544 and whose index matches the pseudo-element.
dbaron@6470 545 </li>
dbaron@6470 546 </ol>
dbaron@6470 547
dbaron@6481 548 <div class="example">
dbaron@6481 549 <table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
dbaron@6481 550 &lt;style&gt;
dbaron@6481 551 .dark-columns {
dbaron@6481 552 overflow: regions;
dbaron@6481 553 width: 6em;
dbaron@6481 554 height: 10em;
dbaron@6481 555 float: left;
dbaron@6481 556 margin-right: 1em;
dbaron@6481 557 font: medium/1.25 Times New
dbaron@6481 558 Roman, Times, serif;
dbaron@6481 559 }
dbaron@6481 560 .dark-columns::nth-region(1) {
dbaron@6481 561 background: aqua; color: black;
dbaron@6481 562 }
dbaron@6481 563 .dark-columns::nth-region(1) :link {
dbaron@6481 564 color: blue;
dbaron@6481 565 }
dbaron@6481 566 .dark-columns::nth-region(1) :visited {
dbaron@6481 567 color: purple;
dbaron@6481 568 }
dbaron@6481 569 .dark-columns::nth-region(2) {
dbaron@6481 570 background: navy; color: white;
dbaron@6481 571 }
dbaron@6481 572 .dark-columns::nth-region(2) :link {
dbaron@6481 573 color: aqua;
dbaron@6481 574 }
dbaron@6481 575 .dark-columns::nth-region(2) :visited {
dbaron@6481 576 color: fuchsia;
dbaron@6481 577 }
dbaron@6481 578 &lt;/style&gt;
dbaron@6481 579 &lt;div class="dark-columns"&gt;
dbaron@6481 580 <i>...</i>
dbaron@6481 581 &lt;/div&gt;</pre></td><td>
dbaron@6481 582 <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>region into<br>another<br>dark-colored</div>
dbaron@6481 583 <div class="dark-columns-demo two">region. 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>regions.</div>
dbaron@6481 584 </td></tr></table>
dbaron@6481 585 </div>
dbaron@6481 586
dbaron@6478 587
dbaron@6470 588 <h3 id="max-lines">The 'max-lines' property</h3>
dbaron@6470 589
dbaron@6470 590 <p>
dbaron@6470 591 Authors may wish to style the opening lines of an element
dbaron@6470 592 with different styles
dbaron@6470 593 by putting those opening lines in a separate region.
dbaron@6470 594 However, since it may be difficult to predict the exact height
dbaron@6470 595 occupied by those lines
dbaron@6470 596 in order to restrict the first region to that height,
dbaron@6470 597 this specification introduces a 'max-lines' property
dbaron@6470 598 that forces a region to break
dbaron@6470 599 after a specified number of lines.
dbaron@6470 600 This forces a break after the given number of lines
dbaron@6470 601 contained within the element or its descendants,
dbaron@6470 602 as long as those lines are in the same block formatting context.
dbaron@6470 603 </p>
dbaron@6470 604
dbaron@6470 605 <table class=propdef>
dbaron@6470 606 <tr>
dbaron@6470 607 <th>Name:
dbaron@6470 608 <td><dfn>max-lines</dfn>
dbaron@6470 609 <tr>
dbaron@6470 610 <th><a href="#values">Value</a>:
dbaron@6470 611 <td>none | &lt;integer&gt;
dbaron@6470 612 <tr>
dbaron@6470 613 <th>Initial:
dbaron@6470 614 <td>none
dbaron@6470 615 <tr>
dbaron@6470 616 <th>Applies to:
dbaron@6470 617 <td>region boxes
dbaron@6470 618 <tr>
dbaron@6470 619 <th>Inherited:
dbaron@6470 620 <td>no
dbaron@6470 621 <tr>
dbaron@6482 622 <th>Animatable:
dbaron@6482 623 <td>as <a href="http://www.w3.org/TR/css3-transitions/#animatable-types">integer</a>
dbaron@6482 624 <tr>
dbaron@6470 625 <th>Percentages:
dbaron@6470 626 <td>N/A
dbaron@6470 627 <tr>
dbaron@6470 628 <th>Media:
dbaron@6470 629 <td>visual
dbaron@6470 630 <tr>
dbaron@6470 631 <th>Computed&nbsp;value:
dbaron@6470 632 <td>specified value
dbaron@6470 633 <tr>
dbaron@6470 634 <th>Canonical order:
dbaron@6470 635 <td><abbr title="follows order of property value definition">per grammar</abbr>
dbaron@6470 636 </table>
dbaron@6470 637
dbaron@6470 638 <dl>
dbaron@6470 639 <dt>none
dbaron@6470 640 <dd>
dbaron@6470 641 <p>
dbaron@6470 642 Breaks occur only as specified elsewhere.
dbaron@6470 643 </p>
dbaron@6470 644 </dd>
dbaron@6470 645
dbaron@6470 646 <dt>&lt;integer&gt;
dbaron@6470 647 <dd>
dbaron@6470 648 <p>
dbaron@6470 649 In addition to any breaks specified elsewhere,
dbaron@6470 650 a break is forced before any line that would exceed
dbaron@6470 651 the given number of lines
dbaron@6470 652 being placed inside the element
dbaron@6470 653 (excluding lines that are in
dbaron@6470 654 a different block formatting context from
dbaron@6470 655 the block formatting context to which
dbaron@6470 656 an unstyled child of the element would belong).
dbaron@6470 657 </p>
dbaron@6470 658
dbaron@6470 659 <p class="issue">
dbaron@6470 660 If there are multiple boundaries between this line
dbaron@6470 661 and the previous, where exactly (in terms of element
dbaron@6470 662 boundaries) is the break forced?
dbaron@6470 663 </p>
dbaron@6470 664
dbaron@6470 665 <p>
dbaron@6470 666 Only positive integers are accepted.
dbaron@6470 667 Zero or negative integers are a parse error.
dbaron@6470 668 </p>
dbaron@6470 669 </dd>
dbaron@6470 670 </dl>
dbaron@6470 671
dbaron@6470 672 <p class="issue">Should this apply to regions overflow only, or also
dbaron@6470 673 to pagination?</p>
dbaron@6470 674
dbaron@6479 675 <div class="example">
dbaron@6479 676 <table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;
dbaron@6479 677 &lt;style&gt;
dbaron@6479 678 .article {
dbaron@6479 679 overflow: regions;
dbaron@6479 680 }
dbaron@6479 681 .article::first-letter {
dbaron@6479 682 font-size: 2em;
dbaron@6479 683 line-height: 0.9;
dbaron@6479 684 }
dbaron@6479 685 .article::nth-region(1) {
dbaron@6479 686 font-size: 1.5em;
dbaron@6479 687 max-lines: 3;
dbaron@6479 688 }
dbaron@6479 689 .article::nth-region(n+2) {
dbaron@6479 690 /* 2 and up */
dbaron@6479 691 column-count: 2;
dbaron@6479 692 }
dbaron@6479 693 &lt;/style&gt;
dbaron@6479 694 &lt;div class="article"&gt;
dbaron@6479 695 <i>...</i>
dbaron@6479 696 &lt;/div&gt;</pre></td><td>
dbaron@6479 697 <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>
dbaron@6479 698 <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>
dbaron@6479 699 <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>
dbaron@6479 700 </td></tr></table>
dbaron@6479 701 </div>
dbaron@6478 702
dbaron@6470 703 <h2 id="conformance">
dbaron@6470 704 Conformance</h2>
dbaron@6470 705
dbaron@6470 706 <h3 id="placement">
dbaron@6470 707 Module interactions</h3>
dbaron@6470 708
dbaron@6470 709 <p>This module extends the 'overflow'
dbaron@6470 710 feature defined in [[CSS21]] section 11.1.1. It defines additional
dbaron@6470 711 overflow handling mechanisms that implementations must implement as
dbaron@6470 712 described in this module in order to conform to this module.</p>
dbaron@6470 713
dbaron@6470 714 <p>No properties in this module apply to the <code>::first-line</code> or
dbaron@6470 715 <code>::first-letter</code> pseudo-elements.</p>
dbaron@6470 716
dbaron@6470 717 <h3 id="values">
dbaron@6470 718 Values</h3>
dbaron@6470 719
dbaron@6470 720 <p>This specification follows the
dbaron@6470 721 <a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
dbaron@6470 722 definition conventions</a> from [[!CSS21]]. Value types not defined in
dbaron@6470 723 this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
dbaron@6470 724 Other CSS modules may expand the definitions of these value types: for
dbaron@6470 725 example [[CSS3COLOR]], when combined with this module, expands the
dbaron@6470 726 definition of the &lt;color&gt; value type as used in this specification.</p>
dbaron@6470 727
dbaron@6470 728 <p>In addition to the property-specific values listed in their definitions,
dbaron@6470 729 all properties defined in this specification also accept the
dbaron@6470 730 <a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
dbaron@6470 731 keyword as their property value. For readability it has not been repeated
dbaron@6470 732 explicitly.
dbaron@6470 733
dbaron@6470 734
dbaron@6470 735 <h3 id="conventions">
dbaron@6470 736 Document conventions</h3>
dbaron@6470 737
dbaron@6470 738 <p>Conformance requirements are expressed with a combination of
dbaron@6470 739 descriptive assertions and RFC 2119 terminology. The key words “MUST”,
dbaron@6470 740 “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
dbaron@6470 741 “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
dbaron@6470 742 document are to be interpreted as described in RFC 2119.
dbaron@6470 743 However, for readability, these words do not appear in all uppercase
dbaron@6470 744 letters in this specification.
dbaron@6470 745
dbaron@6470 746 <p>All of the text of this specification is normative except sections
dbaron@6470 747 explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
dbaron@6470 748
dbaron@6470 749 <p>Examples in this specification are introduced with the words “for example”
dbaron@6470 750 or are set apart from the normative text with <code>class="example"</code>,
dbaron@6470 751 like this:
dbaron@6470 752
dbaron@6470 753 <div class="example">
dbaron@6470 754 <p>This is an example of an informative example.</p>
dbaron@6470 755 </div>
dbaron@6470 756
dbaron@6470 757 <p>Informative notes begin with the word “Note” and are set apart from the
dbaron@6470 758 normative text with <code>class="note"</code>, like this:
dbaron@6470 759
dbaron@6470 760 <p class="note">Note, this is an informative note.</p>
dbaron@6470 761
dbaron@6470 762 <h3 id="conformance-classes">
dbaron@6470 763 Conformance classes</h3>
dbaron@6470 764
dbaron@6483 765 <p>Conformance to CSS Overflow Module Level 3
dbaron@6470 766 is defined for three conformance classes:
dbaron@6470 767 <dl>
dbaron@6470 768 <dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
dbaron@6470 769 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
dbaron@6470 770 style sheet</a>.
dbaron@6470 771 <dt><dfn>renderer</dfn></dt>
dbaron@6470 772 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
dbaron@6470 773 that interprets the semantics of a style sheet and renders
dbaron@6470 774 documents that use them.
dbaron@6470 775 <dt><dfn id="authoring-tool">authoring tool</dfn></dt>
dbaron@6470 776 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
dbaron@6470 777 that writes a style sheet.
dbaron@6470 778 </dl>
dbaron@6470 779
dbaron@6483 780 <p>A style sheet is conformant to CSS Overflow Module Level 3
dbaron@6470 781 if all of its statements that use syntax defined in this module are valid
dbaron@6470 782 according to the generic CSS grammar and the individual grammars of each
dbaron@6470 783 feature defined in this module.
dbaron@6470 784
dbaron@6483 785 <p>A renderer is conformant to CSS Overflow Module Level 3
dbaron@6470 786 if, in addition to interpreting the style sheet as defined by the
dbaron@6470 787 appropriate specifications, it supports all the features defined
dbaron@6483 788 by CSS Overflow Module Level 3 by parsing them correctly
dbaron@6470 789 and rendering the document accordingly. However, the inability of a
dbaron@6470 790 UA to correctly render a document due to limitations of the device
dbaron@6470 791 does not make the UA non-conformant. (For example, a UA is not
dbaron@6470 792 required to render color on a monochrome monitor.)
dbaron@6470 793
dbaron@6483 794 <p>An authoring tool is conformant to CSS Overflow Module Level 3
dbaron@6470 795 if it writes style sheets that are syntactically correct according to the
dbaron@6470 796 generic CSS grammar and the individual grammars of each feature in
dbaron@6470 797 this module, and meet all other conformance requirements of style sheets
dbaron@6470 798 as described in this module.
dbaron@6470 799
dbaron@6470 800 <h3 id="partial">
dbaron@6470 801 Partial implementations</h3>
dbaron@6470 802
dbaron@6470 803 <p>So that authors can exploit the forward-compatible parsing rules to
dbaron@6470 804 assign fallback values, CSS renderers <strong>must</strong>
dbaron@6470 805 treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
dbaron@6470 806 as appropriate</a>) any at-rules, properties, property values, keywords,
dbaron@6470 807 and other syntactic constructs for which they have no usable level of
dbaron@6470 808 support. In particular, user agents <strong>must not</strong> selectively
dbaron@6470 809 ignore unsupported component values and honor supported values in a single
dbaron@6470 810 multi-value property declaration: if any value is considered invalid
dbaron@6470 811 (as unsupported values must be), CSS requires that the entire declaration
dbaron@6470 812 be ignored.</p>
dbaron@6470 813
dbaron@6470 814 <h3 id="experimental">
dbaron@6470 815 Experimental implementations</h3>
dbaron@6470 816
dbaron@6470 817 <p>To avoid clashes with future CSS features, the CSS2.1 specification
dbaron@6470 818 reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
dbaron@6470 819 syntax</a> for proprietary and experimental extensions to CSS.
dbaron@6470 820
dbaron@6470 821 <p>Prior to a specification reaching the Candidate Recommendation stage
dbaron@6470 822 in the W3C process, all implementations of a CSS feature are considered
dbaron@6470 823 experimental. The CSS Working Group recommends that implementations
dbaron@6470 824 use a vendor-prefixed syntax for such features, including those in
dbaron@6470 825 W3C Working Drafts. This avoids incompatibilities with future changes
dbaron@6470 826 in the draft.
dbaron@6470 827 </p>
dbaron@6470 828
dbaron@6470 829 <h3 id="testing">
dbaron@6470 830 Non-experimental implementations</h3>
dbaron@6470 831
dbaron@6470 832 <p>Once a specification reaches the Candidate Recommendation stage,
dbaron@6470 833 non-experimental implementations are possible, and implementors should
dbaron@6470 834 release an unprefixed implementation of any CR-level feature they
dbaron@6470 835 can demonstrate to be correctly implemented according to spec.
dbaron@6470 836
dbaron@6470 837 <p>To establish and maintain the interoperability of CSS across
dbaron@6470 838 implementations, the CSS Working Group requests that non-experimental
dbaron@6470 839 CSS renderers submit an implementation report (and, if necessary, the
dbaron@6470 840 testcases used for that implementation report) to the W3C before
dbaron@6470 841 releasing an unprefixed implementation of any CSS features. Testcases
dbaron@6470 842 submitted to W3C are subject to review and correction by the CSS
dbaron@6470 843 Working Group.
dbaron@6470 844
dbaron@6470 845 <p>Further information on submitting testcases and implementation reports
dbaron@6470 846 can be found from on the CSS Working Group's website at
dbaron@6470 847 <a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
dbaron@6470 848 Questions should be directed to the
dbaron@6470 849 <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
dbaron@6470 850 mailing list.
dbaron@6470 851
dbaron@6470 852 <h3 id="cr-exit-criteria">
dbaron@6470 853 CR exit criteria</h3>
dbaron@6470 854
dbaron@6470 855 <p class=issue>[Change or remove the following CR exit criteria if
dbaron@6470 856 the spec is not a module, but, e.g., a Note or a profile. This text was <a
dbaron@6470 857 href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on 2008-06-04.</a>]</p>
dbaron@6470 858
dbaron@6470 859 <p>
dbaron@6470 860 For this specification to be advanced to Proposed Recommendation,
dbaron@6470 861 there must be at least two independent, interoperable implementations
dbaron@6470 862 of each feature. Each feature may be implemented by a different set of
dbaron@6470 863 products, there is no requirement that all features be implemented by
dbaron@6470 864 a single product. For the purposes of this criterion, we define the
dbaron@6470 865 following terms:
dbaron@6470 866
dbaron@6470 867 <dl>
dbaron@6470 868 <dt>independent <dd>each implementation must be developed by a
dbaron@6470 869 different party and cannot share, reuse, or derive from code
dbaron@6470 870 used by another qualifying implementation. Sections of code that
dbaron@6470 871 have no bearing on the implementation of this specification are
dbaron@6470 872 exempt from this requirement.
dbaron@6470 873
dbaron@6470 874 <dt>interoperable <dd>passing the respective test case(s) in the
dbaron@6470 875 official CSS test suite, or, if the implementation is not a Web
dbaron@6470 876 browser, an equivalent test. Every relevant test in the test
dbaron@6470 877 suite should have an equivalent test created if such a user
dbaron@6470 878 agent (UA) is to be used to claim interoperability. In addition
dbaron@6470 879 if such a UA is to be used to claim interoperability, then there
dbaron@6470 880 must one or more additional UAs which can also pass those
dbaron@6470 881 equivalent tests in the same way for the purpose of
dbaron@6470 882 interoperability. The equivalent tests must be made publicly
dbaron@6470 883 available for the purposes of peer review.
dbaron@6470 884
dbaron@6470 885 <dt>implementation <dd>a user agent which:
dbaron@6470 886
dbaron@6470 887 <ol class=inline>
dbaron@6470 888 <li>implements the specification.
dbaron@6470 889
dbaron@6470 890 <li>is available to the general public. The implementation may
dbaron@6470 891 be a shipping product or other publicly available version
dbaron@6470 892 (i.e., beta version, preview release, or “nightly build”).
dbaron@6470 893 Non-shipping product releases must have implemented the
dbaron@6470 894 feature(s) for a period of at least one month in order to
dbaron@6470 895 demonstrate stability.
dbaron@6470 896
dbaron@6470 897 <li>is not experimental (i.e., a version specifically designed
dbaron@6470 898 to pass the test suite and is not intended for normal usage
dbaron@6470 899 going forward).
dbaron@6470 900 </ol>
dbaron@6470 901 </dl>
dbaron@6470 902
dbaron@6470 903 <p>The specification will remain Candidate Recommendation for at least
dbaron@6470 904 six months.
dbaron@6470 905
dbaron@6470 906 <h2 class=no-num id="acknowledgments">
dbaron@6470 907 Acknowledgments</h2>
dbaron@6470 908
dbaron@6470 909 <p>
dbaron@6470 910 Thanks especially to the feedback from
dbaron@6470 911 H&aring;kon Wium Lie,
dbaron@6470 912 Florian Rivoal,
dbaron@6473 913 Alan Stearns,
dbaron@6470 914 and all the rest of the
dbaron@6470 915 <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> community.
dbaron@6470 916 </p>
dbaron@6470 917
dbaron@6470 918 <h2 class=no-num id="references">
dbaron@6470 919 References</h2>
dbaron@6470 920
dbaron@6470 921 <h3 class="no-num" id="normative-references">
dbaron@6470 922 Normative references</h3>
dbaron@6470 923 <!--normative-->
dbaron@6470 924
dbaron@6470 925 <h3 class="no-num" id="other-references">
dbaron@6470 926 Other references</h3>
dbaron@6470 927 <!--informative-->
dbaron@6470 928
dbaron@6470 929 <h2 class="no-num" id="index">
dbaron@6470 930 Index</h2>
dbaron@6470 931 <!--index-->
dbaron@6470 932
dbaron@6470 933 <h2 class="no-num" id="property-index">
dbaron@6470 934 Property index</h2>
dbaron@6470 935 <!-- properties -->
dbaron@6470 936
dbaron@6470 937 </body>
dbaron@6470 938 </html>
dbaron@6470 939 <!-- Keep this comment at the end of the file
dbaron@6470 940 Local variables:
dbaron@6470 941 mode: sgml
dbaron@6470 942 sgml-declaration:"~/SGML/HTML4.decl"
dbaron@6470 943 sgml-default-doctype-name:"html"
dbaron@6470 944 sgml-minimize-attributes:t
dbaron@6470 945 sgml-nofill-elements:("pre" "style" "br")
dbaron@6470 946 sgml-live-element-indicator:t
dbaron@6470 947 sgml-omittag:nil
dbaron@6470 948 sgml-shorttag:nil
dbaron@6470 949 sgml-namecase-general:t
dbaron@6470 950 sgml-general-insert-case:lower
dbaron@6470 951 sgml-always-quote-attributes:t
dbaron@6470 952 sgml-indent-step:nil
dbaron@6470 953 sgml-indent-data:t
dbaron@6470 954 sgml-parent-document:nil
dbaron@6470 955 sgml-exposed-tags:nil
dbaron@6470 956 sgml-local-catalogs:nil
dbaron@6470 957 sgml-local-ecat-files:nil
dbaron@6470 958 End:
dbaron@6470 959 -->
dbaron@6470 960

mercurial