Annotation of html5/spec-author-view/grouping-content.html, revision 1.132
1.58 mike 1: <!DOCTYPE html><!-- when publishing, change bits marked ZZZ --><html class="split chapter" lang="en-US-x-Hixie"><head><meta content="text/html; charset=UTF-8" http-equiv="Content-Type"><title>4.5 Grouping content — HTML5 (Edition for Web Authors)</title><link href="whatwg.css" rel="stylesheet"><style type="text/css">
1.12 mike 2: pre { margin-left: 2em; white-space: pre-wrap; }
3: h2 { margin: 3em 0 1em 0; }
4: h3 { margin: 2.5em 0 1em 0; }
5: h4 { margin: 2.5em 0 0.75em 0; }
6: h5, h6 { margin: 2.5em 0 1em; }
7: h1 + h2, h1 + h2 + h2 { margin: 0.75em 0 0.75em; }
8: h2 + h3, h3 + h4, h4 + h5, h5 + h6 { margin-top: 0.5em; }
9: p { margin: 1em 0; }
10: hr:not(.top) { display: block; background: none; border: none; padding: 0; margin: 2em 0; height: auto; }
11: dl, dd { margin-top: 0; margin-bottom: 0; }
12: dt { margin-top: 0.75em; margin-bottom: 0.25em; clear: left; }
13: dt + dt { margin-top: 0; }
14: dd dt { margin-top: 0.25em; margin-bottom: 0; }
15: dd p { margin-top: 0; }
16: dd dl + p { margin-top: 1em; }
17: dd table + p { margin-top: 1em; }
18: p + * > li, dd li { margin: 1em 0; }
19: dt, dfn { font-weight: bold; font-style: normal; }
20: dt dfn { font-style: italic; }
21: pre, code { font-size: inherit; font-family: monospace; font-variant: normal; }
22: pre strong { color: black; font: inherit; font-weight: bold; background: yellow; }
23: pre em { font-weight: bolder; font-style: normal; }
24: @media screen { code { color: orangered; } code :link, code :visited { color: inherit; } }
25: var sub { vertical-align: bottom; font-size: smaller; position: relative; top: 0.1em; }
26: table { border-collapse: collapse; border-style: hidden hidden none hidden; }
1.37 mike 27: table thead, table tbody { border-bottom: solid; }
1.12 mike 28: table tbody th:first-child { border-left: solid; }
29: table tbody th { text-align: left; }
30: table td, table th { border-left: solid; border-right: solid; border-bottom: solid thin; vertical-align: top; padding: 0.2em; }
31: blockquote { margin: 0 0 0 2em; border: 0; padding: 0; font-style: italic; }
32:
33: .bad, .bad *:not(.XXX) { color: gray; border-color: gray; background: transparent; }
34: .matrix, .matrix td { border: none; text-align: right; }
35: .matrix { margin-left: 2em; }
36: .dice-example { border-collapse: collapse; border-style: hidden solid solid hidden; border-width: thin; margin-left: 3em; }
37: .dice-example caption { width: 30em; font-size: smaller; font-style: italic; padding: 0.75em 0; text-align: left; }
38: .dice-example td, .dice-example th { border: solid thin; width: 1.35em; height: 1.05em; text-align: center; padding: 0; }
39:
40: .toc dfn, h1 dfn, h2 dfn, h3 dfn, h4 dfn, h5 dfn, h6 dfn { font: inherit; }
41: img.extra { float: right; }
42: pre.idl { border: solid thin; background: #EEEEEE; color: black; padding: 0.5em 1em; }
43: pre.idl :link, pre.idl :visited { color: inherit; background: transparent; }
44: pre.css { border: solid thin; background: #FFFFEE; color: black; padding: 0.5em 1em; }
45: pre.css:first-line { color: #AAAA50; }
1.21 mike 46: dl.domintro { color: green; margin: 2em 0 2em 2em; padding: 0.5em 1em; border: none; background: #DDFFDD; }
1.12 mike 47: hr + dl.domintro, div.impl + dl.domintro { margin-top: 2.5em; margin-bottom: 1.5em; }
48: dl.domintro dt, dl.domintro dt * { color: black; text-decoration: none; }
49: dl.domintro dd { margin: 0.5em 0 1em 2em; padding: 0; }
50: dl.domintro dd p { margin: 0.5em 0; }
51: dl.switch { padding-left: 2em; }
52: dl.switch > dt { text-indent: -1.5em; }
53: dl.switch > dt:before { content: '\21AA'; padding: 0 0.5em 0 0; display: inline-block; width: 1em; text-align: right; line-height: 0.5em; }
54: dl.triple { padding: 0 0 0 1em; }
55: dl.triple dt, dl.triple dd { margin: 0; display: inline }
56: dl.triple dt:after { content: ':'; }
57: dl.triple dd:after { content: '\A'; white-space: pre; }
58: .diff-old { text-decoration: line-through; color: silver; background: transparent; }
59: .diff-chg, .diff-new { text-decoration: underline; color: green; background: transparent; }
60: a .diff-new { border-bottom: 1px blue solid; }
61:
62: h2 { page-break-before: always; }
63: h1, h2, h3, h4, h5, h6 { page-break-after: avoid; }
64: h1 + h2, hr + h2.no-toc { page-break-before: auto; }
65:
66: p > span:not([title=""]):not([class="XXX"]):not([class="impl"]), li > span:not([title=""]):not([class="XXX"]):not([class="impl"]) { border-bottom: solid #9999CC; }
67:
68: div.head { margin: 0 0 1em; padding: 1em 0 0 0; }
69: div.head p { margin: 0; }
70: div.head h1 { margin: 0; }
71: div.head .logo { float: right; margin: 0 1em; }
72: div.head .logo img { border: none } /* remove border from top image */
73: div.head dl { margin: 1em 0; }
74: div.head p.copyright, div.head p.alt { font-size: x-small; font-style: oblique; margin: 0; }
75:
76: body > .toc > li { margin-top: 1em; margin-bottom: 1em; }
77: body > .toc.brief > li { margin-top: 0.35em; margin-bottom: 0.35em; }
78: body > .toc > li > * { margin-bottom: 0.5em; }
79: body > .toc > li > * > li > * { margin-bottom: 0.25em; }
80: .toc, .toc li { list-style: none; }
81:
82: .brief { margin-top: 1em; margin-bottom: 1em; line-height: 1.1; }
83: .brief li { margin: 0; padding: 0; }
84: .brief li p { margin: 0; padding: 0; }
85:
86: .category-list { margin-top: -0.75em; margin-bottom: 1em; line-height: 1.5; }
87: .category-list::before { content: '\21D2\A0'; font-size: 1.2em; font-weight: 900; }
88: .category-list li { display: inline; }
89: .category-list li:not(:last-child)::after { content: ', '; }
90: .category-list li > span, .category-list li > a { text-transform: lowercase; }
91: .category-list li * { text-transform: none; } /* don't affect <code> nested in <a> */
92:
93: .XXX { color: #E50000; background: white; border: solid red; padding: 0.5em; margin: 1em 0; }
94: .XXX > :first-child { margin-top: 0; }
95: p .XXX { line-height: 3em; }
96: .annotation { border: solid thin black; background: #0C479D; color: white; position: relative; margin: 8px 0 20px 0; }
97: .annotation:before { position: absolute; left: 0; top: 0; width: 100%; height: 100%; margin: 6px -6px -6px 6px; background: #333333; z-index: -1; content: ''; }
98: .annotation :link, .annotation :visited { color: inherit; }
99: .annotation :link:hover, .annotation :visited:hover { background: transparent; }
100: .annotation span { border: none ! important; }
101: .note { color: green; background: transparent; font-family: sans-serif; }
102: .warning { color: red; background: transparent; }
103: .note, .warning { font-weight: bolder; font-style: italic; }
104: p.note, div.note { padding: 0.5em 2em; }
105: span.note { padding: 0 2em; }
106: .note p:first-child, .warning p:first-child { margin-top: 0; }
107: .note p:last-child, .warning p:last-child { margin-bottom: 0; }
108: .warning:before { font-style: normal; }
109: p.note:before { content: 'Note: '; }
110: p.warning:before { content: '\26A0 Warning! '; }
111:
112: .bookkeeping:before { display: block; content: 'Bookkeeping details'; font-weight: bolder; font-style: italic; }
113: .bookkeeping { font-size: 0.8em; margin: 2em 0; }
114: .bookkeeping p { margin: 0.5em 2em; display: list-item; list-style: square; }
115:
116: h4 { position: relative; z-index: 3; }
117: h4 + .element, h4 + div + .element { margin-top: -2.5em; padding-top: 2em; }
118: .element {
119: background: #EEEEFF;
120: color: black;
121: margin: 0 0 1em 0.15em;
122: padding: 0 1em 0.25em 0.75em;
123: border-left: solid #9999FF 0.25em;
124: position: relative;
125: z-index: 1;
126: }
127: .element:before {
128: position: absolute;
129: z-index: 2;
130: top: 0;
131: left: -1.15em;
132: height: 2em;
133: width: 0.9em;
134: background: #EEEEFF;
135: content: ' ';
136: border-style: none none solid solid;
137: border-color: #9999FF;
138: border-width: 0.25em;
139: }
140:
141: .example { display: block; color: #222222; background: #FCFCFC; border-left: double; margin-left: 2em; padding-left: 1em; }
142: td > .example:only-child { margin: 0 0 0 0.1em; }
143:
144: ul.domTree, ul.domTree ul { padding: 0 0 0 1em; margin: 0; }
145: ul.domTree li { padding: 0; margin: 0; list-style: none; position: relative; }
146: ul.domTree li li { list-style: none; }
147: ul.domTree li:first-child::before { position: absolute; top: 0; height: 0.6em; left: -0.75em; width: 0.5em; border-style: none none solid solid; content: ''; border-width: 0.1em; }
148: ul.domTree li:not(:last-child)::after { position: absolute; top: 0; bottom: -0.6em; left: -0.75em; width: 0.5em; border-style: none none solid solid; content: ''; border-width: 0.1em; }
149: ul.domTree span { font-style: italic; font-family: serif; }
150: ul.domTree .t1 code { color: purple; font-weight: bold; }
151: ul.domTree .t2 { font-style: normal; font-family: monospace; }
152: ul.domTree .t2 .name { color: black; font-weight: bold; }
153: ul.domTree .t2 .value { color: blue; font-weight: normal; }
154: ul.domTree .t3 code, .domTree .t4 code, .domTree .t5 code { color: gray; }
155: ul.domTree .t7 code, .domTree .t8 code { color: green; }
156: ul.domTree .t10 code { color: teal; }
157:
1.15 mike 158: body.dfnEnabled dfn { cursor: pointer; }
159: .dfnPanel {
160: display: inline;
161: position: absolute;
162: z-index: 10;
163: height: auto;
164: width: auto;
165: padding: 0.5em 0.75em;
166: font: small sans-serif, Droid Sans Fallback;
167: background: #DDDDDD;
168: color: black;
169: border: outset 0.2em;
170: }
171: .dfnPanel * { margin: 0; padding: 0; font: inherit; text-indent: 0; }
172: .dfnPanel :link, .dfnPanel :visited { color: black; }
173: .dfnPanel p { font-weight: bolder; }
174: .dfnPanel * + p { margin-top: 0.25em; }
175: .dfnPanel li { list-style-position: inside; }
176:
1.12 mike 177: #configUI { position: absolute; z-index: 20; top: 10em; right: 1em; width: 11em; font-size: small; }
178: #configUI p { margin: 0.5em 0; padding: 0.3em; background: #EEEEEE; color: black; border: inset thin; }
179: #configUI p label { display: block; }
180: #configUI #updateUI, #configUI .loginUI { text-align: center; }
181: #configUI input[type=button] { display: block; margin: auto; }
1.124 mike 182:
1.12 mike 183: </style><style type="text/css">
184:
185: .applies thead th > * { display: block; }
186: .applies thead code { display: block; }
187: .applies tbody th { whitespace: nowrap; }
188: .applies td { text-align: center; }
189: .applies .yes { background: yellow; }
190:
191: .matrix, .matrix td { border: none; text-align: right; }
192: .matrix { margin-left: 2em; }
193:
194: .dice-example { border-collapse: collapse; border-style: hidden solid solid hidden; border-width: thin; margin-left: 3em; }
195: .dice-example caption { width: 30em; font-size: smaller; font-style: italic; padding: 0.75em 0; text-align: left; }
196: .dice-example td, .dice-example th { border: solid thin; width: 1.35em; height: 1.05em; text-align: center; padding: 0; }
197:
198: #table-example-1 { border: solid thin; border-collapse: collapse; margin-left: 3em; }
199: #table-example-1 * { font-family: "Essays1743", serif; line-height: 1.01em; }
200: #table-example-1 caption { padding-bottom: 0.5em; }
201: #table-example-1 thead, #table-example-1 tbody { border: none; }
202: #table-example-1 th, #table-example-1 td { border: solid thin; }
203: #table-example-1 th { font-weight: normal; }
204: #table-example-1 td { border-style: none solid; vertical-align: top; }
205: #table-example-1 th { padding: 0.5em; vertical-align: middle; text-align: center; }
206: #table-example-1 tbody tr:first-child td { padding-top: 0.5em; }
207: #table-example-1 tbody tr:last-child td { padding-bottom: 1.5em; }
208: #table-example-1 tbody td:first-child { padding-left: 2.5em; padding-right: 0; width: 9em; }
209: #table-example-1 tbody td:first-child::after { content: leader(". "); }
210: #table-example-1 tbody td { padding-left: 2em; padding-right: 2em; }
211: #table-example-1 tbody td:first-child + td { width: 10em; }
212: #table-example-1 tbody td:first-child + td ~ td { width: 2.5em; }
213: #table-example-1 tbody td:first-child + td + td + td ~ td { width: 1.25em; }
214:
215: .apple-table-examples { border: none; border-collapse: separate; border-spacing: 1.5em 0em; width: 40em; margin-left: 3em; }
216: .apple-table-examples * { font-family: "Times", serif; }
217: .apple-table-examples td, .apple-table-examples th { border: none; white-space: nowrap; padding-top: 0; padding-bottom: 0; }
218: .apple-table-examples tbody th:first-child { border-left: none; width: 100%; }
219: .apple-table-examples thead th:first-child ~ th { font-size: smaller; font-weight: bolder; border-bottom: solid 2px; text-align: center; }
220: .apple-table-examples tbody th::after, .apple-table-examples tfoot th::after { content: leader(". ") }
221: .apple-table-examples tbody th, .apple-table-examples tfoot th { font: inherit; text-align: left; }
222: .apple-table-examples td { text-align: right; vertical-align: top; }
223: .apple-table-examples.e1 tbody tr:last-child td { border-bottom: solid 1px; }
224: .apple-table-examples.e1 tbody + tbody tr:last-child td { border-bottom: double 3px; }
225: .apple-table-examples.e2 th[scope=row] { padding-left: 1em; }
226: .apple-table-examples sup { line-height: 0; }
227:
1.13 mike 228: .details-example img { vertical-align: top; }
229:
1.25 mike 230: #named-character-references-table {
231: font-size: 0.6em;
232: column-width: 28em;
233: column-gap: 1em;
234: -moz-column-width: 28em;
235: -moz-column-gap: 1em;
236: -webkit-column-width: 28em;
237: -webkit-column-gap: 1em;
238: }
239: #named-character-references-table > table > tbody > tr > td:last-child { text-align: center; }
240: #named-character-references-table > table > tbody > tr > td:last-child:hover > span { position: absolute; top: auto; left: auto; margin-left: 0.5em; line-height: 1.2; font-size: 5em; border: outset; padding: 0.25em 0.5em; background: white; width: 1.25em; height: auto; text-align: center; }
241:
1.38 mike 242: .glyph.control { color: red; }
243:
1.41 mike 244: @font-face {
245: font-family: 'Essays1743';
246: src: url('http://www.whatwg.org/specs/web-apps/current-work/fonts/Essays1743.ttf');
247: }
248: @font-face {
249: font-family: 'Essays1743';
250: font-weight: bold;
251: src: url('http://www.whatwg.org/specs/web-apps/current-work/fonts/Essays1743-Bold.ttf');
252: }
253: @font-face {
254: font-family: 'Essays1743';
255: font-style: italic;
256: src: url('http://www.whatwg.org/specs/web-apps/current-work/fonts/Essays1743-Italic.ttf');
257: }
258: @font-face {
259: font-family: 'Essays1743';
260: font-style: italic;
261: font-weight: bold;
262: src: url('http://www.whatwg.org/specs/web-apps/current-work/fonts/Essays1743-BoldItalic.ttf');
263: }
264:
1.24 mike 265: </style><link href="data:text/css," id="complete" rel="stylesheet" title="Complete specification"><link href="data:text/css,.impl%20%7B%20display:%20none;%20%7D%0Ahtml%20%7B%20border:%20solid%20yellow;%20%7D%20.domintro:before%20%7B%20display:%20none;%20%7D" id="author" rel="alternate stylesheet" title="Author documentation only"><link href="data:text/css,.impl%20%7B%20background:%20%23FFEEEE;%20%7D%20.domintro:before%20%7B%20background:%20%23FFEEEE;%20%7D" id="highlight" rel="alternate stylesheet" title="Highlight implementation requirements"><script type="text/javascript">
1.12 mike 266: function getCookie(name) {
267: var params = location.search.substr(1).split("&");
268: for (var index = 0; index < params.length; index++) {
269: if (params[index] == name)
270: return "1";
271: var data = params[index].split("=");
272: if (data[0] == name)
273: return unescape(data[1]);
274: }
275: var cookies = document.cookie.split("; ");
276: for (var index = 0; index < cookies.length; index++) {
277: var data = cookies[index].split("=");
278: if (data[0] == name)
279: return unescape(data[1]);
280: }
281: return null;
282: }
283: function load(script) {
284: var e = document.createElement('script');
285: e.setAttribute('src', 'http://www.whatwg.org/specs/web-apps/current-work/' + script + '?' + encodeURIComponent(location) + '&' + encodeURIComponent(document.referrer));
286: document.body.appendChild(e);
287: }
288: function init() {
289: if (location.search == '?slow-browser')
290: return;
291: var configUI = document.createElement('div');
292: configUI.id = 'configUI';
293: document.body.appendChild(configUI);
294: // load('reviewer.js'); // would need cross-site XHR
295: if (document.getElementById('head'))
296: load('toc.js');
297:
298: // load('updater.js'); // would need cross-site XHR
1.13 mike 299: load('dfn.js'); // doesn't support split-out specs, but, oh well.
1.12 mike 300: // load('status.js'); // would need cross-site XHR
301: if (getCookie('profile') == '1')
302: document.getElementsByTagName('h2')[0].textContent += '; load: ' + (new Date() - loadTimer) + 'ms';
303: fixBrokenLink();
304: }
1.57 mike 305: </script><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css"><link href="style.css" rel="stylesheet"><script src="link-fixup.js"></script><link href="sections.html" rel="prev" title="4.4 Sections">
1.51 mike 306: <link href="Overview.html#contents" rel="index" title="Table of contents">
307: <link href="text-level-semantics.html" rel="next" title="4.6 Text-level semantics">
308: <body onload="fixBrokenLink(); init()"><div class="head" id="head">
1.12 mike 309: <p><a href="http://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72"></a></p>
1.39 mike 310:
1.132 ! mike 311: <h1>HTML5 (Edition for Web Authors)<span class="rcsrevision"> revision 1.4197</span></h1>
1.12 mike 312: </div><div>
1.51 mike 313: <a href="sections.html">← 4.4 Sections</a> –
314: <a href="Overview.html#contents">Table of contents</a> –
315: <a href="text-level-semantics.html">4.6 Text-level semantics →</a>
1.12 mike 316: <ol class="toc"><li><ol><li><a href="grouping-content.html#grouping-content"><span class="secno">4.5 </span>Grouping content</a>
1.51 mike 317: <ol><li><a href="grouping-content.html#the-p-element"><span class="secno">4.5.1 </span>The <code>p</code> element</a><li><a href="grouping-content.html#the-hr-element"><span class="secno">4.5.2 </span>The <code>hr</code> element</a><li><a href="grouping-content.html#the-pre-element"><span class="secno">4.5.3 </span>The <code>pre</code> element</a><li><a href="grouping-content.html#the-blockquote-element"><span class="secno">4.5.4 </span>The <code>blockquote</code> element</a><li><a href="grouping-content.html#the-ol-element"><span class="secno">4.5.5 </span>The <code>ol</code> element</a><li><a href="grouping-content.html#the-ul-element"><span class="secno">4.5.6 </span>The <code>ul</code> element</a><li><a href="grouping-content.html#the-li-element"><span class="secno">4.5.7 </span>The <code>li</code> element</a><li><a href="grouping-content.html#the-dl-element"><span class="secno">4.5.8 </span>The <code>dl</code> element</a><li><a href="grouping-content.html#the-dt-element"><span class="secno">4.5.9 </span>The <code>dt</code> element</a><li><a href="grouping-content.html#the-dd-element"><span class="secno">4.5.10 </span>The <code>dd</code> element</a><li><a href="grouping-content.html#the-figure-element"><span class="secno">4.5.11 </span>The <code>figure</code> element</a><li><a href="grouping-content.html#the-figcaption-element"><span class="secno">4.5.12 </span>The <code>figcaption</code> element</a><li><a href="grouping-content.html#the-div-element"><span class="secno">4.5.13 </span>The <code>div</code> element</a></ol></ol></ol></div>
1.12 mike 318:
1.51 mike 319: <h3 id="grouping-content"><span class="secno">4.5 </span>Grouping content</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><h4 id="the-p-element"><span class="secno">4.5.1 </span>The <dfn><code>p</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 320: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
321: <dd><a href="dnd.html#formatblock-candidate"><code title="">formatBlock</code> candidate</a>.</dd>
322: <dt>Contexts in which this element may be used:</dt>
323: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
324: <dt>Content model:</dt>
325: <dd><a href="content-models.html#phrasing-content">Phrasing content</a>.</dd>
326: <dt>Content attributes:</dt>
327: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
328: <dt>DOM interface:</dt>
329: <dd>
330: <pre class="idl">interface <dfn id="htmlparagraphelement">HTMLParagraphElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {};</pre>
331: </dd>
1.51 mike 332: </dl><p>The <code><a href="#the-p-element">p</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a
333: <a href="content-models.html#paragraph">paragraph</a>.<div class="example">
1.12 mike 334: <p>The following examples are conforming HTML fragments:</p>
335: <pre><p>The little kitten gently seated himself on a piece of
336: carpet. Later in his life, this would be referred to as the time the
337: cat sat on the mat.</p></pre>
338: <pre><fieldset>
339: <legend>Personal information</legend>
340: <p>
341: <label>Name: <input name="n"></label>
342: <label><input name="anon" type="checkbox"> Hide from other users</label>
343: </p>
344: <p><label>Address: <textarea name="a"></textarea></label></p>
345: </fieldset></pre>
346: <pre><p>There was once an example from Femley,<br>
347: Whose markup was of dubious quality.<br>
348: The validator complained,<br>
349: So the author was pained,<br>
350: To move the error from the markup to the rhyming.</p></pre>
351: </div><p>The <code><a href="#the-p-element">p</a></code> element should not be used when a more
1.51 mike 352: specific element is more appropriate.<div class="example">
1.12 mike 353:
354: <p>The following example is technically correct:</p>
355:
356: <pre><section>
357: <!-- ... -->
358: <p>Last modified: 2001-04-23</p>
359: <p>Author: fred@example.com</p>
360: </section></pre>
361:
362: <p>However, it would be better marked-up as:</p>
363:
364: <pre><section>
365: <!-- ... -->
366: <footer>Last modified: 2001-04-23</footer>
367: <address>Author: fred@example.com</address>
368: </section></pre>
369:
370: <p>Or:</p>
371:
372: <pre><section>
373: <!-- ... -->
374: <footer>
375: <p>Last modified: 2001-04-23</p>
376: <address>Author: fred@example.com</address>
377: </footer>
378: </section></pre>
379:
1.51 mike 380: </div><h4 id="the-hr-element"><span class="secno">4.5.2 </span>The <dfn><code>hr</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 381: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
382: <dt>Contexts in which this element may be used:</dt>
383: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
384: <dt>Content model:</dt>
385: <dd>Empty.</dd>
386: <dt>Content attributes:</dt>
387: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
388: <dt>DOM interface:</dt>
389: <dd>
390: <pre class="idl">interface <dfn id="htmlhrelement">HTMLHRElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {};</pre>
391: </dd>
1.51 mike 392: </dl><p>The <code><a href="#the-hr-element">hr</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a
1.12 mike 393: <a href="content-models.html#paragraph">paragraph</a>-level thematic break, e.g. a scene change in
394: a story, or a transition to another topic within a section of a
1.51 mike 395: reference book.<div class="example">
1.12 mike 396:
1.33 mike 397: <p>The following fictional extract from a project manual shows two
398: sections that use the <code><a href="#the-hr-element">hr</a></code> element to separate topics
399: within the section.</p>
400:
401: <pre><section>
402: <h1>Communication</h1>
403: <p>There are various methods of communication. This section
404: covers a few of the important ones used by the project.</p>
405: <strong><hr></strong>
406: <p>Communication stones seem to come in pairs and have mysterious
407: properties:</p>
408: <ul>
409: <li>They can transfer thoughts in two directions once activated
410: if used alone.</li>
411: <li>If used with another device, they can transfer one's
412: consciousness to another body.</li>
413: <li>If both stones are used with another device, the
414: consciousnesses switch bodies.</li>
415: </ul>
416: <strong><hr></strong>
417: <p>Radios use the electromagnetic spectrum in the meter range and
418: longer.</p>
419: <strong><hr></strong>
420: <p>Signal flares use the electromagnetic spectrum in the
421: nanometer range.</p>
422: </section>
423: <section>
424: <h1>Food</h1>
425: <p>All food at the project is rationed:</p>
426: <dl>
427: <dt>Potatoes</dt>
428: <dd>Two per day</dd>
429: <dt>Soup</dt>
430: <dd>One bowl per day</dd>
431: </dl>
432: <strong><hr></strong>
433: <p>Cooking is done by the chefs on a set rotation.</p>
434: </section></pre>
435:
436: <p>There is no need for an <code><a href="#the-hr-element">hr</a></code> element between the
437: sections themselves, since the <code><a href="sections.html#the-section-element">section</a></code> elements and
438: the <code><a href="sections.html#the-h1-h2-h3-h4-h5-and-h6-elements">h1</a></code> elements imply thematic changes themselves.</p>
439:
440: </div><div class="example">
441:
1.12 mike 442: <p>The following extract from <cite>Pandora's Star</cite> by Peter
443: F. Hamilton shows two paragraphs that precede a scene change and
444: the paragraph that follows it. The scene change, represented in the
445: printed book by a gap containing a solitary centered star between
446: the second and third paragraphs, is here represented using the
447: <code><a href="#the-hr-element">hr</a></code> element.</p>
448:
449: <!-- ISBN 1-4050-0020-1; bottom of page 14 -->
450:
451: <pre lang="en-GB"><p>Dudley was ninety-two, in his second life, and fast approaching
452: time for another rejuvenation. Despite his body having the physical
453: age of a standard fifty-year-old, the prospect of a long degrading
454: campaign within academia was one he regarded with dread. For a
455: supposedly advanced civilization, the Intersolar Commonwearth could be
456: appallingly backward at times, not to mention cruel.</p>
457: <p><i>Maybe it won't be that bad</i>, he told himself. The lie was
458: comforting enough to get him through the rest of the night's
459: shift.</p>
460: <strong><hr></strong>
461: <p>The Carlton AllLander drove Dudley home just after dawn. Like the
462: astronomer, the vehicle was old and worn, but perfectly capable of
463: doing its job. It had a cheap diesel engine, common enough on a
464: semi-frontier world like Gralmond, although its drive array was a
465: thoroughly modern photoneural processor. With its high suspension and
466: deep-tread tyres it could plough along the dirt track to the
467: observatory in all weather and seasons, including the metre-deep snow
468: of Gralmond's winters.</p></pre>
469:
1.34 mike 470: </div><p class="note">The <code><a href="#the-hr-element">hr</a></code> element does not affect the
1.51 mike 471: document's <a href="sections.html#outline">outline</a>.<h4 id="the-pre-element"><span class="secno">4.5.3 </span>The <dfn><code>pre</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 472: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
473: <dd><a href="dnd.html#formatblock-candidate"><code title="">formatBlock</code> candidate</a>.</dd>
474: <dt>Contexts in which this element may be used:</dt>
475: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
476: <dt>Content model:</dt>
477: <dd><a href="content-models.html#phrasing-content">Phrasing content</a>.</dd>
478: <dt>Content attributes:</dt>
479: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
480: <dt>DOM interface:</dt>
481: <dd>
482: <pre class="idl">interface <dfn id="htmlpreelement">HTMLPreElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {};</pre>
483: </dd>
1.51 mike 484: </dl><p>The <code><a href="#the-pre-element">pre</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a block of
1.12 mike 485: preformatted text, in which structure is represented by typographic
1.51 mike 486: conventions rather than by elements.<p class="note">In <a href="syntax.html#syntax">the HTML syntax</a>, a leading
1.12 mike 487: newline character immediately following the <code><a href="#the-pre-element">pre</a></code> element
1.51 mike 488: start tag is stripped.<p>Some examples of cases where the <code><a href="#the-pre-element">pre</a></code> element could
489: be used:<ul><li>Including an e-mail, with paragraphs indicated by blank lines,
1.12 mike 490: lists indicated by lines prefixed with a bullet, and so on.</li>
491:
492: <li>Including fragments of computer code, with structure indicated
493: according to the conventions of that language.</li>
494:
495: <li>Displaying ASCII art.</li>
496:
497: </ul><p class="note">Authors are encouraged to consider how preformatted
498: text will be experienced when the formatting is lost, as will be the
499: case for users of speech synthesizers, braille displays, and the
500: like. For cases like ASCII art, it is likely that an alternative
501: presentation, such as a textual description, would be more
1.51 mike 502: universally accessible to the readers of the document.<p>To represent a block of computer code, the <code><a href="#the-pre-element">pre</a></code>
1.12 mike 503: element can be used with a <code><a href="text-level-semantics.html#the-code-element">code</a></code> element; to represent a
504: block of computer output the <code><a href="#the-pre-element">pre</a></code> element can be used
505: with a <code><a href="text-level-semantics.html#the-samp-element">samp</a></code> element. Similarly, the <code><a href="text-level-semantics.html#the-kbd-element">kbd</a></code>
506: element can be used within a <code><a href="#the-pre-element">pre</a></code> element to indicate
1.51 mike 507: text that the user is to enter.<div class="example">
1.12 mike 508:
509: <p>In the following snippet, a sample of computer code is
510: presented.</p>
511:
512: <pre><p>This is the <code>Panel</code> constructor:</p>
513: <pre><code>function Panel(element, canClose, closeHandler) {
514: this.element = element;
515: this.canClose = canClose;
516: this.closeHandler = function () { if (closeHandler) closeHandler() };
517: }</code></pre></pre>
518:
519: </div><div class="example">
520:
521: <p>In the following snippet, <code><a href="text-level-semantics.html#the-samp-element">samp</a></code> and <code><a href="text-level-semantics.html#the-kbd-element">kbd</a></code>
522: elements are mixed in the contents of a <code><a href="#the-pre-element">pre</a></code> element to
523: show a session of Zork I.</p>
524:
525: <pre><pre><samp>You are in an open field west of a big white house with a boarded
526: front door.
527: There is a small mailbox here.
528:
529: ></samp> <kbd>open mailbox</kbd>
530:
531: <samp>Opening the mailbox reveals:
532: A leaflet.
533:
534: ></samp></pre></pre>
535:
536: </div><div class="example">
537:
538: <p>The following shows a contemporary poem that uses the
539: <code><a href="#the-pre-element">pre</a></code> element to preserve its unusual formatting, which
540: forms an intrinsic part of the poem itself.</p>
541:
542: <pre><pre> maxling
543:
544: it is with a heart
545: heavy
546:
547: that i admit loss of a feline
548: so loved
549:
550: a friend lost to the
551: unknown
552: (night)
553:
554: ~cdr 11dec07</pre></pre>
555:
1.51 mike 556: </div><h4 id="the-blockquote-element"><span class="secno">4.5.4 </span>The <dfn><code>blockquote</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 557: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
558: <dd><a href="sections.html#sectioning-root">Sectioning root</a>.</dd>
559: <dd><a href="dnd.html#formatblock-candidate"><code title="">formatBlock</code> candidate</a>.</dd>
560: <dt>Contexts in which this element may be used:</dt>
561: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
562: <dt>Content model:</dt>
563: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
564: <dt>Content attributes:</dt>
565: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
566: <dd><code title="attr-blockquote-cite"><a href="#attr-blockquote-cite">cite</a></code></dd>
567: <dt>DOM interface:</dt>
568: <dd>
569: <pre class="idl">interface <dfn id="htmlquoteelement">HTMLQuoteElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {
1.51 mike 570: attribute DOMString <a class="full-spec-link" href="http://dev.w3.org/html5/spec/grouping-content.html#dom-quote-cite" title='Read about this "cite" reference in the full HTML5 spec.'>cite</a>;
1.12 mike 571: };</pre>
572: <p class="note">The <code><a href="#htmlquoteelement">HTMLQuoteElement</a></code> interface is
573: also used by the <code><a href="text-level-semantics.html#the-q-element">q</a></code> element.</p>
574: </dd>
1.51 mike 575: </dl><p>The <code><a href="#the-blockquote-element">blockquote</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a
576: section that is quoted from another source.<p>Content inside a <code><a href="#the-blockquote-element">blockquote</a></code> must be quoted from
1.35 mike 577: another source, whose address, if it has one, may be cited in the
1.12 mike 578: <dfn id="attr-blockquote-cite" title="attr-blockquote-cite"><code>cite</code></dfn>
1.51 mike 579: attribute.<p>If the <code title="attr-blockquote-cite"><a href="#attr-blockquote-cite">cite</a></code> attribute
1.32 mike 580: is present, it must be a <a href="urls.html#valid-url-potentially-surrounded-by-spaces">valid URL potentially surrounded by
1.51 mike 581: spaces</a>. <div class="example">
1.12 mike 582:
583: <p>This next example shows the use of <code><a href="text-level-semantics.html#the-cite-element">cite</a></code> alongside
584: <code><a href="#the-blockquote-element">blockquote</a></code>:</p>
585:
586: <pre><p>His next piece was the aptly named <cite>Sonnet 130</cite>:</p>
587: <blockquote cite="http://quotes.example.org/s/sonnet130.html">
588: <p>My mistress' eyes are nothing like the sun,<br>
589: Coral is far more red, than her lips red,<br>
590: ...</pre>
591:
592: </div><div class="example">
593:
594: <p>This example shows how a forum post could use
595: <code><a href="#the-blockquote-element">blockquote</a></code> to show what post a user is replying
596: to. The <code><a href="sections.html#the-article-element">article</a></code> element is used for each post, to mark
597: up the threading.</p>
598:
599: <pre><article>
600: <h1><a href="http://bacon.example.com/?blog=109431">Bacon on a crowbar</a></h1>
601: <article>
602: <header><strong>t3yw</strong> 12 points 1 hour ago</header>
603: <p>I bet a narwhal would love that.</p>
604: <footer><a href="?pid=29578">permalink</a></footer>
605: <article>
606: <header><strong>greg</strong> 8 points 1 hour ago</header>
607: <blockquote><p>I bet a narwhal would love that.</p></blockquote>
608: <p>Dude narwhals don't eat bacon.</p>
609: <footer><a href="?pid=29579">permalink</a></footer>
610: <article>
611: <header><strong>t3yw</strong> 15 points 1 hour ago</header>
612: <blockquote>
613: <blockquote><p>I bet a narwhal would love that.</p></blockquote>
614: <p>Dude narwhals don't eat bacon.</p>
615: </blockquote>
616: <p>Next thing you'll be saying they don't get capes and wizard
617: hats either!</p>
618: <footer><a href="?pid=29580">permalink</a></footer>
619: <article>
620: <article>
621: <header><strong>boing</strong> -5 points 1 hour ago</header>
622: <p>narwhals are worse than ceiling cat</p>
623: <footer><a href="?pid=29581">permalink</a></footer>
624: </article>
625: </article>
626: </article>
627: </article>
628: <article>
629: <header><strong>fred</strong> 1 points 23 minutes ago</header>
630: <blockquote><p>I bet a narwhal would love that.</p></blockquote>
631: <p>I bet they'd love to peel a banana too.</p>
632: <footer><a href="?pid=29582">permalink</a></footer>
633: </article>
634: </article>
635: </article></pre>
636:
1.16 mike 637: </div><p class="note"><a href="links.html#conversations">Examples of how to
1.12 mike 638: represent a conversation</a> are shown in a later section; it is not
639: appropriate to use the <code><a href="text-level-semantics.html#the-cite-element">cite</a></code> and <code><a href="#the-blockquote-element">blockquote</a></code>
1.51 mike 640: elements for this purpose.<h4 id="the-ol-element"><span class="secno">4.5.5 </span>The <dfn><code>ol</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 641: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
642: <dt>Contexts in which this element may be used:</dt>
643: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
644: <dt>Content model:</dt>
645: <dd>Zero or more <code><a href="#the-li-element">li</a></code> elements.</dd>
646: <dt>Content attributes:</dt>
647: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
648: <dd><code title="attr-ol-reversed"><a href="#attr-ol-reversed">reversed</a></code></dd>
649: <dd><code title="attr-ol-start"><a href="#attr-ol-start">start</a></code></dd>
650: <dt>DOM interface:</dt>
651: <dd>
652: <pre class="idl">interface <dfn id="htmlolistelement">HTMLOListElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {
1.51 mike 653: attribute boolean <a class="full-spec-link" href="http://dev.w3.org/html5/spec/grouping-content.html#dom-ol-reversed" title='Read about this "reversed" reference in the full HTML5 spec.'>reversed</a>;
654: attribute long <a class="full-spec-link" href="http://dev.w3.org/html5/spec/grouping-content.html#dom-ol-start" title='Read about this "start" reference in the full HTML5 spec.'>start</a>;
1.12 mike 655: };</pre>
656: </dd>
1.51 mike 657: </dl><p>The <code><a href="#the-ol-element">ol</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a list of
1.12 mike 658: items, where the items have been intentionally ordered, such that
1.51 mike 659: changing the order would change the meaning of the document.<p>The items of the list are the <code><a href="#the-li-element">li</a></code> element child nodes
660: of the <code><a href="#the-ol-element">ol</a></code> element, in <a href="infrastructure.html#tree-order">tree order</a>.<p>The <dfn id="attr-ol-reversed" title="attr-ol-reversed"><code>reversed</code></dfn>
1.12 mike 661: attribute is a <a href="common-microsyntaxes.html#boolean-attribute">boolean attribute</a>. If present, it
662: indicates that the list is a descending list (..., 3, 2, 1). If the
663: attribute is omitted, the list is an ascending list (1, 2, 3,
1.51 mike 664: ...).<p>The <dfn id="attr-ol-start" title="attr-ol-start"><code>start</code></dfn>
1.12 mike 665: attribute, if present, must be a <a href="common-microsyntaxes.html#valid-integer">valid integer</a> giving
666: the ordinal value of the first list item.</p><!-- v2: resuming numbering of lists from previous lists? --><div class="example">
667:
668: <p>The following markup shows a list where the order matters, and
669: where the <code><a href="#the-ol-element">ol</a></code> element is therefore appropriate. Compare
670: this list to the equivalent list in the <code><a href="#the-ul-element">ul</a></code> section to
671: see an example of the same items using the <code><a href="#the-ul-element">ul</a></code>
672: element.</p>
673:
674: <pre><p>I have lived in the following countries (given in the order of when
675: I first lived there):</p>
676: <ol>
677: <li>Switzerland
678: <li>United Kingdom
679: <li>United States
680: <li>Norway
681: </ol></pre>
682:
683: <p>Note how changing the order of the list changes the meaning of
684: the document. In the following example, changing the relative order
685: of the first two items has changed the birthplace of the
686: author:</p>
687:
688: <pre><p>I have lived in the following countries (given in the order of when
689: I first lived there):</p>
690: <ol>
691: <li>United Kingdom
692: <li>Switzerland
693: <li>United States
694: <li>Norway
695: </ol></pre>
696:
1.51 mike 697: </div><h4 id="the-ul-element"><span class="secno">4.5.6 </span>The <dfn><code>ul</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 698: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
699: <dt>Contexts in which this element may be used:</dt>
700: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
701: <dt>Content model:</dt>
702: <dd>Zero or more <code><a href="#the-li-element">li</a></code> elements.</dd>
703: <dt>Content attributes:</dt>
704: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
705: <dt>DOM interface:</dt>
706: <dd>
707: <pre class="idl">interface <dfn id="htmlulistelement">HTMLUListElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {};</pre>
708: </dd>
1.51 mike 709: </dl><p>The <code><a href="#the-ul-element">ul</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a list of
710: items, where the order of the items is not important — that
1.12 mike 711: is, where changing the order would not materially change the meaning
1.51 mike 712: of the document.<p>The items of the list are the <code><a href="#the-li-element">li</a></code> element child nodes
713: of the <code><a href="#the-ul-element">ul</a></code> element.<div class="example">
1.12 mike 714:
715: <p>The following markup shows a list where the order does not
716: matter, and where the <code><a href="#the-ul-element">ul</a></code> element is therefore
717: appropriate. Compare this list to the equivalent list in the
718: <code><a href="#the-ol-element">ol</a></code> section to see an example of the same items using
719: the <code><a href="#the-ol-element">ol</a></code> element.</p>
720:
721: <pre><p>I have lived in the following countries:</p>
722: <ul>
723: <li>Norway
724: <li>Switzerland
725: <li>United Kingdom
726: <li>United States
727: </ul></pre>
728:
729: <p>Note that changing the order of the list does not change the
730: meaning of the document. The items in the snippet above are given
731: in alphabetical order, but in the snippet below they are given in
732: order of the size of their current account balance in 2007, without
733: changing the meaning of the document whatsoever:</p>
734:
735: <pre><p>I have lived in the following countries:</p>
736: <ul>
737: <li>Switzerland
738: <li>Norway
739: <li>United Kingdom
740: <li>United States
741: </ul></pre>
742:
1.51 mike 743: </div><h4 id="the-li-element"><span class="secno">4.5.7 </span>The <dfn><code>li</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 744: <dd>None.</dd>
745: <dt>Contexts in which this element may be used:</dt>
746: <dd>Inside <code><a href="#the-ol-element">ol</a></code> elements.</dd>
747: <dd>Inside <code><a href="#the-ul-element">ul</a></code> elements.</dd>
748: <dd>Inside <code><a href="interactive-elements.html#menus">menu</a></code> elements.</dd>
749: <dt>Content model:</dt>
750: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
751: <dt>Content attributes:</dt>
752: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
753: <dd>If the element is a child of an <code><a href="#the-ol-element">ol</a></code> element: <code title="attr-li-value"><a href="#attr-li-value">value</a></code></dd>
754: <dt>DOM interface:</dt>
755: <dd>
756: <pre class="idl">interface <dfn id="htmllielement">HTMLLIElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {
1.51 mike 757: attribute long <a class="full-spec-link" href="http://dev.w3.org/html5/spec/grouping-content.html#dom-li-value" title='Read about this "value" reference in the full HTML5 spec.'>value</a>;
1.12 mike 758: };</pre>
759: </dd>
1.51 mike 760: </dl><p>The <code><a href="#the-li-element">li</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a list
1.12 mike 761: item. If its parent element is an <code><a href="#the-ol-element">ol</a></code>, <code><a href="#the-ul-element">ul</a></code>,
762: or <code><a href="interactive-elements.html#menus">menu</a></code> element, then the element is an item of the
763: parent element's list, as defined for those elements. Otherwise, the
764: list item has no defined list-related relationship to any other
1.51 mike 765: <code><a href="#the-li-element">li</a></code> element.<p>The <dfn id="attr-li-value" title="attr-li-value"><code>value</code></dfn>
1.12 mike 766: attribute, if present, must be a <a href="common-microsyntaxes.html#valid-integer">valid integer</a> giving
1.51 mike 767: the ordinal value of the list item.<div class="example">
1.12 mike 768: <p>The following example, the top ten movies are listed (in reverse
769: order). Note the way the list is given a title by using a
1.17 mike 770: <code><a href="#the-figure-element">figure</a></code> element and its <code><a href="#the-figcaption-element">figcaption</a></code>
1.14 mike 771: element.</p>
1.12 mike 772: <pre><figure>
1.14 mike 773: <figcaption>The top 10 movies of all time</figcaption>
774: <ol>
775: <li value="10"><cite>Josie and the Pussycats</cite>, 2001</li>
1.58 mike 776: <li value="9"><cite lang="sh">Црна мачка, бели мачор</cite>, 1998</li>
1.14 mike 777: <li value="8"><cite>A Bug's Life</cite>, 1998</li>
778: <li value="7"><cite>Toy Story</cite>, 1995</li>
779: <li value="6"><cite>Monsters, Inc</cite>, 2001</li>
780: <li value="5"><cite>Cars</cite>, 2006</li>
781: <li value="4"><cite>Toy Story 2</cite>, 1999</li>
782: <li value="3"><cite>Finding Nemo</cite>, 2003</li>
783: <li value="2"><cite>The Incredibles</cite>, 2004</li>
784: <li value="1"><cite>Ratatouille</cite>, 2007</li>
785: </ol>
1.12 mike 786: </figure></pre>
787:
788: <p>The markup could also be written as follows, using the <code title="attr-ol-reversed"><a href="#attr-ol-reversed">reversed</a></code> attribute on the
789: <code><a href="#the-ol-element">ol</a></code> element:</p>
790:
791: <pre><figure>
1.14 mike 792: <figcaption>The top 10 movies of all time</figcaption>
793: <ol reversed>
794: <li><cite>Josie and the Pussycats</cite>, 2001</li>
1.58 mike 795: <li><cite lang="sh">Црна мачка, бели мачор</cite>, 1998</li>
1.14 mike 796: <li><cite>A Bug's Life</cite>, 1998</li>
797: <li><cite>Toy Story</cite>, 1995</li>
798: <li><cite>Monsters, Inc</cite>, 2001</li>
799: <li><cite>Cars</cite>, 2006</li>
800: <li><cite>Toy Story 2</cite>, 1999</li>
801: <li><cite>Finding Nemo</cite>, 2003</li>
802: <li><cite>The Incredibles</cite>, 2004</li>
803: <li><cite>Ratatouille</cite>, 2007</li>
804: </ol>
1.12 mike 805: </figure></pre>
806: </div><p class="note">If the <code><a href="#the-li-element">li</a></code> element is the child of a
807: <code><a href="interactive-elements.html#menus">menu</a></code> element and itself has a child that defines a
808: <a href="commands.html#concept-command" title="concept-command">command</a>, then the
1.51 mike 809: <code><a href="#the-li-element">li</a></code> element will match the <code title="selector-enabled"><a class="full-spec-link" href="http://dev.w3.org/html5/spec/links.html#selector-enabled" title='Read about this ":enabled" reference in the full HTML5 spec.'>:enabled</a></code> and <code title="selector-disabled"><a class="full-spec-link" href="http://dev.w3.org/html5/spec/links.html#selector-disabled" title='Read about this ":disabled" reference in the full HTML5 spec.'>:disabled</a></code> pseudo-classes in the
810: same way as the first such child element does.<h4 id="the-dl-element"><span class="secno">4.5.8 </span>The <dfn><code>dl</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 811: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
812: <dt>Contexts in which this element may be used:</dt>
813: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
814: <dt>Content model:</dt>
815: <dd>Zero or more groups each consisting of one or more
816: <code><a href="#the-dt-element">dt</a></code> elements followed by one or more <code><a href="#the-dd-element">dd</a></code>
817: elements.</dd>
818: <dt>Content attributes:</dt>
819: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
820: <dt>DOM interface:</dt>
821: <dd>
822: <pre class="idl">interface <dfn id="htmldlistelement">HTMLDListElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {};</pre>
823: </dd>
1.51 mike 824: </dl><p>The <code><a href="#the-dl-element">dl</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> an
1.12 mike 825: association list consisting of zero or more name-value groups (a
826: description list). Each group must consist of one or more names
827: (<code><a href="#the-dt-element">dt</a></code> elements) followed by one or more values
828: (<code><a href="#the-dd-element">dd</a></code> elements). Within a single <code><a href="#the-dl-element">dl</a></code> element,
829: there should not be more than one <code><a href="#the-dt-element">dt</a></code> element for each
1.51 mike 830: name.<p>Name-value groups may be terms and definitions, metadata topics
831: and values, or any other groups of name-value data.<p>The values within a group are alternatives; multiple paragraphs
1.12 mike 832: forming part of the same value must all be given within the same
1.51 mike 833: <code><a href="#the-dd-element">dd</a></code> element.<p>The order of the list of groups, and of the names and values
834: within each group, may be significant.<div class="example">
1.12 mike 835: <p>In the following example, one entry ("Authors") is linked to two
836: values ("John" and "Luke").</p>
837: <pre><dl>
838: <dt> Authors
839: <dd> John
840: <dd> Luke
841: <dt> Editor
842: <dd> Frank
843: </dl></pre>
844: </div><div class="example">
845: <p>In the following example, one definition is linked to two
846: terms.</p>
847: <pre><dl>
848: <dt lang="en-US"> <dfn>color</dfn> </dt>
849: <dt lang="en-GB"> <dfn>colour</dfn> </dt>
850: <dd> A sensation which (in humans) derives from the ability of
851: the fine structure of the eye to distinguish three differently
852: filtered analyses of a view. </dd>
853: </dl></pre>
854: </div><div class="example">
855: <p>The following example illustrates the use of the <code><a href="#the-dl-element">dl</a></code>
856: element to mark up metadata of sorts. At the end of the example,
857: one group has two metadata labels ("Authors" and "Editors") and two
858: values ("Robert Rothman" and "Daniel Jackson").</p>
859: <pre><dl>
860: <dt> Last modified time </dt>
861: <dd> 2004-12-23T23:33Z </dd>
862: <dt> Recommended update interval </dt>
863: <dd> 60s </dd>
864: <dt> Authors </dt>
865: <dt> Editors </dt>
866: <dd> Robert Rothman </dd>
867: <dd> Daniel Jackson </dd>
868: </dl></pre>
869: </div><div class="example">
870:
871: <p>The following example shows the <code><a href="#the-dl-element">dl</a></code> element used to
872: give a set of instructions. The order of the instructions here is
873: important (in the other examples, the order of the blocks was not
874: important).</p>
875:
876: <pre><p>Determine the victory points as follows (use the
877: first matching case):</p>
878: <dl>
879: <dt> If you have exactly five gold coins </dt>
880: <dd> You get five victory points </dd>
881: <dt> If you have one or more gold coins, and you have one or more silver coins </dt>
882: <dd> You get two victory points </dd>
883: <dt> If you have one or more silver coins </dt>
884: <dd> You get one victory point </dd>
885: <dt> Otherwise </dt>
886: <dd> You get no victory points </dd>
887: </dl></pre>
888: </div><div class="example">
889: <p>The following snippet shows a <code><a href="#the-dl-element">dl</a></code> element being used
890: as a glossary. Note the use of <code><a href="text-level-semantics.html#the-dfn-element">dfn</a></code> to indicate the
891: word being defined.</p>
892: <pre><dl>
893: <dt><dfn>Apartment</dfn>, n.</dt>
894: <dd>An execution context grouping one or more threads with one or
895: more COM objects.</dd>
896: <dt><dfn>Flat</dfn>, n.</dt>
897: <dd>A deflated tire.</dd>
898: <dt><dfn>Home</dfn>, n.</dt>
899: <dd>The user's login directory.</dd>
900: </dl></pre>
901: </div><p class="note">The <code><a href="#the-dl-element">dl</a></code> element is inappropriate for
1.16 mike 902: marking up dialogue. <a href="links.html#conversations">Examples of how to
1.51 mike 903: mark up dialogue</a> are shown below.<h4 id="the-dt-element"><span class="secno">4.5.9 </span>The <dfn><code>dt</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 904: <dd>None.</dd>
905: <dt>Contexts in which this element may be used:</dt>
906: <dd>Before <code><a href="#the-dd-element">dd</a></code> or <code><a href="#the-dt-element">dt</a></code> elements inside <code><a href="#the-dl-element">dl</a></code> elements.</dd>
907: <dt>Content model:</dt>
1.31 mike 908: <dd><a href="content-models.html#phrasing-content">Phrasing content</a>.</dd>
1.12 mike 909: <dt>Content attributes:</dt>
910: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
911: <dt>DOM interface:</dt>
912: <dd>Uses <code><a href="elements.html#htmlelement">HTMLElement</a></code>.</dd>
1.51 mike 913: </dl><p>The <code><a href="#the-dt-element">dt</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> the term, or
1.14 mike 914: name, part of a term-description group in a description list
1.51 mike 915: (<code><a href="#the-dl-element">dl</a></code> element).<p class="note">The <code><a href="#the-dt-element">dt</a></code> element itself, when used in a
1.12 mike 916: <code><a href="#the-dl-element">dl</a></code> element, does not indicate that its contents are a
917: term being defined, but this can be indicated using the
1.51 mike 918: <code><a href="text-level-semantics.html#the-dfn-element">dfn</a></code> element.<div class="example">
1.23 mike 919:
920: <p>This example shows a list of frequently asked questions (a FAQ)
921: marked up using the <code><a href="#the-dt-element">dt</a></code> element for questions and the
922: <code><a href="#the-dd-element">dd</a></code> element for answers.</p>
923:
924: <pre><article>
925: <h1>FAQ</h1>
926: <dl>
927: <dt>What do we want?</dt>
928: <dd>Our data.</dd>
929: <dt>When do we want it?</dt>
930: <dd>Now.</dd>
931: <dt>Where is it?</dt>
932: <dd>We are not sure.</dd>
933: </dl>
934: </article></pre>
935:
1.51 mike 936: </div><h4 id="the-dd-element"><span class="secno">4.5.10 </span>The <dfn><code>dd</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 937: <dd>None.</dd>
938: <dt>Contexts in which this element may be used:</dt>
939: <dd>After <code><a href="#the-dt-element">dt</a></code> or <code><a href="#the-dd-element">dd</a></code> elements inside <code><a href="#the-dl-element">dl</a></code> elements.</dd>
940: <dt>Content model:</dt>
941: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
942: <dt>Content attributes:</dt>
943: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
944: <dt>DOM interface:</dt>
945: <dd>Uses <code><a href="elements.html#htmlelement">HTMLElement</a></code>.</dd>
1.51 mike 946: </dl><p>The <code><a href="#the-dd-element">dd</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> the
1.12 mike 947: description, definition, or value, part of a term-description group
1.51 mike 948: in a description list (<code><a href="#the-dl-element">dl</a></code> element).<div class="example">
1.12 mike 949:
950: <p>A <code><a href="#the-dl-element">dl</a></code> can be used to define a vocabulary list, like
951: in a dictionary. In the following example, each entry, given by a
952: <code><a href="#the-dt-element">dt</a></code> with a <code><a href="text-level-semantics.html#the-dfn-element">dfn</a></code>, has several
953: <code><a href="#the-dd-element">dd</a></code>s, showing the various parts of the definition.</p>
954:
955: <!-- the actual pronunciations below are nonsense. -->
956: <pre><dl>
957: <dt><dfn>happiness</dfn></dt>
1.51 mike 958: <dd class="pronunciation">/'hæ p. nes/</dd>
1.12 mike 959: <dd class="part-of-speech"><i><abbr>n.</abbr></i></dd>
960: <dd>The state of being happy.</dd>
961: <dd>Good fortune; success. <q>Oh <b>happiness</b>! It worked!</q></dd>
962: <dt><dfn>rejoice</dfn></dt>
963: <dd class="pronunciation">/ri jois'/</dd>
964: <dd><i class="part-of-speech"><abbr>v.intr.</abbr></i> To be delighted oneself.</dd>
965: <dd><i class="part-of-speech"><abbr>v.tr.</abbr></i> To cause one to be delighted.</dd>
966: </dl></pre>
1.51 mike 967: </div><h4 id="the-figure-element"><span class="secno">4.5.11 </span>The <dfn><code>figure</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.17 mike 968: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
969: <dd><a href="sections.html#sectioning-root">Sectioning root</a>.</dd>
970: <dt>Contexts in which this element may be used:</dt>
971: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
972: <dt>Content model:</dt>
1.19 mike 973: <dd>Either: One <code><a href="#the-figcaption-element">figcaption</a></code> element followed by <a href="content-models.html#flow-content">flow content</a>.</dd>
974: <dd>Or: <a href="content-models.html#flow-content">Flow content</a> followed by one <code><a href="#the-figcaption-element">figcaption</a></code> element.</dd>
975: <dd>Or: <a href="content-models.html#flow-content">Flow content</a>.</dd>
1.17 mike 976: <dt>Content attributes:</dt>
977: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
978: <dt>DOM interface:</dt>
979: <dd>Uses <code><a href="elements.html#htmlelement">HTMLElement</a></code>.</dd>
1.51 mike 980: </dl><!-- v2: Add a <credit> element for photo credits --><p>The <code><a href="#the-figure-element">figure</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> some
1.17 mike 981: <a href="content-models.html#flow-content">flow content</a>, optionally with a caption, that is
982: self-contained and is typically referenced as a single unit from the
1.51 mike 983: main flow of the document.<p>The element can thus be used to annotate illustrations, diagrams,
1.17 mike 984: photos, code listings, etc, that are referred to from the main
985: content of the document, but that could, without affecting the flow
986: of the document, be moved away from that primary content, e.g. to
1.51 mike 987: the side of the page, to dedicated pages, or to an appendix.<p>The <code><a href="#the-figcaption-element">figcaption</a></code>
1.17 mike 988: element child of the element, if any, represents the caption of the
989: <code><a href="#the-figure-element">figure</a></code> element's contents. If there is no child
1.51 mike 990: <code><a href="#the-figcaption-element">figcaption</a></code> element, then there is no caption.<div class="example">
1.17 mike 991:
992: <p>This example shows the <code><a href="#the-figure-element">figure</a></code> element to mark up a
993: code listing.</p>
994:
995: <pre><p>In <a href="#l4">listing 4</a> we see the primary core interface
996: API declaration.</p>
997: <figure id="l4">
998: <figcaption>Listing 4. The primary core interface API declaration.</figcaption>
999: <pre><code>interface PrimaryCore {
1000: boolean verifyDataLine();
1001: void sendData(in sequence&lt;byte> data);
1002: void initSelfDestruct();
1003: }</code></pre>
1004: </figure>
1005: <p>The API is designed to use UTF-8.</p></pre>
1006:
1007: </div><div class="example">
1008:
1009: <p>Here we see a <code><a href="#the-figure-element">figure</a></code> element to mark up a
1010: photo.</p>
1011:
1012: <pre><figure>
1013: <img src="bubbles-work.jpeg"
1014: alt="Bubbles, sitting in his office chair, works on his
1015: latest project intently.">
1016: <figcaption>Bubbles at work</figcaption>
1017: </figure></pre>
1018:
1019: </div><div class="example">
1020:
1021: <p>In this example, we see an image that is <em>not</em>
1022: a figure, as well as an image and a video that are.</p>
1023:
1024: <pre><h2>Malinko's comics</h2>
1025:
1026: <p>This case centered on some sort of "intellectual property"
1027: infringement related to a comic (see Exhibit A). The suit started
1028: after a trailer ending with these words:
1029:
1030: <blockquote>
1031: <img src="promblem-packed-action.png" alt="ROUGH COPY! Promblem-Packed Action!">
1032: </blockquote>
1033:
1034: <p>...was aired. A lawyer, armed with a Bigger Notebook, launched a
1035: preemptive strike using snowballs. A complete copy of the trailer is
1036: included with Exhibit B.
1037:
1038: <figure>
1039: <img src="ex-a.png" alt="Two squiggles on a dirty piece of paper.">
1040: <figcaption>Exhibit A. The alleged <cite>rough copy</cite> comic.</figcaption>
1041: </figure>
1042:
1043: <figure>
1044: <video src="ex-b.mov"></video>
1045: <figcaption>Exhibit B. The <cite>Rough Copy</cite> trailer.</figcaption>
1046: </figure>
1047:
1048: <p>The case was resolved out of court.</pre>
1049:
1050: </div><div class="example">
1051:
1052: <p>Here, a part of a poem is marked up using
1053: <code><a href="#the-figure-element">figure</a></code>.</p>
1054:
1055: <pre><figure>
1056: <p>'Twas brillig, and the slithy toves<br>
1057: Did gyre and gimble in the wabe;<br>
1058: All mimsy were the borogoves,<br>
1059: And the mome raths outgrabe.</p>
1060: <figcaption><cite>Jabberwocky</cite> (first verse). Lewis Carroll, 1832-98</figcaption>
1061: </figure></pre>
1062:
1063: </div><div class="example">
1064:
1065: <p>In this example, which could be part of a much larger work
1066: discussing a castle, the figure has three images in it.</p>
1067:
1068: <pre><figure>
1069: <img src="castle1423.jpeg" title="Etching. Anonymous, ca. 1423."
1070: alt="The castle has one tower, and a tall wall around it.">
1071: <img src="castle1858.jpeg" title="Oil-based paint on canvas. Maria Towle, 1858."
1072: alt="The castle now has two towers and two walls.">
1073: <img src="castle1999.jpeg" title="Film photograph. Peter Jankle, 1999."
1074: alt="The castle lies in ruins, the original tower all that remains in one piece.">
1075: <figcaption>The castle through the ages: 1423, 1858, and 1999 respectively.</figcaption>
1076: </figure></pre>
1077:
1.27 mike 1078: </div><h4 id="the-figcaption-element"><span class="secno">4.5.12 </span>The <dfn><code>figcaption</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
1.17 mike 1079: <dd>None.</dd>
1080: <dt>Contexts in which this element may be used:</dt>
1081: <dd>As the first or last child of a <code><a href="#the-figure-element">figure</a></code> element.</dd>
1082: <dt>Content model:</dt>
1.36 mike 1083: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
1.17 mike 1084: <dt>Content attributes:</dt>
1085: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
1086: <dt>DOM interface:</dt>
1087: <dd>Uses <code><a href="elements.html#htmlelement">HTMLElement</a></code>.</dd>
1.51 mike 1088: </dl><p>The <code><a href="#the-figcaption-element">figcaption</a></code> element <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> a
1.17 mike 1089: caption or legend for the rest of the contents of the
1090: <code><a href="#the-figcaption-element">figcaption</a></code> element's parent <code><a href="#the-figure-element">figure</a></code>
1.51 mike 1091: element.<h4 id="the-div-element"><span class="secno">4.5.13 </span>The <dfn><code>div</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><dl class="element"><dt>Categories</dt>
1.12 mike 1092: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
1093: <dd><a href="dnd.html#formatblock-candidate"><code title="">formatBlock</code> candidate</a>.</dd>
1094: <dt>Contexts in which this element may be used:</dt>
1095: <dd>Where <a href="content-models.html#flow-content">flow content</a> is expected.</dd>
1096: <dt>Content model:</dt>
1097: <dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
1098: <dt>Content attributes:</dt>
1099: <dd><a href="elements.html#global-attributes">Global attributes</a></dd>
1100: <dt>DOM interface:</dt>
1101: <dd>
1102: <pre class="idl">interface <dfn id="htmldivelement">HTMLDivElement</dfn> : <a href="elements.html#htmlelement">HTMLElement</a> {};</pre>
1103: </dd>
1104: </dl><p>The <code><a href="#the-div-element">div</a></code> element has no special meaning at all. It
1.51 mike 1105: <a class="full-spec-link" href="http://dev.w3.org/html5/spec/rendering.html#represents" title='Read about this "represents" reference in the full HTML5 spec.'>represents</a> its children. It can be used with the <code title="attr-class"><a href="elements.html#classes">class</a></code>, <code title="attr-lang"><a href="elements.html#attr-lang">lang</a></code>, and <code title="attr-title"><a href="elements.html#the-title-attribute">title</a></code> attributes to mark up semantics
1106: common to a group of consecutive elements.<p class="note">Authors are strongly encouraged to view the
1.12 mike 1107: <code><a href="#the-div-element">div</a></code> element as an element of last resort, for when no
1108: other element is suitable. Use of the <code><a href="#the-div-element">div</a></code> element
1109: instead of more appropriate elements leads to poor accessibility for
1.51 mike 1110: readers and poor maintainability for authors.<div class="example">
1.12 mike 1111:
1112: <p>For example, a blog post would be marked up using
1113: <code><a href="sections.html#the-article-element">article</a></code>, a chapter using <code><a href="sections.html#the-section-element">section</a></code>, a
1114: page's navigation aids using <code><a href="sections.html#the-nav-element">nav</a></code>, and a group of form
1115: controls using <code><a href="forms.html#the-fieldset-element">fieldset</a></code>.</p>
1116:
1117: <p>On the other hand, <code><a href="#the-div-element">div</a></code> elements can be useful for
1118: stylistic purposes or to wrap multiple paragraphs within a section
1119: that are all to be annotated in a similar way. In the following
1120: example, we see <code><a href="#the-div-element">div</a></code> elements used as a way to set the
1121: language of two paragraphs at once, instead of setting the language
1122: on the two paragraph elements separately:</p>
1123:
1124: <pre><article lang="en-US">
1125: <h1>My use of language and my cats</h1>
1126: <p>My cat's behavior hasn't changed much since her absence, except
1127: that she plays her new physique to the neighbors regularly, in an
1128: attempt to get pets.</p>
1129: <div lang="en-GB">
1130: <p>My other cat, coloured black and white, is a sweetie. He followed
1131: us to the pool today, walking down the pavement with us. Yesterday
1132: he apparently visited our neighbours. I wonder if he recognises that
1133: their flat is a mirror image of ours.</p>
1134: <p>Hm, I just noticed that in the last paragraph I used British
1135: English. But I'm supposed to write in American English. So I
1136: shouldn't say "pavement" or "flat" or "colour"...</p>
1137: </div>
1138: <p>I should say "sidewalk" and "apartment" and "color"!</p>
1139: </article></pre>
1140:
1.51 mike 1141: </div>
Webmaster
![[BACK]](/http/77726476706e69737468656265737421f4f257d23063265f6c0f/cvsweb/icons/back.gif?vpn-1){kind=icon}
Return to grouping-content.html CVS log ![[TXT]](/http/77726476706e69737468656265737421f4f257d23063265f6c0f/cvsweb/icons/text.gif?vpn-1){kind=icon}
![[DIR]](/http/77726476706e69737468656265737421f4f257d23063265f6c0f/cvsweb/icons/dir.gif?vpn-1){kind=icon}
Up to [Public] / html5 / spec-author-view