css3-overflow/Overview.src.html@4454a4d747b2
css3-overflow/Overview.src.html
Mon, 06 Aug 2012 17:42:01 -0700
- author
- L. David Baron <dbaron@dbaron.org>
- date
- Mon, 06 Aug 2012 17:42:01 -0700
- changeset 6475
- 4454a4d747b2
- parent 6474
- accd2ba885a3
- child 6476
- abfd019f595b
- permissions
- -rw-r--r--
Add one example.
1 <!DOCTYPE html>
2 <html lang="en">
3 <head>
4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
5 <title>CSS Region Styling 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 .in-cards-demo {
13 width: 13em;
14 height: 8em;
16 padding: 4px;
17 border: medium solid blue;
18 margin: 6px;
20 font: medium/1.3 Times New Roman, Times, serif;
21 white-space: nowrap;
22 }
23 </style>
24 </head>
26 <div class="head">
27 <!--logo-->
29 <h1>CSS Region Styling Module Level 3</h1>
31 <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
32 <dl>
33 <dt>This version:
34 <dd><a href="[VERSION]">http://www.w3.org/TR/[YEAR]/ED-css3-region-styling-[CDATE]/</a>
36 <dt>Latest version:
37 <dd><a href="http://www.w3.org/TR/[SHORTNAME]/">http://www.w3.org/TR/[SHORTNAME]/</a>
39 <dt>Editor's draft:
40 <dd><a href="http://dev.w3.org/csswg/[SHORTNAME]/">http://dev.w3.org/csswg/[SHORTNAME]/</a>
42 <!--
43 <dt>Previous version:
44 <dd><a href="http://www.w3.org/PreviousVersionURI">
45 http://www.w3.org/PreviousVersionURI</a>
46 -->
48 <dt>Issue Tracking:</dt>
49 <dd>Maintained in document (only editor's draft is current)
51 <dt>Feedback:</dt>
52 <dd><a href="http://lists.w3.org/Archives/Public/www-style/">www-style@w3.org</a> with subject line “<kbd>[[SHORTNAME]] <var>… message topic …</var></kbd>”
54 <dt>Editors:
55 <dd class="h-card vcard">
56 <a class="p-name fn u-url url" rel="author"
57 href="http://dbaron.org/">L. David Baron</a>,
58 <a class="p-org org" href="http://www.mozilla.org/">Mozilla</a>
59 </dl>
61 <!--copyright-->
63 <hr title="Separator for header">
64 </div>
66 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
68 <p>
69 <a href="http://www.w3.org/TR/CSS/">CSS</a> is
70 a language for describing
71 the rendering of structured documents (such as HTML and XML)
72 on screen, on paper, in speech, etc.
73 This module contains the features of CSS
74 relating to new mechanisms of overflow handling in visual media (e.g., screen or paper).
75 In interactive media,
76 it describes features that allow the overflow
77 from a fixed size container
78 to be handled by pagination (displaying one page at a time).
79 It also describes features, applying to all visual media,
80 that allow the contents of an element
81 to be spread across multiple containers,
82 allowing the contents to flow across multiple regions of a page
83 or to have different styles for different parts.
84 </p>
86 <h2 class="no-num no-toc" id="status">Status of this document</h2>
88 <!--status-->
90 <p>The following features are at risk: …
92 <h2 class="no-num no-toc" id="contents">
93 Table of contents</h2>
95 <!--toc-->
97 <h2 id="intro">
98 Introduction</h2>
100 <p>
101 In CSS Level 1 [[CSS1]], placing more content than would fit
102 inside an element with a specified size
103 was generally an authoring error.
104 Doing so caused the content to extend
105 outside the bounds of the element,
106 which would likely cause
107 that content to overlap with other elements.
108 </p>
110 <p>
111 CSS Level 2 [[CSS21]] introduced the 'overflow' property,
112 which allows authors to have overflow be handled by scrolling,
113 which means it is no longer an authoring error.
114 It also allows authors to specify
115 that overflow is handled by clipping,
116 which makes sense when the author's intent
117 is that the content not be shown.
118 </p>
120 <p>
121 However, scrolling is not the only way
122 to present large amounts of content,
123 and may even not be the optimal way.
124 After all, the codex replaced the scroll
125 as the common format for large written works
126 because of its advantages.
127 </p>
129 <p>
130 This specification introduces
131 a mechanism for Web pages to specify
132 that a region of a page should handle overflow
133 through pagination rather than through scrolling.
134 </p>
136 <p>
137 This specification also extends the concept of overflow
138 in another direction.
139 Instead of requiring that authors specify a single region
140 into which the content of an element must flow,
141 this specification allows authors to specify multiple regions,
142 each with their own dimensions and styles,
143 so that the content of the element can flow from one to the next,
144 using as many as needed to place the content without overflowing.
145 </p>
147 <p>
148 In both of these cases, implementations must
149 break the content in the block-progression dimension.
150 Implementations must do this is described
151 in the CSS Fragmentation Module [[!CSS3-BREAK]].
152 </p>
155 <h2 id="paginated-overflow">Paginated overflow</h2>
157 <p class="issue">overflow:paginate or overflow:pages (or paged-x, paged-y, paged-x-controls, paged-y-controls as css3-gcpm has?)</p>
159 <p class="issue">Ability to display N pages at once
160 rather than just one page at once?</p>
162 <h2 id="region-overflow">Region overflow</h2>
164 <p>
165 This section introduces and defines the meaning of
166 the new ''regions'' (<span class="issue">or ''repeat''?</span>)
167 value of the 'overflow' property.
168 </p>
170 <p>
171 When the computed value of 'overflow' for an element is ''regions'',
172 and implementations would otherwise have created a box for the element,
173 then implementations must create at least one box for that element.
174 Each box created for the element is called a <dfn>region box</dfn>
175 for that element.
176 (If an element with ''overflow: regions'' generates only one box,
177 that box is a <i>region box</i>.
178 However, if an element's computed 'overflow' is not ''regions'',
179 then its box is not a <i>region box</i>.)
180 Every <i>region box</i> is a fragmentation container,
181 and for each <i>region box</i> which ends with a fragmentation break,
182 (which could happen
183 because breakable content overflows in the block dimension
184 or because of a forced break),
185 there must be another <i>region box</i> created as a next sibling
186 of the previous one.
187 <span class="issue">Or is it as though it's a next sibling of
188 the element? Need to figure out exactly how this interacts with
189 other box-level fixup.</span>
190 (Breakable content might overflow in the box dimension either
191 because of a specified size on the region box
192 or because the region box is within a fragmentation context
193 in which it is being broken.
194 In other words, a single region box is never broken
195 across columns or pages;
196 the pieces that are in separate columns or pages
197 are always distinct region boxes.)
198 </p>
200 <p class="issue">
201 We also want '':nth-region()'' pseudo-elements
202 to be able to apply to the pieces of an element
203 split within a fragmentation context.
204 Should we require that authors who want to use
205 '':nth-region()'' in this way specify ''overflow:regions''
206 (even if they don't specify a constrained height),
207 or should it work automatically for all elements
208 even if they don't have ''overflow: regions''?
209 </p>
211 <div class="example">
212 <table style="width: 100%"><tr><td><pre>
213 <!DOCTYPE HTML>
214 <title>Breaking content into
215 equal-sized cards</title>
216 <style>
217 .in-cards {
218 overflow: regions;
220 width: 13em;
221 height: 8em;
223 padding: 4px;
224 border: medium solid blue;
225 margin: 6px;
227 font: medium/1.3 Times New
228 Roman, Times, serif;
229 }
230 </style>
231 <div class="in-cards">
232 In this example, the text in the div
233 is broken into a series of cards.
234 These cards all have the same style.
235 The presence of enough content to
236 overflow one of the cards causes
237 another one to be created. The second
238 card is created just like it's the
239 next sibling of the first.
240 </div>
241 </pre></td><td>
242 <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>
243 <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>
244 </td></tr></table>
245 </div>
247 <h3 id="region-styling">Region styling</h3>
249 <h4 id="region-pseudo-element">The ::nth-region() pseudo-element</h4>
251 <p>
252 The ::nth-region() pseudo-element is a pseudo-element
253 that describes some of the region boxes generated by an element.
254 The argument to the pseudo-element takes the same syntax
255 as the argument to the :nth-child() pseudo-class
256 defined in [[!SELECT]], and has the same meaning
257 except that the number is relative to
258 <i>region boxes</i> generated by the element
259 instead of siblings of the element.
260 </p>
262 <p class="issue">
263 If we go with a name for the 'overflow' value other than
264 ''overflow: regions'',
265 then we should probably rename this pseudo-element,
266 perhaps to ::nth-piece(), ::nth-part(), or ::nth-instance().
267 </p>
269 <p class="note">
270 Selectors that allow addressing regions
271 by counting from the end rather than the start
272 are intentionally not provided.
273 Such selectors would interfere with determining
274 the number of regions.
275 </p>
277 <h4 id="style-of-regions">Styling of regions</h4>
279 <p class="issue">
280 Should this apply to region overflow only,
281 or also to paginated overflow?
282 (If it applies,
283 then stricter property restrictions would be needed
284 for paginated overflow.)
285 </p>
287 <p>
288 In the absence of rules with ''::nth-region()'' pseudo-elements,
289 the computed style for each <i>region box</i>
290 is the computed style for the element
291 for which the <i>region box</i> was created.
292 However, the style for a <i>region box</i> is also influenced
293 by rules whose selector's <i>subject</i> [[!SELECT]]
294 has an ''::nth-region()'' pseudo-element,
295 if the 1-based number of the region box matches
296 that ''::nth-region()'' pseudo-element
297 and the selector (excluding the ''::nth-region()'' pseudo-element)
298 matches the element generating the regions.
299 </p>
301 <p>
302 Styling an '':nth-region()'' pseudo-element with the 'overflow'
303 property has no effect;
304 the computed value of 'overflow' for the region box
305 remains the same as the computed value of overflow for the element.
306 </p>
308 <p>
309 Specifying ''display: none'' for a region box causes
310 the region box with that index not to be generated.
311 However, in terms of the indices
312 used for matching '':nth-region()'' pseudo-elements
313 of later region boxes,
314 it still counts as though it was generated.
315 However, since it is not generated, it does not contain any content.
316 </p>
318 <p class="issue">
319 Would it make more sense to forbid ''display:none''?
320 Or perhaps to forbid 'display', 'position', 'float',
321 and similar (in addition to 'overflow')?
322 </p>
324 <p>
325 To match the model for other pseudo-elements
326 where the pseudo-elements live inside their corresponding element,
327 declarations in ''::nth-region()'' pseudo-elements override
328 declarations in rules without the pseudo-element.
329 The relative priority within such declarations is determined
330 by normal cascading order (see [[!CSS21]]).
331 </p>
333 <p>
334 Styles specified on ''::nth-region()'' pseudo-elements
335 do affect inheritance to content within the <i>region box</i>.
336 In other words, the content within the <i>region box</i> must
337 inherit from the region box's style (i.e., the pseudo-element style)
338 rather than directly from the element.
339 This means that elements split between region boxes may
340 have different styles for different parts of the element.
341 </p>
343 <p class="issue">
344 This inheritance rule allows specifying styles indirectly
345 (by using explicit ''inherit'' or using default inheritance
346 on properties that don't apply to '':first-letter'')
347 that can't be specified directly
348 (based on the rules in the next section).
349 This is a problem.
350 The restrictions that apply to styling inside regions
351 should also apply to inheritance from regions.
352 </p>
354 <h4 id="style-in-regions">Styling inside regions</h4>
356 <p class="issue">
357 Should this apply to region overflow only,
358 or also to paginated overflow,
359 or even to pagination across pages?
360 </p>
362 <p>
363 The '':nth-region()'' pseudo-element
364 can also be used to style
365 content inside of a <i>region box</i>.
366 Unlike the ''::first-line'' and ''::first-letter'' pseudo-elements,
367 the '':nth-region()'' pseudo-element can be applied
368 to parts of the selector other than the subject:
369 in particular, it can match ancestors of the subject.
370 However, the only CSS properties applied
371 by rules with such selectors
372 are those that apply
373 to the ''::first-letter'' pseudo-element.
374 </p>
376 <p>
377 To be more precise,
378 when a rule's selector has ''::nth-region()'' pseudo-elements
379 attached to parts of the selector other than the subject,
380 the declarations in that rule apply to
381 a fragment (or pseudo-element thereof) when:
382 </p>
383 <ol>
384 <li>
385 the declarations are for properties that apply to the
386 ''::first-letter'' pseudo-element,
387 </li>
388 <li>
389 the declarations would apply to
390 that fragment (or pseudo-element thereof)
391 had those ''::nth-region()'' pseudo-elements been removed,
392 with a particular association between
393 each sequence of simple selectors and the element it matched,
394 and
395 </li>
396 <li>
397 for each removed ''::nth-region()'' pseudo-element,
398 the fragment lives within a <i>region box</i>
399 of the element associated in that association
400 with the selector that the pseudo-element was attached to,
401 and whose index matches the pseudo-element.
402 </li>
403 </ol>
405 <h3 id="max-lines">The 'max-lines' property</h3>
407 <p>
408 Authors may wish to style the opening lines of an element
409 with different styles
410 by putting those opening lines in a separate region.
411 However, since it may be difficult to predict the exact height
412 occupied by those lines
413 in order to restrict the first region to that height,
414 this specification introduces a 'max-lines' property
415 that forces a region to break
416 after a specified number of lines.
417 This forces a break after the given number of lines
418 contained within the element or its descendants,
419 as long as those lines are in the same block formatting context.
420 </p>
422 <table class=propdef>
423 <tr>
424 <th>Name:
425 <td><dfn>max-lines</dfn>
426 <tr>
427 <th><a href="#values">Value</a>:
428 <td>none | <integer>
429 <tr>
430 <th>Initial:
431 <td>none
432 <tr>
433 <th>Applies to:
434 <td>region boxes
435 <tr>
436 <th>Inherited:
437 <td>no
438 <tr>
439 <th>Percentages:
440 <td>N/A
441 <tr>
442 <th>Media:
443 <td>visual
444 <tr>
445 <th>Computed value:
446 <td>specified value
447 <tr>
448 <th>Animatable:
449 <td>as <a href="http://www.w3.org/TR/css3-transitions/#animatable-types">integer</a>
450 <tr>
451 <th>Canonical order:
452 <td><abbr title="follows order of property value definition">per grammar</abbr>
453 </table>
455 <dl>
456 <dt>none
457 <dd>
458 <p>
459 Breaks occur only as specified elsewhere.
460 </p>
461 </dd>
463 <dt><integer>
464 <dd>
465 <p>
466 In addition to any breaks specified elsewhere,
467 a break is forced before any line that would exceed
468 the given number of lines
469 being placed inside the element
470 (excluding lines that are in
471 a different block formatting context from
472 the block formatting context to which
473 an unstyled child of the element would belong).
474 </p>
476 <p class="issue">
477 If there are multiple boundaries between this line
478 and the previous, where exactly (in terms of element
479 boundaries) is the break forced?
480 </p>
482 <p>
483 Only positive integers are accepted.
484 Zero or negative integers are a parse error.
485 </p>
486 </dd>
487 </dl>
489 <p class="issue">Should this apply to regions overflow only, or also
490 to pagination?</p>
492 <h2 id="conformance">
493 Conformance</h2>
495 <h3 id="placement">
496 Module interactions</h3>
498 <p>This module extends the 'overflow'
499 feature defined in [[CSS21]] section 11.1.1. It defines additional
500 overflow handling mechanisms that implementations must implement as
501 described in this module in order to conform to this module.</p>
503 <p>No properties in this module apply to the <code>::first-line</code> or
504 <code>::first-letter</code> pseudo-elements.</p>
506 <h3 id="values">
507 Values</h3>
509 <p>This specification follows the
510 <a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
511 definition conventions</a> from [[!CSS21]]. Value types not defined in
512 this specification are defined in CSS Level 2 Revision 1 [[!CSS21]].
513 Other CSS modules may expand the definitions of these value types: for
514 example [[CSS3COLOR]], when combined with this module, expands the
515 definition of the <color> value type as used in this specification.</p>
517 <p>In addition to the property-specific values listed in their definitions,
518 all properties defined in this specification also accept the
519 <a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">inherit</a>
520 keyword as their property value. For readability it has not been repeated
521 explicitly.
524 <h3 id="conventions">
525 Document conventions</h3>
527 <p>Conformance requirements are expressed with a combination of
528 descriptive assertions and RFC 2119 terminology. The key words “MUST”,
529 “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
530 “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
531 document are to be interpreted as described in RFC 2119.
532 However, for readability, these words do not appear in all uppercase
533 letters in this specification.
535 <p>All of the text of this specification is normative except sections
536 explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
538 <p>Examples in this specification are introduced with the words “for example”
539 or are set apart from the normative text with <code>class="example"</code>,
540 like this:
542 <div class="example">
543 <p>This is an example of an informative example.</p>
544 </div>
546 <p>Informative notes begin with the word “Note” and are set apart from the
547 normative text with <code>class="note"</code>, like this:
549 <p class="note">Note, this is an informative note.</p>
551 <h3 id="conformance-classes">
552 Conformance classes</h3>
554 <p>Conformance to CSS Region Styling Module Level 3
555 is defined for three conformance classes:
556 <dl>
557 <dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
558 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
559 style sheet</a>.
560 <dt><dfn>renderer</dfn></dt>
561 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
562 that interprets the semantics of a style sheet and renders
563 documents that use them.
564 <dt><dfn id="authoring-tool">authoring tool</dfn></dt>
565 <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
566 that writes a style sheet.
567 </dl>
569 <p>A style sheet is conformant to CSS Region Styling Module Level 3
570 if all of its statements that use syntax defined in this module are valid
571 according to the generic CSS grammar and the individual grammars of each
572 feature defined in this module.
574 <p>A renderer is conformant to CSS Region Styling Module Level 3
575 if, in addition to interpreting the style sheet as defined by the
576 appropriate specifications, it supports all the features defined
577 by CSS Region Styling Module Level 3 by parsing them correctly
578 and rendering the document accordingly. However, the inability of a
579 UA to correctly render a document due to limitations of the device
580 does not make the UA non-conformant. (For example, a UA is not
581 required to render color on a monochrome monitor.)
583 <p>An authoring tool is conformant to CSS Region Styling Module Level 3
584 if it writes style sheets that are syntactically correct according to the
585 generic CSS grammar and the individual grammars of each feature in
586 this module, and meet all other conformance requirements of style sheets
587 as described in this module.
589 <h3 id="partial">
590 Partial implementations</h3>
592 <p>So that authors can exploit the forward-compatible parsing rules to
593 assign fallback values, CSS renderers <strong>must</strong>
594 treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
595 as appropriate</a>) any at-rules, properties, property values, keywords,
596 and other syntactic constructs for which they have no usable level of
597 support. In particular, user agents <strong>must not</strong> selectively
598 ignore unsupported component values and honor supported values in a single
599 multi-value property declaration: if any value is considered invalid
600 (as unsupported values must be), CSS requires that the entire declaration
601 be ignored.</p>
603 <h3 id="experimental">
604 Experimental implementations</h3>
606 <p>To avoid clashes with future CSS features, the CSS2.1 specification
607 reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
608 syntax</a> for proprietary and experimental extensions to CSS.
610 <p>Prior to a specification reaching the Candidate Recommendation stage
611 in the W3C process, all implementations of a CSS feature are considered
612 experimental. The CSS Working Group recommends that implementations
613 use a vendor-prefixed syntax for such features, including those in
614 W3C Working Drafts. This avoids incompatibilities with future changes
615 in the draft.
616 </p>
618 <h3 id="testing">
619 Non-experimental implementations</h3>
621 <p>Once a specification reaches the Candidate Recommendation stage,
622 non-experimental implementations are possible, and implementors should
623 release an unprefixed implementation of any CR-level feature they
624 can demonstrate to be correctly implemented according to spec.
626 <p>To establish and maintain the interoperability of CSS across
627 implementations, the CSS Working Group requests that non-experimental
628 CSS renderers submit an implementation report (and, if necessary, the
629 testcases used for that implementation report) to the W3C before
630 releasing an unprefixed implementation of any CSS features. Testcases
631 submitted to W3C are subject to review and correction by the CSS
632 Working Group.
634 <p>Further information on submitting testcases and implementation reports
635 can be found from on the CSS Working Group's website at
636 <a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
637 Questions should be directed to the
638 <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
639 mailing list.
641 <h3 id="cr-exit-criteria">
642 CR exit criteria</h3>
644 <p class=issue>[Change or remove the following CR exit criteria if
645 the spec is not a module, but, e.g., a Note or a profile. This text was <a
646 href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on 2008-06-04.</a>]</p>
648 <p>
649 For this specification to be advanced to Proposed Recommendation,
650 there must be at least two independent, interoperable implementations
651 of each feature. Each feature may be implemented by a different set of
652 products, there is no requirement that all features be implemented by
653 a single product. For the purposes of this criterion, we define the
654 following terms:
656 <dl>
657 <dt>independent <dd>each implementation must be developed by a
658 different party and cannot share, reuse, or derive from code
659 used by another qualifying implementation. Sections of code that
660 have no bearing on the implementation of this specification are
661 exempt from this requirement.
663 <dt>interoperable <dd>passing the respective test case(s) in the
664 official CSS test suite, or, if the implementation is not a Web
665 browser, an equivalent test. Every relevant test in the test
666 suite should have an equivalent test created if such a user
667 agent (UA) is to be used to claim interoperability. In addition
668 if such a UA is to be used to claim interoperability, then there
669 must one or more additional UAs which can also pass those
670 equivalent tests in the same way for the purpose of
671 interoperability. The equivalent tests must be made publicly
672 available for the purposes of peer review.
674 <dt>implementation <dd>a user agent which:
676 <ol class=inline>
677 <li>implements the specification.
679 <li>is available to the general public. The implementation may
680 be a shipping product or other publicly available version
681 (i.e., beta version, preview release, or “nightly build”).
682 Non-shipping product releases must have implemented the
683 feature(s) for a period of at least one month in order to
684 demonstrate stability.
686 <li>is not experimental (i.e., a version specifically designed
687 to pass the test suite and is not intended for normal usage
688 going forward).
689 </ol>
690 </dl>
692 <p>The specification will remain Candidate Recommendation for at least
693 six months.
695 <h2 class=no-num id="acknowledgments">
696 Acknowledgments</h2>
698 <p>
699 Thanks especially to the feedback from
700 Håkon Wium Lie,
701 Florian Rivoal,
702 Alan Stearns,
703 and all the rest of the
704 <a href="http://lists.w3.org/Archives/Public/www-style/">www-style</a> community.
705 </p>
707 <h2 class=no-num id="references">
708 References</h2>
710 <h3 class="no-num" id="normative-references">
711 Normative references</h3>
712 <!--normative-->
714 <h3 class="no-num" id="other-references">
715 Other references</h3>
716 <!--informative-->
718 <h2 class="no-num" id="index">
719 Index</h2>
720 <!--index-->
722 <h2 class="no-num" id="property-index">
723 Property index</h2>
724 <!-- properties -->
726 </body>
727 </html>
728 <!-- Keep this comment at the end of the file
729 Local variables:
730 mode: sgml
731 sgml-declaration:"~/SGML/HTML4.decl"
732 sgml-default-doctype-name:"html"
733 sgml-minimize-attributes:t
734 sgml-nofill-elements:("pre" "style" "br")
735 sgml-live-element-indicator:t
736 sgml-omittag:nil
737 sgml-shorttag:nil
738 sgml-namecase-general:t
739 sgml-general-insert-case:lower
740 sgml-always-quote-attributes:t
741 sgml-indent-step:nil
742 sgml-indent-data:t
743 sgml-parent-document:nil
744 sgml-exposed-tags:nil
745 sgml-local-catalogs:nil
746 sgml-local-ecat-files:nil
747 End:
748 -->
