Annotation of html5/spec/syntax.html, revision 1.223
1.2 mike 1: <!DOCTYPE HTML>
1.12 mike 2: <html lang="en-US-x-Hixie"><head><title>9 The HTML syntax — HTML 5</title><style type="text/css">
1.1 mike 3: pre { margin-left: 2em; white-space: pre-wrap; }
4: h2 { margin: 3em 0 1em 0; }
5: h3 { margin: 2.5em 0 1em 0; }
6: h4 { margin: 2.5em 0 0.75em 0; }
7: h5, h6 { margin: 2.5em 0 1em; }
8: h1 + h2, h1 + h2 + h2 { margin: 0.75em 0 0.75em; }
9: h2 + h3, h3 + h4, h4 + h5, h5 + h6 { margin-top: 0.5em; }
10: p { margin: 1em 0; }
11: hr:not(.top) { display: block; background: none; border: none; padding: 0; margin: 2em 0; height: auto; }
12: dl, dd { margin-top: 0; margin-bottom: 0; }
13: dt { margin-top: 0.75em; margin-bottom: 0.25em; clear: left; }
14: dt + dt { margin-top: 0; }
15: dd dt { margin-top: 0.25em; margin-bottom: 0; }
16: dd p { margin-top: 0; }
17: dd dl + p { margin-top: 1em; }
18: dd table + p { margin-top: 1em; }
19: p + * > li, dd li { margin: 1em 0; }
20: dt, dfn { font-weight: bold; font-style: normal; }
21: dt dfn { font-style: italic; }
22: pre, code { font-size: inherit; font-family: monospace; font-variant: normal; }
23: pre strong { color: black; font: inherit; font-weight: bold; background: yellow; }
24: pre em { font-weight: bolder; font-style: normal; }
25: @media screen { code { color: orangered; } code :link, code :visited { color: inherit; } }
26: var sub { vertical-align: bottom; font-size: smaller; position: relative; top: 0.1em; }
27: table { border-collapse: collapse; border-style: hidden hidden none hidden; }
28: table thead { border-bottom: solid; }
29: table tbody th:first-child { border-left: solid; }
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; }
1.2 mike 39: .applies th > * { display: block; }
1.1 mike 40: .applies thead code { display: block; }
41: .applies td { text-align: center; }
42: .applies .yes { background: yellow; }
43:
44: .toc dfn, h1 dfn, h2 dfn, h3 dfn, h4 dfn, h5 dfn, h6 dfn { font: inherit; }
45: img.extra { float: right; }
46: pre.idl { border: solid thin; background: #EEEEEE; color: black; padding: 0.5em 1em; }
47: pre.idl :link, pre.idl :visited { color: inherit; background: transparent; }
48: pre.css { border: solid thin; background: #FFFFEE; color: black; padding: 0.5em 1em; }
49: pre.css:first-line { color: #AAAA50; }
50: dl.domintro { color: green; margin: 2em 0 2em 2em; padding: 0.5em 1em; border: none; background: #EEFFEE; }
51: hr + dl.domintro, div.impl + dl.domintro { margin-top: 2.5em; margin-bottom: 1.5em; }
52: dl.domintro dt, dl.domintro dt * { color: black; text-decoration: none; }
53: dl.domintro dd { margin: 0.5em 0 1em 2em; padding: 0; }
54: dl.domintro dd p { margin: 0.5em 0; }
55: dl.switch { padding-left: 2em; }
56: dl.switch > dt { text-indent: -1.5em; }
57: dl.switch > dt:before { content: '\21AA'; padding: 0 0.5em 0 0; display: inline-block; width: 1em; text-align: right; line-height: 0.5em; }
58: dl.triple { padding: 0 0 0 1em; }
59: dl.triple dt, dl.triple dd { margin: 0; display: inline }
60: dl.triple dt:after { content: ':'; }
61: dl.triple dd:after { content: '\A'; white-space: pre; }
62: .diff-old { text-decoration: line-through; color: silver; background: transparent; }
63: .diff-chg, .diff-new { text-decoration: underline; color: green; background: transparent; }
64: a .diff-new { border-bottom: 1px blue solid; }
65:
66: h2 { page-break-before: always; }
67: h1, h2, h3, h4, h5, h6 { page-break-after: avoid; }
68: h1 + h2, hr + h2.no-toc { page-break-before: auto; }
69:
70: p > span:not([title=""]):not([class="XXX"]):not([class="impl"]), li > span:not([title=""]):not([class="XXX"]):not([class="impl"]) { border-bottom: solid #9999CC; }
71:
72: div.head { margin: 0 0 1em; padding: 1em 0 0 0; }
73: div.head p { margin: 0; }
74: div.head h1 { margin: 0; }
75: div.head .logo { float: right; margin: 0 1em; }
76: div.head .logo img { border: none } /* remove border from top image */
77: div.head dl { margin: 1em 0; }
78: p.copyright { font-size: x-small; font-style: oblique; margin: 0; }
79:
80: body > .toc > li { margin-top: 1em; margin-bottom: 1em; }
81: body > .toc.brief > li { margin-top: 0.35em; margin-bottom: 0.35em; }
82: body > .toc > li > * { margin-bottom: 0.5em; }
83: body > .toc > li > * > li > * { margin-bottom: 0.25em; }
84: .toc, .toc li { list-style: none; }
85:
86: .brief { margin-top: 1em; margin-bottom: 1em; line-height: 1.1; }
87: .brief li { margin: 0; padding: 0; }
88: .brief li p { margin: 0; padding: 0; }
89:
90: .category-list { margin-top: -0.75em; margin-bottom: 1em; line-height: 1.5; }
91: .category-list::before { content: '\21D2\A0'; font-size: 1.2em; font-weight: 900; }
92: .category-list li { display: inline; }
93: .category-list li:not(:last-child)::after { content: ', '; }
94: .category-list li > span, .category-list li > a { text-transform: lowercase; }
95: .category-list li * { text-transform: none; } /* don't affect <code> nested in <a> */
96:
97: .XXX { color: #E50000; background: white; border: solid red; padding: 0.5em; margin: 1em 0; }
98: .XXX > :first-child { margin-top: 0; }
99: p .XXX { line-height: 3em; }
1.159 mike 100: .annotation { border: solid thin black; background: #0C479D; color: white; position: relative; margin: 8px 0 20px 0; }
101: .annotation:before { position: absolute; left: 0; top: 0; width: 100%; height: 100%; margin: 6px -6px -6px 6px; background: #333333; z-index: -1; content: ''; }
102: .annotation :link, .annotation :visited { color: inherit; }
103: .annotation :link:hover, .annotation :visited:hover { background: transparent; }
104: .annotation span { border: none ! important; }
1.1 mike 105: .note { color: green; background: transparent; font-family: sans-serif; }
106: .warning { color: red; background: transparent; }
107: .note, .warning { font-weight: bolder; font-style: italic; }
108: p.note, div.note { padding: 0.5em 2em; }
109: span.note { padding: 0 2em; }
110: .note p:first-child, .warning p:first-child { margin-top: 0; }
111: .note p:last-child, .warning p:last-child { margin-bottom: 0; }
112: .warning:before { font-style: normal; }
113: p.note:before { content: 'Note: '; }
114: p.warning:before { content: '\26A0 Warning! '; }
115:
116: .bookkeeping:before { display: block; content: 'Bookkeeping details'; font-weight: bolder; font-style: italic; }
117: .bookkeeping { font-size: 0.8em; margin: 2em 0; }
118: .bookkeeping p { margin: 0.5em 2em; display: list-item; list-style: square; }
119:
120: h4 { position: relative; z-index: 3; }
121: h4 + .element, h4 + div + .element { margin-top: -2.5em; padding-top: 2em; }
122: .element {
123: background: #EEEEFF;
124: color: black;
125: margin: 0 0 1em 0.15em;
126: padding: 0 1em 0.25em 0.75em;
127: border-left: solid #9999FF 0.25em;
128: position: relative;
129: z-index: 1;
130: }
131: .element:before {
132: position: absolute;
133: z-index: 2;
134: top: 0;
135: left: -1.15em;
136: height: 2em;
137: width: 0.9em;
138: background: #EEEEFF;
139: content: ' ';
140: border-style: none none solid solid;
141: border-color: #9999FF;
142: border-width: 0.25em;
143: }
144:
1.149 mike 145: .example { display: block; color: #222222; background: #FCFCFC; border-left: double; margin-left: 2em; padding-left: 1em; }
146: td > .example:only-child { margin: 0 0 0 0.1em; }
1.1 mike 147:
148: .tall-and-narrow {
149: font-size: 0.6em;
150: column-width: 25em;
151: column-gap: 1em;
152: -moz-column-width: 25em;
153: -moz-column-gap: 1em;
154: -webkit-column-width: 25em;
155: -webkit-column-gap: 1em;
156: }
157:
158: ul.domTree, ul.domTree ul { padding: 0 0 0 1em; margin: 0; }
159: ul.domTree li { padding: 0; margin: 0; list-style: none; position: relative; }
160: ul.domTree li li { list-style: none; }
161: 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; }
162: 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; }
163: ul.domTree span { font-style: italic; font-family: serif; }
164: ul.domTree .t1 code { color: purple; font-weight: bold; }
165: ul.domTree .t2 { font-style: normal; font-family: monospace; }
166: ul.domTree .t2 .name { color: black; font-weight: bold; }
167: ul.domTree .t2 .value { color: blue; font-weight: normal; }
168: ul.domTree .t3 code, .domTree .t4 code, .domTree .t5 code { color: gray; }
169: ul.domTree .t7 code, .domTree .t8 code { color: green; }
170: ul.domTree .t10 code { color: teal; }
171:
1.158 mike 172: </style><link href="data:text/css," rel="stylesheet" title="Complete specification"><link href="data:text/css,.impl%20%7B%20display:%20none;%20%7D" rel="alternate stylesheet" title="Author documentation only"><link href="data:text/css,.impl%20%7B%20background:%20%23FFEEEE;%20%7D" rel="alternate stylesheet" title="Highlight implementation requirements"><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css"><!-- ZZZ ED vs WD -->
1.2 mike 173: <script src="link-fixup.js"></script>
174: <link href="comms.html" title="8 Communication" rel="prev">
175: <link href="spec.html#contents" title="Table of contents" rel="index">
1.1 mike 176: <link href="named-character-references.html" title="9.6 Named character references" rel="next">
1.16 mike 177: </head><body onload="fixBrokenLink(); fixBrokenLink()"><div class="head">
1.1 mike 178: <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.183 mike 179: <h1>HTML5</h1>
1.1 mike 180: <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
1.123 mike 181: </div><nav>
1.1 mike 182: <a href="comms.html">← 8 Communication</a> –
1.2 mike 183: <a href="spec.html#contents">Table of contents</a> –
1.1 mike 184: <a href="named-character-references.html">9.6 Named character references →</a>
1.223 ! mike 185: </nav><p>This is revision 1.2926.</p>
1.11 mike 186:
1.1 mike 187:
1.123 mike 188: <h2 id="syntax"><span class="secno">9 </span><dfn>The HTML syntax</dfn></h2><p class="note">This section only describes the rules for
1.83 mike 189: <code><a href="iana-considerations.html#text-html">text/html</a></code> resources. Rules for XML resources are
1.1 mike 190: discussed in the section below entitled "<a href="the-xhtml-syntax.html#the-xhtml-syntax">The XHTML
1.159 mike 191: syntax</a>".</p><h3 id="writing"><span class="secno">9.1 </span>Writing HTML documents</h3><p class="XXX annotation"><b>Status: </b><i>Working draft</i></p><div class="impl">
1.1 mike 192:
193: <p><i>This section only applies to documents, authoring tools, and
194: markup generators. In particular, it does not apply to conformance
195: checkers; conformance checkers must use the requirements given in
196: the next section ("parsing HTML documents").</i></p>
197:
1.123 mike 198: </div><p>Documents must consist of the following parts, in the given
199: order:</p><ol><li>Optionally, a single U+FEFF BYTE ORDER MARK (BOM) character.</li>
1.1 mike 200:
201: <li>Any number of <a href="#syntax-comments" title="syntax-comments">comments</a> and
202: <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
203:
204: <li>A <a href="#syntax-doctype" title="syntax-doctype">DOCTYPE</a>.
205:
206: </li><li>Any number of <a href="#syntax-comments" title="syntax-comments">comments</a> and
207: <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
208:
1.159 mike 209: <li>The root element, in the form of an <code><a href="semantics.html#the-html-element-0">html</a></code> <a href="#syntax-elements" title="syntax-elements">element</a>.</li>
1.1 mike 210:
211: <li>Any number of <a href="#syntax-comments" title="syntax-comments">comments</a> and
212: <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
213:
214: </ol><p>The various types of content mentioned above are described in the
1.123 mike 215: next few sections.</p><p>In addition, there are some restrictions on how <a href="semantics.html#character-encoding-declaration" title="character encoding declaration">character encoding
1.1 mike 216: declarations</a> are to be serialized, as discussed in the
1.123 mike 217: section on that topic.</p><div class="note">
1.1 mike 218:
1.159 mike 219: <p>Space characters before the root <code><a href="semantics.html#the-html-element-0">html</a></code> element, and
220: space characters at the start of the <code><a href="semantics.html#the-html-element-0">html</a></code> element and
221: before the <code><a href="semantics.html#the-head-element-0">head</a></code> element, will be dropped when the
1.1 mike 222: document is parsed; space characters <em>after</em> the root
1.159 mike 223: <code><a href="semantics.html#the-html-element-0">html</a></code> element will be parsed as if they were at the end
224: of the <code><a href="semantics.html#the-body-element-0">body</a></code> element. Thus, space characters around the
1.1 mike 225: root element do not round-trip.</p>
226:
227: <p>It is suggested that newlines be inserted after the DOCTYPE,
228: after any comments that are before the root element, after the
1.159 mike 229: <code><a href="semantics.html#the-html-element-0">html</a></code> element's start tag (if it is not <a href="#syntax-tag-omission" title="syntax-tag-omission">omitted</a>), and after any comments
230: that are inside the <code><a href="semantics.html#the-html-element-0">html</a></code> element but before the
231: <code><a href="semantics.html#the-head-element-0">head</a></code> element.</p>
1.1 mike 232:
1.123 mike 233: </div><p>Many strings in the HTML syntax (e.g. the names of elements and
1.1 mike 234: their attributes) are case-insensitive, but only for characters in
235: the ranges U+0041 .. U+005A (LATIN CAPITAL LETTER A to LATIN CAPITAL
236: LETTER Z) and U+0061 .. U+007A (LATIN SMALL LETTER A to LATIN SMALL
237: LETTER Z). For convenience, in this section this is just referred to
1.168 mike 238: as "case-insensitive".</p><h4 id="the-doctype"><span class="secno">9.1.1 </span>The DOCTYPE</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/4">ISSUE-4</a> (html-versioning) blocks progress to Last Call</span></p><p>A <dfn id="syntax-doctype" title="syntax-doctype">DOCTYPE</dfn> is a mostly useless,
1.123 mike 239: but required, header.</p><p class="note">DOCTYPEs are required for legacy reasons. When
1.1 mike 240: omitted, browsers tend to use a different rendering mode that is
241: incompatible with some specifications. Including the DOCTYPE in a
242: document ensures that the browser makes a best-effort attempt at
1.123 mike 243: following the relevant specifications.</p><p>A DOCTYPE must consist of the following characters, in this
244: order:</p><ol class="brief"><li>A U+003C LESS-THAN SIGN (<code><</code>) character.</li>
1.1 mike 245: <li>A U+0021 EXCLAMATION MARK (<code>!</code>) character.</li>
246: <li>A string that is an <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> match for the string "<code title="">DOCTYPE</code>".</li>
247: <li>One or more <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
248: <li>A string that is an <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> match for the string "<code title="">HTML</code>".</li>
249: <li>Optionally, a <a href="#doctype-legacy-string">DOCTYPE legacy string</a> (defined below).</li>
250: <li>Zero or more <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
251: <li>A U+003E GREATER-THAN SIGN (<code>></code>) character.</li>
252: </ol><p class="note">In other words, <code><!DOCTYPE HTML></code>,
1.123 mike 253: case-insensitively.</p><p>For the purposes of HTML generators that cannot output HTML
1.1 mike 254: markup with the short DOCTYPE "<code title=""><!DOCTYPE
255: HTML></code>", a <dfn id="doctype-legacy-string">DOCTYPE legacy string</dfn> may be inserted
256: into the DOCTYPE (in the position defined above). This string must
1.123 mike 257: consist of:</p><ol class="brief"><li>One or more <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
1.1 mike 258: <li>A string that is an <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> match for the string "<code title="">SYSTEM</code>".</li>
259: <li>One or more <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
260: <li>A U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (the <i>quote mark</i>).</li>
261: <li>The literal string "<code title="">about:legacy-compat</code>".</li>
262: <li>A matching U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (i.e. the same character as in the earlier step marked <i>quote mark</i>).</li>
263: </ol><p class="note">In other words, <code><!DOCTYPE HTML SYSTEM
264: "about:legacy-compat"></code> or <code><!DOCTYPE HTML SYSTEM
265: 'about:legacy-compat'></code>, case-insensitively except for the bit
1.123 mike 266: in quotes.</p><p>The <a href="#doctype-legacy-string">DOCTYPE legacy string</a> should not be used unless
1.1 mike 267: the document is generated from a system that cannot output the
1.123 mike 268: shorter string.</p><h4 id="elements-0"><span class="secno">9.1.2 </span>Elements</h4><p>There are five different kinds of <dfn id="syntax-elements" title="syntax-elements">elements</dfn>: void elements, raw text
1.1 mike 269: elements, RCDATA elements, foreign elements, and normal
1.123 mike 270: elements.</p><dl><dt><dfn id="void-elements">Void elements</dfn></dt>
1.1 mike 271:
272: <dd><code><a href="the-canvas-element.html#the-area-element">area</a></code>, <code><a href="semantics.html#the-base-element">base</a></code>, <code><a href="semantics.html#the-br-element">br</a></code>,
1.159 mike 273: <code><a href="tabular-data.html#the-col-element">col</a></code>, <code><a href="interactive-elements.html#the-command">command</a></code>, <code><a href="text-level-semantics.html#the-embed-element">embed</a></code>,
274: <code><a href="semantics.html#the-hr-element">hr</a></code>, <code><a href="text-level-semantics.html#the-img-element">img</a></code>, <code><a href="forms.html#the-input-element">input</a></code>,
1.1 mike 275: <code><a href="forms.html#the-keygen-element">keygen</a></code>, <code><a href="semantics.html#the-link-element">link</a></code>, <code><a href="semantics.html#meta">meta</a></code>,
1.159 mike 276: <code><a href="text-level-semantics.html#the-param-element">param</a></code>, <code><a href="video.html#the-source-element">source</a></code></dd>
1.1 mike 277:
1.91 mike 278: <dt>Raw text elements</dt>
1.1 mike 279:
280: <dd><code><a href="semantics.html#script">script</a></code>, <code><a href="semantics.html#the-style-element">style</a></code></dd> <!-- iframe and
1.91 mike 281: noscript don't count as raw text for syntax purposes -->
1.1 mike 282:
283: <dt>RCDATA elements</dt>
284:
1.159 mike 285: <dd><code><a href="forms.html#the-textarea-element">textarea</a></code>, <code><a href="semantics.html#the-title-element-0">title</a></code></dd>
1.1 mike 286:
287: <dt>Foreign elements</dt>
288:
289: <dd>Elements from the <a href="#mathml-namespace">MathML namespace</a>
290: and the <a href="#svg-namespace">SVG namespace</a>.</dd>
291:
292: <dt>Normal elements</dt>
293:
294: <dd>All other allowed <a href="infrastructure.html#html-elements">HTML elements</a> are normal
295: elements.</dd>
296:
297: </dl><p><dfn id="syntax-tags" title="syntax-tags">Tags</dfn> are used to delimit the start
1.91 mike 298: and end of elements in the markup. Raw text, RCDATA, and normal
1.1 mike 299: elements have a <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> to
300: indicate where they begin, and an <a href="#syntax-end-tag" title="syntax-end-tag">end
301: tag</a> to indicate where they end. The start and end tags of
302: certain normal elements can be <a href="#syntax-tag-omission" title="syntax-tag-omission">omitted</a>, as described
303: later. Those that cannot be omitted must not be omitted. <a href="#void-elements">Void
304: elements</a> only have a start tag; end tags must not be
305: specified for void elements. Foreign elements must either have a
306: start tag and an end tag, or a start tag that is marked as
1.123 mike 307: self-closing, in which case they must not have an end tag.</p><p>The contents of the element must be placed between just after the
1.1 mike 308: start tag (which <a href="#syntax-tag-omission" title="syntax-tag-omission">might be implied,
309: in certain cases</a>) and just before the end tag (which again,
310: <a href="#syntax-tag-omission" title="syntax-tag-omission">might be implied in certain
311: cases</a>). The exact allowed contents of each individual element
312: depends on the content model of that element, as described earlier
313: in this specification. Elements must not contain content that their
314: content model disallows. In addition to the restrictions placed on
315: the contents by those content models, however, the five types of
1.123 mike 316: elements have additional <em>syntactic</em> requirements.</p><p><a href="#void-elements">Void elements</a> can't have any contents (since there's
1.1 mike 317: no end tag, no content can be put between the start tag and the end
1.123 mike 318: tag).</p><p>Raw text elements can have <a href="#syntax-text" title="syntax-text">text</a>,
1.1 mike 319: though it has <a href="#cdata-rcdata-restrictions">restrictions</a>
1.123 mike 320: described below.</p><p>RCDATA elements can have <a href="#syntax-text" title="syntax-text">text</a>
1.1 mike 321: and <a href="#syntax-charref" title="syntax-charref">character references</a>, but
322: the text must not contain an <a href="#syntax-ambiguous-ampersand" title="syntax-ambiguous-ampersand">ambiguous ampersand</a>.
323: There are also <a href="#cdata-rcdata-restrictions">further
1.123 mike 324: restrictions</a> described below.</p><p>Foreign elements whose start tag is marked as self-closing can't
1.1 mike 325: have any contents (since, again, as there's no end tag, no content
326: can be put between the start tag and the end tag). Foreign elements
327: whose start tag is <em>not</em> marked as self-closing can have
328: <a href="#syntax-text" title="syntax-text">text</a>, <a href="#syntax-charref" title="syntax-charref">character references</a>, <a href="#syntax-cdata" title="syntax-cdata">CDATA sections</a>, other <a href="#syntax-elements" title="syntax-elements">elements</a>, and <a href="#syntax-comments" title="syntax-comments">comments</a>, but the text must not
329: contain the character U+003C LESS-THAN SIGN (<code><</code>) or
330: an <a href="#syntax-ambiguous-ampersand" title="syntax-ambiguous-ampersand">ambiguous
1.123 mike 331: ampersand</a>.</p><p>Normal elements can have <a href="#syntax-text" title="syntax-text">text</a>,
1.1 mike 332: <a href="#syntax-charref" title="syntax-charref">character references</a>, other
333: <a href="#syntax-elements" title="syntax-elements">elements</a>, and <a href="#syntax-comments" title="syntax-comments">comments</a>, but the text must not
334: contain the character U+003C LESS-THAN SIGN (<code><</code>) or
335: an <a href="#syntax-ambiguous-ampersand" title="syntax-ambiguous-ampersand">ambiguous
336: ampersand</a>. Some normal elements also have <a href="#element-restrictions">yet more restrictions</a> on what
337: content they are allowed to hold, beyond the restrictions imposed by
338: the content model and those described in this paragraph. Those
1.123 mike 339: restrictions are described below.</p><p>Tags contain a <dfn id="syntax-tag-name" title="syntax-tag-name">tag name</dfn>,
1.1 mike 340: giving the element's name. HTML elements all have names that only
341: use characters in the range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE,
1.202 mike 342: U+0061 LATIN SMALL LETTER A .. U+007A LATIN SMALL LETTER Z, and
343: U+0041 LATIN CAPITAL LETTER A .. U+005A LATIN CAPITAL LETTER Z. In
344: the HTML syntax, tag names may be written with any mix of lower- and
345: uppercase letters that, when converted to all-lowercase, matches the
346: element's tag name; tag names are case-insensitive.</p><h5 id="start-tags"><span class="secno">9.1.2.1 </span>Start tags</h5><p><dfn id="syntax-start-tag" title="syntax-start-tag">Start tags</dfn> must have the
1.123 mike 347: following format:</p><ol><li>The first character of a start tag must be a U+003C LESS-THAN
1.1 mike 348: SIGN (<code><</code>).</li>
349:
350: <li>The next few characters of a start tag must be the element's
351: <a href="#syntax-tag-name" title="syntax-tag-name">tag name</a>.</li>
352:
353: <li>If there are to be any attributes in the next step, there must
354: first be one or more <a href="infrastructure.html#space-character" title="space character">space
355: characters</a>.</li>
356:
357: <li>Then, the start tag may have a number of attributes, the <a href="#syntax-attributes" title="syntax-attributes">syntax for which</a> is described
358: below. Attributes may be separated from each other by one or more
359: <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
360:
361: <li>After the attributes, there may be one or more <a href="infrastructure.html#space-character" title="space character">space characters</a>. (Some attributes
362: are required to be followed by a space. See the <a href="#syntax-attributes" title="syntax-attributes">attributes section</a> below.)</li>
363:
364: <li>Then, if the element is one of the <a href="#void-elements">void elements</a>,
365: or if the element is a foreign element, then there may be a single
366: U+002F SOLIDUS (<code>/</code>) character. This character has no
367: effect on void elements, but on foreign elements it marks the start
368: tag as self-closing.</li>
369:
370: <li>Finally, start tags must be closed by a U+003E GREATER-THAN
371: SIGN (<code>></code>) character.</li>
372:
1.123 mike 373: </ol><h5 id="end-tags"><span class="secno">9.1.2.2 </span>End tags</h5><p><dfn id="syntax-end-tag" title="syntax-end-tag">End tags</dfn> must have the
374: following format:</p><ol><li>The first character of an end tag must be a U+003C LESS-THAN
1.1 mike 375: SIGN (<code><</code>).</li>
376:
377: <li>The second character of an end tag must be a U+002F SOLIDUS
378: (<code>/</code>).</li>
379:
380: <li>The next few characters of an end tag must be the element's
381: <a href="#syntax-tag-name" title="syntax-tag-name">tag name</a>.</li>
382:
383: <li>After the tag name, there may be one or more <a href="infrastructure.html#space-character" title="space
384: character">space characters</a>.</li>
385:
386: <li>Finally, end tags must be closed by a U+003E GREATER-THAN
387: SIGN (<code>></code>) character.</li>
388:
1.123 mike 389: </ol><h5 id="attributes"><span class="secno">9.1.2.3 </span>Attributes</h5><p><dfn id="syntax-attributes" title="syntax-attributes">Attributes</dfn> for an element
390: are expressed inside the element's start tag.</p><p>Attributes have a name and a value. <dfn id="syntax-attribute-name" title="syntax-attribute-name">Attribute names</dfn> must consist of
1.1 mike 391: one or more characters other than the <a href="infrastructure.html#space-character" title="space
392: character">space characters</a>, U+0000 NULL, U+0022 QUOTATION
393: MARK ("), U+0027 APOSTROPHE ('), U+003E GREATER-THAN SIGN
394: (>), U+002F SOLIDUS (/), and U+003D EQUALS SIGN (=) characters,
395: the control characters, and any characters that are not defined by
396: Unicode. In the HTML syntax, attribute names may be written with any
397: mix of lower- and uppercase letters that are an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.123 mike 398: case-insensitive</a> match for the attribute's name.</p><p><dfn id="syntax-attribute-value" title="syntax-attribute-value">Attribute values</dfn> are a
1.1 mike 399: mixture of <a href="#syntax-text" title="syntax-text">text</a> and <a href="#syntax-charref" title="syntax-charref">character references</a>, except with the
1.123 mike 400: additional restriction that the text cannot contain an <a href="#syntax-ambiguous-ampersand" title="syntax-ambiguous-ampersand">ambiguous ampersand</a>.</p><p>Attributes can be specified in four different ways:</p><dl><dt>Empty attribute syntax</dt>
1.1 mike 401:
402: <dd>
403:
404: <p>Just the <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute
405: name</a>.</p>
406:
407: <div class="example">
408:
409: <p>In the following example, the <code title="attr-fe-disabled"><a href="forms.html#attr-fe-disabled">disabled</a></code> attribute is given with
410: the empty attribute syntax:</p>
411:
412: <pre><input <em>disabled</em>></pre>
413:
414: </div>
415:
416: <p>If an attribute using the empty attribute syntax is to be
417: followed by another attribute, then there must be a <a href="infrastructure.html#space-character">space
418: character</a> separating the two.</p>
419:
420: </dd>
421:
1.2 mike 422: <dt id="unquoted">Unquoted attribute value syntax</dt>
1.1 mike 423:
424: <dd>
425:
426: <p>The <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute name</a>,
427: followed by zero or more <a href="infrastructure.html#space-character" title="space character">space
428: characters</a>, followed by a single U+003D EQUALS SIGN
429: character, followed by zero or more <a href="infrastructure.html#space-character" title="space
430: character">space characters</a>, followed by the <a href="#syntax-attribute-value" title="syntax-attribute-value">attribute value</a>, which, in
431: addition to the requirements given above for attribute values,
432: must not contain any literal <a href="infrastructure.html#space-character" title="space character">space
433: characters</a>, any U+0022 QUOTATION MARK (<code>"</code>)
434: characters, U+0027 APOSTROPHE (<code>'</code>) characters,
435: U+003D EQUALS SIGN (<code>=</code>) characters, U+003C LESS-THAN
436: SIGN (<code><</code>) characters, or U+003E GREATER-THAN SIGN
437: (<code>></code>) characters, and must not be the empty
438: string.</p>
439:
440: <div class="example">
441:
442: <p>In the following example, the <code title="attr-input-value"><a href="forms.html#attr-input-value">value</a></code> attribute is given
443: with the unquoted attribute value syntax:</p>
444:
445: <pre><input <em>value=yes</em>></pre>
446:
447: </div>
448:
449: <p>If an attribute using the unquoted attribute syntax is to be
1.101 mike 450: followed by another attribute or by the optional U+002F SOLIDUS
451: (<code>/</code>) character allowed in step 6 of the <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> syntax above, then there
1.1 mike 452: must be a <a href="infrastructure.html#space-character">space character</a> separating the two.</p>
453:
454: </dd>
455:
456: <dt>Single-quoted attribute value syntax</dt>
457:
458: <dd>
459:
460: <p>The <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute name</a>,
461: followed by zero or more <a href="infrastructure.html#space-character" title="space character">space
462: characters</a>, followed by a single U+003D EQUALS SIGN
463: character, followed by zero or more <a href="infrastructure.html#space-character" title="space
464: character">space characters</a>, followed by a single U+0027
465: APOSTROPHE (<code>'</code>) character, followed by the <a href="#syntax-attribute-value" title="syntax-attribute-value">attribute value</a>, which, in
466: addition to the requirements given above for attribute values,
467: must not contain any literal U+0027 APOSTROPHE (<code>'</code>)
468: characters, and finally followed by a second single U+0027
469: APOSTROPHE (<code>'</code>) character.</p>
470:
471: <div class="example">
472:
473: <p>In the following example, the <code title="attr-input-type"><a href="forms.html#attr-input-type">type</a></code> attribute is given with the
474: single-quoted attribute value syntax:</p>
475:
476: <pre><input <em>type='checkbox'</em>></pre>
477:
478: </div>
479:
480: <p>If an attribute using the single-quoted attribute syntax is to
481: be followed by another attribute, then there must be a <a href="infrastructure.html#space-character">space
482: character</a> separating the two.</p>
483:
484: </dd>
485:
486: <dt>Double-quoted attribute value syntax</dt>
487:
488: <dd>
489:
490: <p>The <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute name</a>,
491: followed by zero or more <a href="infrastructure.html#space-character" title="space character">space
492: characters</a>, followed by a single U+003D EQUALS SIGN
493: character, followed by zero or more <a href="infrastructure.html#space-character" title="space
494: character">space characters</a>, followed by a single U+0022
495: QUOTATION MARK (<code>"</code>) character, followed by the <a href="#syntax-attribute-value" title="syntax-attribute-value">attribute value</a>, which, in
496: addition to the requirements given above for attribute values,
497: must not contain any literal U+0022 QUOTATION MARK
498: (<code>"</code>) characters, and finally followed by a second
499: single U+0022 QUOTATION MARK (<code>"</code>) character.</p>
500:
501: <div class="example">
502:
503: <p>In the following example, the <code title="attr-fe-name"><a href="forms.html#attr-fe-name">name</a></code> attribute is given with the
504: double-quoted attribute value syntax:</p>
505:
506: <pre><input <em>name="be evil"</em>></pre>
507:
508: </div>
509:
510: <p>If an attribute using the double-quoted attribute syntax is to
511: be followed by another attribute, then there must be a <a href="infrastructure.html#space-character">space
512: character</a> separating the two.</p>
513:
514: </dd>
515:
516: </dl><p>There must never be two or more attributes on the same start tag
517: whose names are an <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> match for
1.123 mike 518: each other.</p><h5 id="optional-tags"><span class="secno">9.1.2.4 </span>Optional tags</h5><p>Certain tags can be <dfn id="syntax-tag-omission" title="syntax-tag-omission">omitted</dfn>.</p><p class="note">Omitting an element's <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> does not mean the element
1.1 mike 519: is not present; it is implied, but it is still there. An HTML
1.159 mike 520: document always has a root <code><a href="semantics.html#the-html-element-0">html</a></code> element, even if the
1.1 mike 521: string <code title=""><html></code> doesn't appear anywhere in
1.159 mike 522: the markup.</p><!-- <html> --><p>An <code><a href="semantics.html#the-html-element-0">html</a></code> element's <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> may be omitted if the
523: first thing inside the <code><a href="semantics.html#the-html-element-0">html</a></code> element is not a <a href="#syntax-comments" title="syntax-comments">comment</a>.</p><!-- </html> --><p>An <code><a href="semantics.html#the-html-element-0">html</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
524: tag</a> may be omitted if the <code><a href="semantics.html#the-html-element-0">html</a></code> element is not
525: immediately followed by a <a href="#syntax-comments" title="syntax-comments">comment</a>.</p><!-- <head> --><p>A <code><a href="semantics.html#the-head-element-0">head</a></code> element's <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> may be omitted <!--if the
1.1 mike 526: element is empty, or--> if the first thing inside the
1.159 mike 527: <code><a href="semantics.html#the-head-element-0">head</a></code> element is an element.</p><!-- </head> --><p>A <code><a href="semantics.html#the-head-element-0">head</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
528: tag</a> may be omitted if the <code><a href="semantics.html#the-head-element-0">head</a></code> element is not
529: immediately followed by a <a href="infrastructure.html#space-character">space character</a> or a <a href="#syntax-comments" title="syntax-comments">comment</a>.</p><!-- <body> --><p>A <code><a href="semantics.html#the-body-element-0">body</a></code> element's <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> may be omitted if the
530: element is empty, or if the first thing inside the <code><a href="semantics.html#the-body-element-0">body</a></code>
1.1 mike 531: element is not a <a href="infrastructure.html#space-character">space character</a> or a <a href="#syntax-comments" title="syntax-comments">comment</a>, except if the first thing
1.159 mike 532: inside the <code><a href="semantics.html#the-body-element-0">body</a></code> element is a <code><a href="semantics.html#script">script</a></code> or
1.1 mike 533: <code><a href="semantics.html#the-style-element">style</a></code> element. <!-- Note that even if the </head> end
534: tag is present, the parser makes <style> and <script> elements
535: between </head> and <body> end up in the <head> instead of implying
1.159 mike 536: the <body> --></p><!-- </body> --><p>A <code><a href="semantics.html#the-body-element-0">body</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
537: tag</a> may be omitted if the <code><a href="semantics.html#the-body-element-0">body</a></code> element is not
1.123 mike 538: immediately followed by a <a href="#syntax-comments" title="syntax-comments">comment</a>.</p><!-- </li> --><p>A <code><a href="semantics.html#the-li-element">li</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 539: tag</a> may be omitted if the <code><a href="semantics.html#the-li-element">li</a></code> element is
540: immediately followed by another <code><a href="semantics.html#the-li-element">li</a></code> element or if there
1.123 mike 541: is no more content in the parent element.</p><!-- </dt> --><p>A <code><a href="semantics.html#the-dt-element">dt</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 542: tag</a> may be omitted if the <code><a href="semantics.html#the-dt-element">dt</a></code> element is
543: immediately followed by another <code><a href="semantics.html#the-dt-element">dt</a></code> element or a
1.123 mike 544: <code><a href="semantics.html#the-dd-element">dd</a></code> element.</p><!-- </dd> --><p>A <code><a href="semantics.html#the-dd-element">dd</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 545: tag</a> may be omitted if the <code><a href="semantics.html#the-dd-element">dd</a></code> element is
546: immediately followed by another <code><a href="semantics.html#the-dd-element">dd</a></code> element or a
547: <code><a href="semantics.html#the-dt-element">dt</a></code> element, or if there is no more content in the
1.123 mike 548: parent element.</p><!-- </p> --><p>A <code><a href="semantics.html#the-p-element">p</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 549: tag</a> may be omitted if the <code><a href="semantics.html#the-p-element">p</a></code> element is
550: immediately followed by an <code><a href="semantics.html#the-address-element">address</a></code>,
551: <code><a href="semantics.html#the-article-element">article</a></code>, <code><a href="semantics.html#the-aside-element">aside</a></code>, <code><a href="semantics.html#the-blockquote-element">blockquote</a></code>,
1.86 mike 552: <!--v2DATAGRID <code>datagrid</code>,--> <code><a href="semantics.html#the-dialog-element">dialog</a></code>,
553: <code><a href="obsolete.html#dir">dir</a></code>, <code><a href="interactive-elements.html#the-div-element">div</a></code>, <code><a href="semantics.html#the-dl-element">dl</a></code>,
554: <code><a href="forms.html#the-fieldset-element">fieldset</a></code>, <code><a href="semantics.html#the-footer-element">footer</a></code>, <code><a href="forms.html#the-form-element">form</a></code>,
555: <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h1</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h2</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h3</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h4</a></code>,
556: <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h5</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h6</a></code>, <code><a href="semantics.html#the-header-element">header</a></code>,
557: <code><a href="semantics.html#the-hgroup-element">hgroup</a></code>, <code><a href="semantics.html#the-hr-element">hr</a></code>, <code><a href="interactive-elements.html#menus">menu</a></code>,
558: <code><a href="semantics.html#the-nav-element">nav</a></code>, <code><a href="semantics.html#the-ol-element">ol</a></code>, <code><a href="semantics.html#the-p-element">p</a></code>, <code><a href="semantics.html#the-pre-element">pre</a></code>,
1.1 mike 559: <code><a href="semantics.html#the-section-element">section</a></code>, <code><a href="tabular-data.html#the-table-element">table</a></code>, or <code><a href="semantics.html#the-ul-element">ul</a></code>,
560: element, or if there is no more content in the parent element and
1.123 mike 561: the parent element is not an <code><a href="text-level-semantics.html#the-a-element">a</a></code> element.</p><!-- </rt> --><p>An <code><a href="text-level-semantics.html#the-rt-element">rt</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 562: tag</a> may be omitted if the <code><a href="text-level-semantics.html#the-rt-element">rt</a></code> element is
563: immediately followed by an <code><a href="text-level-semantics.html#the-rt-element">rt</a></code> or <code><a href="text-level-semantics.html#the-rp-element">rp</a></code>
1.123 mike 564: element, or if there is no more content in the parent element.</p><!-- </rp> --><p>An <code><a href="text-level-semantics.html#the-rp-element">rp</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 565: tag</a> may be omitted if the <code><a href="text-level-semantics.html#the-rp-element">rp</a></code> element is
566: immediately followed by an <code><a href="text-level-semantics.html#the-rt-element">rt</a></code> or <code><a href="text-level-semantics.html#the-rp-element">rp</a></code>
1.123 mike 567: element, or if there is no more content in the parent element.</p><!-- </optgroup> (the text assumes <optgroup> can only be inside a
1.1 mike 568: <select>; commented out text below can handle the non-<select> case
1.123 mike 569: if we ever allow it) --><p>An <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end tag</a> may be omitted if the
1.1 mike 570: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element <!--has an ancestor
571: <code>select</code> element and--> is immediately followed by
572: another <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, or if <!--all of the elements
573: that are ancestors of the <code>optgroup</code> element, up to and
574: including the first ancestor element that is not an
575: <code>optgroup</code> element, have no more content--> there is no
1.123 mike 576: more content in the parent element.</p><!-- so e.g. the max number of </optgroup>s are omitted here:
1.1 mike 577: <select><optgroup></select>
578: <p id=x><optgroup></optgroup>x</p>
579: <p id=x><optgroup><optgroup></optgroup></optgroup>x</p>
580: <p><optgroup id=x><optgroup></optgroup>x</p>
581: <p><optgroup><optgroup id=x>x</p>
1.123 mike 582: --><!-- </option> --><p>An <code><a href="forms.html#the-option-element">option</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 583: tag</a> may be omitted if the <code><a href="forms.html#the-option-element">option</a></code> element is
584: immediately followed by another <code><a href="forms.html#the-option-element">option</a></code> element, or if
585: it is immediately followed by an <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, or
1.123 mike 586: if there is no more content in the parent element.</p><!-- <colgroup> --><p>A <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element's <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> may be omitted if the
1.1 mike 587: first thing inside the <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element is a
588: <code><a href="tabular-data.html#the-col-element">col</a></code> element, and if the element is not immediately
589: preceded by another <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element whose <a href="#syntax-end-tag" title="syntax-end-tag">end tag</a> has been omitted. (It can't be
1.123 mike 590: omitted if the element is empty.)</p><!-- </colgroup> --><p>A <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end tag</a> may be omitted if the
1.1 mike 591: <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element is not immediately followed by a
1.123 mike 592: <a href="infrastructure.html#space-character">space character</a> or a <a href="#syntax-comments" title="syntax-comments">comment</a>.</p><!-- </thead> --><p>A <code><a href="tabular-data.html#the-thead-element">thead</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 593: tag</a> may be omitted if the <code><a href="tabular-data.html#the-thead-element">thead</a></code> element is
594: immediately followed by a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> or <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code>
1.123 mike 595: element.</p><!-- <tbody> --><p>A <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element's <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> may be omitted if the
1.1 mike 596: first thing inside the <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element is a
597: <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, and if the element is not immediately
598: preceded by a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>, <code><a href="tabular-data.html#the-thead-element">thead</a></code>, or
599: <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element whose <a href="#syntax-end-tag" title="syntax-end-tag">end
600: tag</a> has been omitted. (It can't be omitted if the element is
1.123 mike 601: empty.)</p><!-- </tbody> --><p>A <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 602: tag</a> may be omitted if the <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element is
603: immediately followed by a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> or <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code>
1.123 mike 604: element, or if there is no more content in the parent element.</p><!-- </tfoot> --><p>A <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 605: tag</a> may be omitted if the <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element is
606: immediately followed by a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element, or if there is
1.123 mike 607: no more content in the parent element.</p><!-- </tr> --><p>A <code><a href="tabular-data.html#the-tr-element">tr</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 608: tag</a> may be omitted if the <code><a href="tabular-data.html#the-tr-element">tr</a></code> element is
609: immediately followed by another <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, or if there
1.123 mike 610: is no more content in the parent element.</p><!-- </td> --><p>A <code><a href="tabular-data.html#the-td-element">td</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 611: tag</a> may be omitted if the <code><a href="tabular-data.html#the-td-element">td</a></code> element is
612: immediately followed by a <code><a href="tabular-data.html#the-td-element">td</a></code> or <code><a href="tabular-data.html#the-th-element">th</a></code>
1.123 mike 613: element, or if there is no more content in the parent element.</p><!-- </th> --><p>A <code><a href="tabular-data.html#the-th-element">th</a></code> element's <a href="#syntax-end-tag" title="syntax-end-tag">end
1.1 mike 614: tag</a> may be omitted if the <code><a href="tabular-data.html#the-th-element">th</a></code> element is
615: immediately followed by a <code><a href="tabular-data.html#the-td-element">td</a></code> or <code><a href="tabular-data.html#the-th-element">th</a></code>
1.123 mike 616: element, or if there is no more content in the parent element.</p><p><strong>However</strong>, a <a href="#syntax-start-tag" title="syntax-start-tag">start
617: tag</a> must never be omitted if it has any attributes.</p><h5 id="element-restrictions"><span class="secno">9.1.2.5 </span>Restrictions on content models</h5><p>For historical reasons, certain elements have extra restrictions
618: beyond even the restrictions given by their content model.</p><p>A <code><a href="tabular-data.html#the-table-element">table</a></code> element must not contain <code><a href="tabular-data.html#the-tr-element">tr</a></code>
1.1 mike 619: elements, even though these elements are technically allowed inside
620: <code><a href="tabular-data.html#the-table-element">table</a></code> elements according to the content models
621: described in this specification. (If a <code><a href="tabular-data.html#the-tr-element">tr</a></code> element is
622: put inside a <code><a href="tabular-data.html#the-table-element">table</a></code> in the markup, it will in fact imply
1.123 mike 623: a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> start tag before it.)</p><p>A single U+000A LINE FEED (LF) character may be placed
1.1 mike 624: immediately after the <a href="#syntax-start-tag" title="syntax-start-tag">start
625: tag</a> of <code><a href="semantics.html#the-pre-element">pre</a></code> and <code><a href="forms.html#the-textarea-element">textarea</a></code>
626: elements. This does not affect the processing of the element. The
627: otherwise optional U+000A LINE FEED (LF) character <em>must</em> be
628: included if the element's contents start with that character
629: (because otherwise the leading newline in the contents would be
1.123 mike 630: treated like the optional newline, and ignored).</p><div class="example">
1.1 mike 631: <p>The following two <code><a href="semantics.html#the-pre-element">pre</a></code> blocks are equivalent:</p>
632: <pre><pre>Hello</pre></pre>
633: <pre><pre><br>Hello</pre></pre>
1.123 mike 634: </div><h5 id="cdata-rcdata-restrictions"><span class="secno">9.1.2.6 </span>Restrictions on the contents of raw text and RCDATA elements</h5><p>The text in raw text and RCDATA elements must not contain any
1.1 mike 635: occurrences of the string "<code title=""></</code>" (U+003C
636: LESS-THAN SIGN, U+002F SOLIDUS) followed by characters that
637: case-insensitively match the tag name of the element followed by one
638: of U+0009 CHARACTER TABULATION, U+000A LINE FEED (LF), U+000C FORM
639: FEED (FF), U+0020 SPACE, U+003E GREATER-THAN SIGN (>), or U+002F
1.123 mike 640: SOLIDUS (/), unless that string is part of an <a href="#syntax-escape" title="syntax-escape">escaping text span</a>.</p><p>An <dfn id="syntax-escape" title="syntax-escape">escaping text span</dfn> is a span
1.1 mike 641: of <a href="#syntax-text" title="syntax-text">text</a> that starts with an <a href="#syntax-escape-start" title="syntax-escape-start">escaping text span start</a> that is
642: not itself in an <a href="#syntax-escape" title="syntax-escape">escaping text
643: span</a>, and ends at the next <a href="#syntax-escape-end" title="syntax-escape-end">escaping text span end</a>. There
644: cannot be any <a href="#syntax-charref" title="syntax-charref">character
645: references</a> inside an <a href="#syntax-escape" title="syntax-escape">escaping
646: text span</a> — sequences of characters that would look
647: like <a href="#syntax-charref" title="syntax-charref">character references</a> do not
1.123 mike 648: have special meaning.</p><p>An <dfn id="syntax-escape-start" title="syntax-escape-start">escaping text span
1.1 mike 649: start</dfn> is a part of <a href="#syntax-text" title="syntax-text">text</a> that
650: consists of the four character sequence "<code title=""><!--</code>" (U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
1.123 mike 651: MARK, U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS).</p><p>An <dfn id="syntax-escape-end" title="syntax-escape-end">escaping text span end</dfn> is
1.1 mike 652: a part of <a href="#syntax-text" title="syntax-text">text</a> that consists of the
653: three character sequence "<code title="">--></code>" (U+002D
1.134 mike 654: HYPHEN-MINUS, U+002D HYPHEN-MINUS, U+003E GREATER-THAN SIGN).</p><p>An <a href="#syntax-escape-start" title="syntax-escape-start">escaping text span
1.1 mike 655: start</a> may share its U+002D HYPHEN-MINUS characters with its
656: corresponding <a href="#syntax-escape-end" title="syntax-escape-end">escaping text span
1.123 mike 657: end</a>.</p><p>The text in raw text elements and RCDATA elements must not have
1.91 mike 658: an <a href="#syntax-escape-start" title="syntax-escape-start">escaping text span start</a>
659: that is not followed by an <a href="#syntax-escape-end" title="syntax-escape-end">escaping
1.123 mike 660: text span end</a>.</p><h4 id="text-0"><span class="secno">9.1.3 </span>Text</h4><p><dfn id="syntax-text" title="syntax-text">Text</dfn> is allowed inside elements,
1.1 mike 661: attributes, and comments. Text must consist of Unicode characters.
662: Text must not contain U+0000 characters. Text must not contain
663: permanently undefined Unicode characters. Text must not contain
664: control characters other than <a href="infrastructure.html#space-character" title="space character">space
665: characters</a>. Extra constraints are placed on what is and what
666: is not allowed in text based on where the text is to be put, as
1.123 mike 667: described in the other sections.</p><h5 id="newlines"><span class="secno">9.1.3.1 </span>Newlines</h5><p><dfn id="syntax-newlines" title="syntax-newlines">Newlines</dfn> in HTML may be
1.1 mike 668: represented either as U+000D CARRIAGE RETURN (CR) characters, U+000A
669: LINE FEED (LF) characters, or pairs of U+000D CARRIAGE RETURN (CR),
1.123 mike 670: U+000A LINE FEED (LF) characters in that order.</p><h4 id="character-references"><span class="secno">9.1.4 </span>Character references</h4><p>In certain cases described in other sections, <a href="#syntax-text" title="syntax-text">text</a> may be mixed with <dfn id="syntax-charref" title="syntax-charref">character references</dfn>. These can be used
1.1 mike 671: to escape characters that couldn't otherwise legally be included in
1.123 mike 672: <a href="#syntax-text" title="syntax-text">text</a>.</p><p>Character references must start with a U+0026 AMPERSAND
1.1 mike 673: (<code>&</code>). Following this, there are three possible kinds
1.123 mike 674: of character references:</p><dl><dt>Named character references</dt>
1.1 mike 675:
676: <dd>The ampersand must be followed by one of the names given in the
677: <a href="named-character-references.html#named-character-references">named character references</a> section, using the same
678: case. The name must be one that is terminated by a U+003B SEMICOLON
679: (<code title="">;</code>) character.</dd>
680:
681:
682: <dt>Decimal numeric character reference</dt>
683:
684: <dd>The ampersand must be followed by a U+0023 NUMBER SIGN
685: (<code>#</code>) character, followed by one or more digits in the
686: range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE, representing a
687: base-ten integer that itself is a Unicode code point that is
688: not U+0000, U+000D, in the range U+0080 .. U+009F, or in the range
689: 0xD800 .. 0xDFFF (surrogates). The digits must then be followed by
690: a U+003B SEMICOLON character (<code title="">;</code>).</dd>
691:
692:
693: <dt>Hexadecimal numeric character reference</dt>
694:
695: <dd>The ampersand must be followed by a U+0023 NUMBER SIGN
696: (<code>#</code>) character, which must be followed by either a
697: U+0078 LATIN SMALL LETTER X or a U+0058 LATIN CAPITAL LETTER X
698: character, which must then be followed by one or more digits in the
699: range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE, U+0061 LATIN SMALL
700: LETTER A .. U+0066 LATIN SMALL LETTER F, and U+0041 LATIN CAPITAL
701: LETTER A .. U+0046 LATIN CAPITAL LETTER F, representing a
702: base-sixteen integer that itself is a Unicode code point that is
703: not U+0000, U+000D, in the range U+0080 .. U+009F, or in the range
704: 0xD800 .. 0xDFFF (surrogates). The digits must then be followed by
705: a U+003B SEMICOLON character (<code title="">;</code>).</dd>
706:
707: </dl><p>An <dfn id="syntax-ambiguous-ampersand" title="syntax-ambiguous-ampersand">ambiguous
708: ampersand</dfn> is a U+0026 AMPERSAND (<code>&</code>) character
709: that is followed by some <a href="#syntax-text" title="syntax-text">text</a> other
710: than a <a href="infrastructure.html#space-character">space character</a>, a U+003C LESS-THAN SIGN
711: character ('<'), or another U+0026 AMPERSAND (<code>&</code>)
1.123 mike 712: character.</p><h4 id="cdata-sections"><span class="secno">9.1.5 </span>CDATA sections</h4><p><dfn id="syntax-cdata" title="syntax-cdata">CDATA sections</dfn> must start with
1.1 mike 713: the character sequence U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
714: MARK, U+005B LEFT SQUARE BRACKET, U+0043 LATIN CAPITAL LETTER C,
715: U+0044 LATIN CAPITAL LETTER D, U+0041 LATIN CAPITAL LETTER A, U+0054
716: LATIN CAPITAL LETTER T, U+0041 LATIN CAPITAL LETTER A, U+005B LEFT
717: SQUARE BRACKET (<code title=""><![CDATA[</code>). Following this
718: sequence, the CDATA section may have <a href="#syntax-text" title="syntax-text">text</a>, with the additional restriction
719: that the text must not contain the three character sequence U+005D
720: RIGHT SQUARE BRACKET, U+005D RIGHT SQUARE BRACKET, U+003E
721: GREATER-THAN SIGN (<code title="">]]></code>). Finally, the CDATA
722: section must be ended by the three character sequence U+005D RIGHT
723: SQUARE BRACKET, U+005D RIGHT SQUARE BRACKET, U+003E GREATER-THAN
1.159 mike 724: SIGN (<code title="">]]></code>).</p><h4 id="comments"><span class="secno">9.1.6 </span>Comments</h4><p class="XXX annotation"><b>Status: </b><i>Working draft</i></p><p><dfn id="syntax-comments" title="syntax-comments">Comments</dfn> must start with the
1.1 mike 725: four character sequence U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
726: MARK, U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS (<code title=""><!--</code>). Following this sequence, the comment may
727: have <a href="#syntax-text" title="syntax-text">text</a>, with the additional
728: restriction that the text must not start with a single U+003E
729: GREATER-THAN SIGN ('>') character, nor start with a U+002D
730: HYPHEN-MINUS (<code title="">-</code>) character followed by a
731: U+003E GREATER-THAN SIGN ('>') character, nor contain two
732: consecutive U+002D HYPHEN-MINUS (<code title="">-</code>)
733: characters, nor end with a U+002D HYPHEN-MINUS (<code title="">-</code>) character. Finally, the comment must be ended by
734: the three character sequence U+002D HYPHEN-MINUS, U+002D
1.123 mike 735: HYPHEN-MINUS, U+003E GREATER-THAN SIGN (<code title="">--></code>).</p><div class="impl">
1.1 mike 736:
1.159 mike 737: <h3 id="parsing"><span class="secno">9.2 </span>Parsing HTML documents</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
1.1 mike 738:
739: <p><i>This section only applies to user agents, data mining tools,
740: and conformance checkers.</i></p>
741:
742: <p class="note">The rules for parsing XML documents into DOM trees
743: are covered by the next section, entitled "<a href="the-xhtml-syntax.html#the-xhtml-syntax">The XHTML
744: syntax</a>".</p>
745:
746: <p>For <a href="dom.html#html-documents">HTML documents</a>, user agents must use the parsing
747: rules described in this section to generate the DOM trees. Together,
748: these rules define what is referred to as the <dfn id="html-parser">HTML
749: parser</dfn>.</p>
750:
751: <div class="note">
752:
753: <p>While the HTML syntax described in this specification bears a
754: close resemblance to SGML and XML, it is a separate language with
755: its own parsing rules.</p>
756:
1.183 mike 757: <p>Some earlier versions of HTML (in particular from HTML2 to
758: HTML4) were based on SGML and used SGML parsing rules. However, few
1.1 mike 759: (if any) web browsers ever implemented true SGML parsing for HTML
760: documents; the only user agents to strictly handle HTML as an SGML
761: application have historically been validators. The resulting
762: confusion — with validators claiming documents to have one
763: representation while widely deployed Web browsers interoperably
764: implemented a different representation — has wasted decades
765: of productivity. This version of HTML thus returns to a non-SGML
766: basis.</p>
767:
768: <p>Authors interested in using SGML tools in their authoring
769: pipeline are encouraged to use XML tools and the XML serialization
770: of HTML.</p>
771:
772: </div>
773:
774: <p>This specification defines the parsing rules for HTML documents,
775: whether they are syntactically correct or not. Certain points in the
776: parsing algorithm are said to be <dfn id="parse-error" title="parse error">parse
777: errors</dfn>. The error handling for parse errors is well-defined:
778: user agents must either act as described below when encountering
779: such problems, or must abort processing at the first error that they
780: encounter for which they do not wish to apply the rules described
781: below.</p>
782:
783: <p>Conformance checkers must report at least one parse error
784: condition to the user if one or more parse error conditions exist in
785: the document and must not report parse error conditions if none
786: exist in the document. Conformance checkers may report more than one
1.174 mike 787: parse error condition if more than one parse error condition exists
1.1 mike 788: in the document. Conformance checkers are not required to recover
789: from parse errors.</p>
790:
791: <p class="note">Parse errors are only errors with the
792: <em>syntax</em> of HTML. In addition to checking for parse errors,
793: conformance checkers will also verify that the document obeys all
794: the other conformance requirements described in this
795: specification.</p>
796:
797: <p>For the purposes of conformance checkers, if a resource is
798: determined to be in <a href="#syntax">the HTML syntax</a>, then it is an
799: <a href="dom.html#html-documents" title="HTML documents">HTML document</a>.</p>
800:
801:
802: <h4 id="overview-of-the-parsing-model"><span class="secno">9.2.1 </span>Overview of the parsing model</h4>
803:
804: <p>The input to the HTML parsing process consists of a stream of
805: Unicode characters, which is passed through a
806: <a href="#tokenization">tokenization</a> stage followed by a <a href="#tree-construction">tree
807: construction</a> stage. The output is a <code>Document</code>
808: object.</p>
809:
810: <p class="note">Implementations that <a href="infrastructure.html#non-scripted">do not
811: support scripting</a> do not have to actually create a DOM
812: <code>Document</code> object, but the DOM tree in such cases is
813: still used as the model for the rest of the specification.</p>
814:
815: <p>In the common case, the data handled by the tokenization stage
1.159 mike 816: comes from the network, but <a href="embedded-content-0.html#dynamic-markup-insertion" title="dynamic markup
817: insertion">it can also come from script</a>, e.g. using the <code title="dom-document-write"><a href="embedded-content-0.html#dom-document-write">document.write()</a></code> API.</p>
1.1 mike 818:
819: <p><img alt="" src="images/parsing-model-overview.png"></p>
820:
821: <p id="nestedParsing">There is only one set of states for the
822: tokenizer stage and the tree construction stage, but the tree
823: construction stage is reentrant, meaning that while the tree
824: construction stage is handling one token, the tokenizer might be
825: resumed, causing further tokens to be emitted and processed before
826: the first token's processing is complete.</p>
827:
828: <div class="example">
829:
830: <p>In the following example, the tree construction stage will be
831: called upon to handle a "p" start tag token while handling the
832: "script" start tag token:</p>
833:
834: <pre>...
835: <script>
836: document.write('<p>');
837: </script>
838: ...</pre>
839:
840: </div>
841:
842: <p>To handle these cases, parsers have a <dfn id="script-nesting-level">script nesting
843: level</dfn>, which must be initially set to zero, and a <dfn id="parser-pause-flag">parser
844: pause flag</dfn>, which must be initially set to false.</p>
845:
846:
847:
848: <h4 id="the-input-stream"><span class="secno">9.2.2 </span>The <dfn>input stream</dfn></h4>
849:
850: <p>The stream of Unicode characters that comprises the input to the
851: tokenization stage will be initially seen by the user agent as a
852: stream of bytes (typically coming over the network or from the local
853: file system). The bytes encode the actual characters according to a
854: particular <em>character encoding</em>, which the user agent must
855: use to decode the bytes into characters.</p>
856:
857: <p class="note">For XML documents, the algorithm user agents must
858: use to determine the character encoding is given by the XML
1.104 mike 859: specification. This section does not apply to XML documents. <a href="references.html#refsXML">[XML]</a></p>
1.1 mike 860:
861:
1.168 mike 862: <h5 id="determining-the-character-encoding"><span class="secno">9.2.2.1 </span>Determining the character encoding</h5><p class="XXX annotation"><b>Status: </b><i>Working draft</i></p>
1.1 mike 863:
864: <p>In some cases, it might be impractical to unambiguously determine
865: the encoding before parsing the document. Because of this, this
866: specification provides for a two-pass mechanism with an optional
867: pre-scan. Implementations are allowed, as described below, to apply
868: a simplified parsing algorithm to whatever bytes they have available
869: before beginning to parse the document. Then, the real parser is
870: started, using a tentative encoding derived from this pre-parse and
871: other out-of-band metadata. If, while the document is being loaded,
872: the user agent discovers an encoding declaration that conflicts with
873: this information, then the parser can get reinvoked to perform a
874: parse of the document with the real encoding.</p>
875:
876: <p id="documentEncoding">User agents must use the following
877: algorithm (the <dfn id="encoding-sniffing-algorithm">encoding sniffing algorithm</dfn>) to determine
878: the character encoding to use when decoding a document in the first
879: pass. This algorithm takes as input any out-of-band metadata
880: available to the user agent (e.g. the <a href="infrastructure.html#content-type" title="Content-Type">Content-Type metadata</a> of the document)
881: and all the bytes available so far, and returns an encoding and a
882: <dfn id="concept-encoding-confidence" title="concept-encoding-confidence">confidence</dfn>. The
883: confidence is either <i>tentative</i>, <i>certain</i>, or
884: <i>irrelevant</i>. The encoding used, and whether the confidence in
885: that encoding is <i>tentative</i> or <i>certain</i>, is <a href="#meta-charset-during-parse">used during the parsing</a> to
886: determine whether to <a href="#change-the-encoding">change the encoding</a>. If no
887: encoding is necessary, e.g. because the parser is operating on a
888: stream of Unicode characters and doesn't have to use an encoding at
889: all, then the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
890: <i>irrelevant</i>.</p>
891:
892: <ol><li><p>If the transport layer specifies an encoding, and it is
893: supported, return that encoding with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
894: <i>certain</i>, and abort these steps.</p></li>
895:
896: <li><p>The user agent may wait for more bytes of the resource to be
897: available, either in this step or at any later step in this
898: algorithm. For instance, a user agent might wait 500ms or 512
899: bytes, whichever came first. In general preparsing the source to
900: find the encoding improves performance, as it reduces the need to
901: throw away the data structures used when parsing upon finding the
902: encoding information. However, if the user agent delays too long to
903: obtain data to determine the encoding, then the cost of the delay
904: could outweigh any performance improvements from the
905: preparse.</p></li>
906:
907: <li><p>For each of the rows in the following table, starting with
908: the first one and going down, if there are as many or more bytes
909: available than the number of bytes in the first column, and the
910: first bytes of the file match the bytes given in the first column,
911: then return the encoding given in the cell in the second column of
912: that row, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
913: <i>certain</i>, and abort these steps:</p>
914:
915: <!-- this table is present in several forms in this file; keep them in sync -->
916: <table><thead><tr><th>Bytes in Hexadecimal
917: </th><th>Encoding
918: </th></tr></thead><tbody><!-- nobody uses this
919: <tr>
920: <td>00 00 FE FF
921: <td>UTF-32BE
922: <tr>
923: <td>FF FE 00 00
924: <td>UTF-32LE
925: --><tr><td>FE FF
926: </td><td>UTF-16BE
927: </td></tr><tr><td>FF FE
928: </td><td>UTF-16LE
929: </td></tr><tr><td>EF BB BF
930: </td><td>UTF-8
931: <!-- nobody uses this
932: <tr>
933: <td>DD 73 66 73
934: <td>UTF-EBCDIC
935: -->
936: </td></tr></tbody></table><p class="note">This step looks for Unicode Byte Order Marks
937: (BOMs).</p></li>
938:
939: <li><p>Otherwise, the user agent will have to search for explicit
940: character encoding information in the file itself. This should
941: proceed as follows:
942:
943: </p><p>Let <var title="">position</var> be a pointer to a byte in the
944: input stream, initially pointing at the first byte. If at any
945: point during these substeps the user agent either runs out of
946: bytes or decides that scanning further bytes would not be
947: efficient, then skip to the next step of the overall character
948: encoding detection algorithm. User agents may decide that scanning
949: <em>any</em> bytes is not efficient, in which case these substeps
950: are entirely skipped.</p>
951:
952: <p>Now, repeat the following "two" steps until the algorithm
953: aborts (either because user agent aborts, as described above, or
954: because a character encoding is found):</p>
955:
956: <ol><li><p>If <var title="">position</var> points to:</p>
957:
958: <dl class="switch"><dt>A sequence of bytes starting with: 0x3C 0x21 0x2D 0x2D (ASCII '<!--')</dt>
959: <dd>
960:
961: <p>Advance the <var title="">position</var> pointer so that it
962: points at the first 0x3E byte which is preceded by two 0x2D
963: bytes (i.e. at the end of an ASCII '-->' sequence) and comes
964: after the 0x3C byte that was found. (The two 0x2D bytes can be
965: the same as the those in the '<!--' sequence.)</p>
966:
967: </dd>
968:
969: <dt>A sequence of bytes starting with: 0x3C, 0x4D or 0x6D, 0x45 or 0x65, 0x54 or 0x74, 0x41 or 0x61, and finally one of 0x09, 0x0A, 0x0C, 0x0D, 0x20, 0x2F (case-insensitive ASCII '<meta' followed by a space or slash)</dt>
970: <dd>
971:
972: <ol><li><p>Advance the <var title="">position</var> pointer so
973: that it points at the next 0x09, 0x0A, 0x0C, 0x0D, 0x20, or
974: 0x2F byte (the one in sequence of characters matched
975: above).</p></li>
976:
977: <li><p><a href="#concept-get-attributes-when-sniffing" title="concept-get-attributes-when-sniffing">Get
978: an attribute</a> and its value. If no attribute was
979: sniffed, then skip this inner set of steps, and jump to the
980: second step in the overall "two step" algorithm.</p></li>
981:
982: <li><p>If the attribute's name is neither "<code title="">charset</code>" nor "<code title="">content</code>",
983: then return to step 2 in these inner steps.</p></li>
984:
985: <li><p>If the attribute's name is "<code title="">charset</code>", let <var title="">charset</var> be
986: the attribute's value, interpreted as a character
987: encoding.</p></li>
988:
989: <li><p>Otherwise, the attribute's name is "<code title="">content</code>": apply the <a href="infrastructure.html#algorithm-for-extracting-an-encoding-from-a-content-type">algorithm for
990: extracting an encoding from a Content-Type</a>, giving the
991: attribute's value as the string to parse. If an encoding is
992: returned, let <var title="">charset</var> be that
993: encoding. Otherwise, return to step 2 in these inner
994: steps.</p></li>
995:
996: <li><p>If <var title="">charset</var> is a UTF-16 encoding,
997: change the value of <var title="">charset</var> to
998: UTF-8.</p></li>
999:
1000: <li><p>If <var title="">charset</var> is a supported
1001: character encoding, then return the given encoding, with
1002: <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1003: <i>tentative</i>, and abort all these steps.</p></li>
1004:
1005: <li><p>Otherwise, return to step 2 in these inner
1006: steps.</p></li>
1007:
1008: </ol></dd>
1009:
1010: <dt>A sequence of bytes starting with a 0x3C byte (ASCII '<'), optionally a 0x2F byte (ASCII '/'), and finally a byte in the range 0x41-0x5A or 0x61-0x7A (an ASCII letter)</dt>
1011: <dd>
1012:
1013: <ol><li><p>Advance the <var title="">position</var> pointer so
1014: that it points at the next 0x09 (ASCII TAB), 0x0A (ASCII LF),
1015: 0x0C (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E
1016: (ASCII '>') byte.</p></li>
1017:
1018: <li><p>Repeatedly <a href="#concept-get-attributes-when-sniffing" title="concept-get-attributes-when-sniffing">get an
1019: attribute</a> until no further attributes can be found,
1020: then jump to the second step in the overall "two step"
1021: algorithm.</p></li>
1022:
1023: </ol></dd>
1024:
1025: <dt>A sequence of bytes starting with: 0x3C 0x21 (ASCII '<!')</dt>
1026: <dt>A sequence of bytes starting with: 0x3C 0x2F (ASCII '</')</dt>
1027: <dt>A sequence of bytes starting with: 0x3C 0x3F (ASCII '<?')</dt>
1028: <dd>
1029:
1030: <p>Advance the <var title="">position</var> pointer so that it
1031: points at the first 0x3E byte (ASCII '>') that comes after the
1032: 0x3C byte that was found.</p>
1033:
1034: </dd>
1035:
1036: <dt>Any other byte</dt>
1037: <dd>
1038:
1039: <p>Do nothing with that byte.</p>
1040:
1041: </dd>
1042:
1043: </dl></li>
1044:
1045: <li>Move <var title="">position</var> so it points at the next
1046: byte in the input stream, and return to the first step of this
1047: "two step" algorithm.</li>
1048:
1049: </ol><p>When the above "two step" algorithm says to <dfn id="concept-get-attributes-when-sniffing" title="concept-get-attributes-when-sniffing">get an
1050: attribute</dfn>, it means doing this:</p>
1051:
1052: <ol><li><p>If the byte at <var title="">position</var> is one of 0x09
1053: (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII FF), 0x0D (ASCII CR),
1054: 0x20 (ASCII space), or 0x2F (ASCII '/') then advance <var title="">position</var> to the next byte and redo this
1055: substep.</p></li>
1056:
1057: <li><p>If the byte at <var title="">position</var> is 0x3E (ASCII
1058: '>'), then abort the "get an attribute" algorithm. There isn't
1059: one.</p></li>
1060:
1061: <li><p>Otherwise, the byte at <var title="">position</var> is the
1062: start of the attribute name. Let <var title="">attribute
1063: name</var> and <var title="">attribute value</var> be the empty
1064: string.</p></li>
1065:
1066: <li><p><i>Attribute name</i>: Process the byte at <var title="">position</var> as follows:</p>
1067:
1068: <dl class="switch"><dt>If it is 0x3D (ASCII '='), and the <var title="">attribute
1069: name</var> is longer than the empty string</dt>
1070:
1071: <dd>Advance <var title="">position</var> to the next byte and
1072: jump to the step below labeled <i>value</i>.</dd>
1073:
1074: <dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII
1075: FF), 0x0D (ASCII CR), or 0x20 (ASCII space)</dt>
1076:
1077: <dd>Jump to the step below labeled <i>spaces</i>.</dd>
1078:
1079: <dt>If it is 0x2F (ASCII '/') or 0x3E (ASCII '>')</dt>
1080:
1081: <dd>Abort the "get an attribute" algorithm. The attribute's
1082: name is the value of <var title="">attribute name</var>, its
1083: value is the empty string.</dd>
1084:
1085: <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
1086: 'Z')</dt>
1087:
1088: <dd>Append the Unicode character with code point <span title=""><var title="">b</var>+0x20</span> to <var title="">attribute
1089: name</var> (where <var title="">b</var> is the value of the
1090: byte at <var title="">position</var>).</dd>
1091:
1092: <dt>Anything else</dt>
1093:
1094: <dd>Append the Unicode character with the same code point as the
1095: value of the byte at <var title="">position</var>) to <var title="">attribute name</var>. (It doesn't actually matter how
1096: bytes outside the ASCII range are handled here, since only
1097: ASCII characters can contribute to the detection of a character
1098: encoding.)</dd>
1099:
1100: </dl></li>
1101:
1102: <li><p>Advance <var title="">position</var> to the next byte and
1103: return to the previous step.</p></li>
1104:
1105: <li><p><i>Spaces</i>: If the byte at <var title="">position</var> is one of 0x09 (ASCII TAB), 0x0A (ASCII
1106: LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then
1107: advance <var title="">position</var> to the next byte, then,
1108: repeat this step.</p></li>
1109:
1110: <li><p>If the byte at <var title="">position</var> is
1111: <em>not</em> 0x3D (ASCII '='), abort the "get an attribute"
1112: algorithm. The attribute's name is the value of <var title="">attribute name</var>, its value is the empty
1113: string.</p></li>
1114:
1115: <li><p>Advance <var title="">position</var> past the 0x3D (ASCII
1116: '=') byte.</p></li>
1117:
1118: <li><p><i>Value:</i> If the byte at <var title="">position</var> is one of 0x09 (ASCII TAB), 0x0A (ASCII
1119: LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then
1120: advance <var title="">position</var> to the next byte, then,
1121: repeat this step.</p></li>
1122:
1123: <li><p>Process the byte at <var title="">position</var> as
1124: follows:</p>
1125:
1126: <dl class="switch"><dt>If it is 0x22 (ASCII '"') or 0x27 ("'")</dt>
1127:
1128: <dd>
1129:
1130: <ol><li>Let <var title="">b</var> be the value of the byte at
1131: <var title="">position</var>.</li>
1132:
1133: <li>Advance <var title="">position</var> to the next
1134: byte.</li>
1135:
1136: <li>If the value of the byte at <var title="">position</var>
1137: is the value of <var title="">b</var>, then advance <var title="">position</var> to the next byte and abort the "get
1138: an attribute" algorithm. The attribute's name is the value of
1139: <var title="">attribute name</var>, and its value is the
1140: value of <var title="">attribute value</var>.</li>
1141:
1142: <li>Otherwise, if the value of the byte at <var title="">position</var> is in the range 0x41 (ASCII 'A') to
1143: 0x5A (ASCII 'Z'), then append a Unicode character to <var title="">attribute value</var> whose code point is 0x20 more
1144: than the value of the byte at <var title="">position</var>.</li>
1145:
1146: <li>Otherwise, append a Unicode character to <var title="">attribute value</var> whose code point is the same as
1147: the value of the byte at <var title="">position</var>.</li>
1148:
1149: <li>Return to the second step in these substeps.</li>
1150:
1151: </ol></dd>
1152:
1153: <dt>If it is 0x3E (ASCII '>')</dt>
1154:
1155: <dd>Abort the "get an attribute" algorithm. The attribute's
1156: name is the value of <var title="">attribute name</var>, its
1157: value is the empty string.</dd>
1158:
1159:
1160: <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
1161: 'Z')</dt>
1162:
1163: <dd>Append the Unicode character with code point <span title=""><var title="">b</var>+0x20</span> to <var title="">attribute
1164: value</var> (where <var title="">b</var> is the value of the
1165: byte at <var title="">position</var>). Advance <var title="">position</var> to the next byte.</dd>
1166:
1167: <dt>Anything else</dt>
1168:
1169: <dd>Append the Unicode character with the same code point as the
1170: value of the byte at <var title="">position</var>) to <var title="">attribute value</var>. Advance <var title="">position</var> to the next byte.</dd>
1171:
1172: </dl></li>
1173:
1174: <li><p>Process the byte at <var title="">position</var> as
1175: follows:</p>
1176:
1177: <dl class="switch"><dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII
1178: FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E (ASCII
1179: '>')</dt>
1180:
1181: <dd>Abort the "get an attribute" algorithm. The attribute's
1182: name is the value of <var title="">attribute name</var> and its
1183: value is the value of <var title="">attribute value</var>.</dd>
1184:
1185: <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
1186: 'Z')</dt>
1187:
1188: <dd>Append the Unicode character with code point <span title=""><var title="">b</var>+0x20</span> to <var title="">attribute
1189: value</var> (where <var title="">b</var> is the value of the
1190: byte at <var title="">position</var>).</dd>
1191:
1192: <dt>Anything else</dt>
1193:
1194: <dd>Append the Unicode character with the same code point as the
1195: value of the byte at <var title="">position</var>) to <var title="">attribute value</var>.</dd>
1196:
1197: </dl></li>
1198:
1199: <li><p>Advance <var title="">position</var> to the next byte and
1200: return to the previous step.</p></li>
1201:
1202: </ol><p>For the sake of interoperability, user agents should not use a
1203: pre-scan algorithm that returns different results than the one
1204: described above. (But, if you do, please at least let us know, so
1205: that we can improve this algorithm and benefit everyone...)</p>
1206:
1207: </li>
1208:
1209: <li><p>If the user agent has information on the likely encoding for
1210: this page, e.g. based on the encoding of the page when it was last
1211: visited, then return that encoding, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1212: <i>tentative</i>, and abort these steps.</p></li>
1213:
1214: <li><p>The user agent may attempt to autodetect the character
1215: encoding from applying frequency analysis or other algorithms to
1216: the data stream. If autodetection succeeds in determining a
1217: character encoding, then return that encoding, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1.104 mike 1218: <i>tentative</i>, and abort these steps. <a href="references.html#refsUNIVCHARDET">[UNIVCHARDET]</a></p></li>
1.1 mike 1219:
1220: <li><p>Otherwise, return an implementation-defined or
1221: user-specified default character encoding, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1222: <i>tentative</i>. In non-legacy environments, the more
1223: comprehensive <code title="">UTF-8</code> encoding is
1224: recommended. Due to its use in legacy content, <code title="">windows-1252</code> is recommended as a default in
1.187 mike 1225: predominantly Western demographics instead.</p></li>
1.1 mike 1226:
1227: </ol><p>The <a href="dom.html#document-s-character-encoding">document's character encoding</a> must immediately
1228: be set to the value returned from this algorithm, at the same time
1229: as the user agent uses the returned value to select the decoder to
1230: use for the input stream.</p>
1231:
1232:
1233:
1234: <h5 id="preprocessing-the-input-stream"><span class="secno">9.2.2.2 </span>Preprocessing the input stream</h5>
1235:
1236: <p>Given an encoding, the bytes in the input stream must be
1237: converted to Unicode characters for the tokenizer, as described by
1238: the rules for that encoding, except that the leading U+FEFF BYTE
1239: ORDER MARK character, if any, must not be stripped by the encoding
1240: layer (it is stripped by the rule below).</p> <!-- this is to
1241: prevent two leading BOMs from being both stripped, once by the
1242: decoder, and once by the parser -->
1243:
1244: <p>Bytes or sequences of bytes in the original byte stream that
1245: could not be converted to Unicode characters must be converted to
1246: U+FFFD REPLACEMENT CHARACTER code points.</p>
1247:
1248: <p class="note">Bytes or sequences of bytes in the original byte
1249: stream that did not conform to the encoding specification
1250: (e.g. invalid UTF-8 byte sequences in a UTF-8 input stream) are
1251: errors that conformance checkers are expected to report.</p>
1252:
1253: <p>Any byte or sequences of bytes in the original byte stream that
1254: is <a href="infrastructure.html#misinterpreted-for-compatibility">misinterpreted for compatibility</a> is a <a href="#parse-error">parse
1255: error</a>.</p>
1256:
1257: <p>One leading U+FEFF BYTE ORDER MARK character must be ignored if
1258: any are present.</p>
1259:
1260: <p>All U+0000 NULL characters in the input must be replaced by
1261: U+FFFD REPLACEMENT CHARACTERs. Any occurrences of such characters is
1262: a <a href="#parse-error">parse error</a>.</p>
1263:
1264: <p>Any occurrences of any characters in the ranges U+0001 to U+0008,
1265: <!-- HT, LF allowed --> <!-- U+000B is in the next list --> <!-- FF,
1266: CR allowed --> U+000E to U+001F, <!-- ASCII allowed --> U+007F
1267: <!--to U+0084, (U+0085 NEL not allowed), U+0086--> to U+009F, U+D800
1268: to U+DFFF<!-- surrogates not allowed -->, U+FDD0 to U+FDEF, and
1269: characters U+000B, U+FFFE, U+FFFF, U+1FFFE, U+1FFFF, U+2FFFE,
1270: U+2FFFF, U+3FFFE, U+3FFFF, U+4FFFE, U+4FFFF, U+5FFFE, U+5FFFF,
1271: U+6FFFE, U+6FFFF, U+7FFFE, U+7FFFF, U+8FFFE, U+8FFFF, U+9FFFE,
1272: U+9FFFF, U+AFFFE, U+AFFFF, U+BFFFE, U+BFFFF, U+CFFFE, U+CFFFF,
1273: U+DFFFE, U+DFFFF, U+EFFFE, U+EFFFF, U+FFFFE, U+FFFFF, U+10FFFE, and
1274: U+10FFFF are <a href="#parse-error" title="parse error">parse errors</a>. (These
1275: are all control characters or permanently undefined Unicode
1276: characters.)</p>
1277:
1278: <p>U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF)
1279: characters are treated specially. Any CR characters that are
1280: followed by LF characters must be removed, and any CR characters not
1281: followed by LF characters must be converted to LF characters. Thus,
1282: newlines in HTML DOMs are represented by LF characters, and there
1283: are never any CR characters in the input to the
1284: <a href="#tokenization">tokenization</a> stage.</p>
1285:
1286: <p>The <dfn id="next-input-character">next input character</dfn> is the first character in the
1287: input stream that has not yet been <dfn id="consumed">consumed</dfn>. Initially,
1288: the <i><a href="#next-input-character">next input character</a></i> is the first character in the
1289: input. The <dfn id="current-input-character">current input character</dfn> is the last character
1290: to have been <i><a href="#consumed">consumed</a></i>.</p>
1291:
1292: <p>The <dfn id="insertion-point">insertion point</dfn> is the position (just before a
1293: character or just before the end of the input stream) where content
1.159 mike 1294: inserted using <code title="dom-document-write"><a href="embedded-content-0.html#dom-document-write">document.write()</a></code> is actually
1.1 mike 1295: inserted. The insertion point is relative to the position of the
1296: character immediately after it, it is not an absolute offset into
1297: the input stream. Initially, the insertion point is
1.10 mike 1298: undefined.</p>
1.1 mike 1299:
1300: <p>The "EOF" character in the tables below is a conceptual character
1301: representing the end of the <a href="#the-input-stream">input stream</a>. If the parser
1.159 mike 1302: is a <a href="embedded-content-0.html#script-created-parser">script-created parser</a>, then the end of the
1.1 mike 1303: <a href="#the-input-stream">input stream</a> is reached when an <dfn id="explicit-eof-character">explicit "EOF"
1.159 mike 1304: character</dfn> (inserted by the <code title="dom-document-close"><a href="embedded-content-0.html#dom-document-close">document.close()</a></code> method) is
1.1 mike 1305: consumed. Otherwise, the "EOF" character is not a real character in
1306: the stream, but rather the lack of any further characters.</p>
1307:
1308:
1309: <h5 id="changing-the-encoding-while-parsing"><span class="secno">9.2.2.3 </span>Changing the encoding while parsing</h5>
1310:
1311: <p>When the parser requires the user agent to <dfn id="change-the-encoding">change the
1312: encoding</dfn>, it must run the following steps. This might happen
1313: if the <a href="#encoding-sniffing-algorithm">encoding sniffing algorithm</a> described above
1314: failed to find an encoding, or if it found an encoding that was not
1315: the actual encoding of the file.</p>
1316:
1317: <ol><li>If the new encoding is identical or equivalent to the encoding
1318: that is already being used to interpret the input stream, then set
1319: the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1320: <i>certain</i> and abort these steps. This happens when the
1321: encoding information found in the file matches what the
1322: <a href="#encoding-sniffing-algorithm">encoding sniffing algorithm</a> determined to be the
1323: encoding, and in the second pass through the parser if the first
1324: pass found that the encoding sniffing algorithm described in the
1325: earlier section failed to find the right encoding.</li>
1326:
1327: <li>If the encoding that is already being used to interpret the
1328: input stream is a UTF-16 encoding, then set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1329: <i>certain</i> and abort these steps. The new encoding is ignored;
1330: if it was anything but the same encoding, then it would be clearly
1331: incorrect.</li>
1332:
1333: <li>If the new encoding is a UTF-16 encoding, change it to
1334: UTF-8.</li>
1335:
1336: <li>If all the bytes up to the last byte converted by the current
1337: decoder have the same Unicode interpretations in both the current
1338: encoding and the new encoding, and if the user agent supports
1339: changing the converter on the fly, then the user agent may change
1340: to the new converter for the encoding on the fly. Set the
1341: <a href="dom.html#document-s-character-encoding">document's character encoding</a> and the encoding used to
1342: convert the input stream to the new encoding, set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1343: <i>certain</i>, and abort these steps.</li>
1344:
1345: <li>Otherwise, <a href="history.html#navigate">navigate</a> to the document again, with
1346: <a href="history.html#replacement-enabled">replacement enabled</a>, and using the same <a href="history.html#source-browsing-context">source
1347: browsing context</a>, but this time skip the <a href="#encoding-sniffing-algorithm">encoding
1348: sniffing algorithm</a> and instead just set the encoding to the
1349: new encoding and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1350: <i>certain</i>. Whenever possible, this should be done without
1351: actually contacting the network layer (the bytes should be
1352: re-parsed from memory), even if, e.g., the document is marked as
1353: not being cacheable. If this is not possible and contacting the
1354: network layer would involve repeating a request that uses a method
1355: other than HTTP GET (<a href="infrastructure.html#concept-http-equivalent-get" title="concept-http-equivalent-get">or
1356: equivalent</a> for non-HTTP URLs), then instead set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1357: <i>certain</i> and ignore the new encoding. The resource will be
1358: misinterpreted. User agents may notify the user of the situation,
1359: to aid in application development.</li>
1360:
1361: </ol><h4 id="parse-state"><span class="secno">9.2.3 </span>Parse state</h4>
1362:
1363: <h5 id="the-insertion-mode"><span class="secno">9.2.3.1 </span>The insertion mode</h5>
1364:
1365: <p>The <dfn id="insertion-mode">insertion mode</dfn> is a state variable that controls
1366: the primary operation of the tree construction stage.</p>
1367:
1368: <p>Initially, the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-initial-insertion-mode" title="insertion mode: initial">initial</a>". It can change to
1369: "<a href="#the-before-html-insertion-mode" title="insertion mode: before html">before html</a>",
1370: "<a href="#the-before-head-insertion-mode" title="insertion mode: before head">before head</a>",
1371: "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>", "<a href="#parsing-main-inheadnoscript" title="insertion mode: in head noscript">in head noscript</a>",
1.91 mike 1372: "<a href="#the-after-head-insertion-mode" title="insertion mode: after head">after head</a>", "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>", "<a href="#parsing-main-incdata" title="insertion mode: in RAWTEXT/RCDATA">in RAWTEXT/RCDATA</a>",
1.1 mike 1373: "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>", "<a href="#parsing-main-intabletext" title="insertion mode: in table text">in table text</a>", "<a href="#parsing-main-incaption" title="insertion mode: in caption">in caption</a>", "<a href="#parsing-main-incolgroup" title="insertion mode: in column group">in column group</a>",
1374: "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table body</a>",
1375: "<a href="#parsing-main-intr" title="insertion mode: in row">in row</a>", "<a href="#parsing-main-intd" title="insertion mode: in cell">in cell</a>", "<a href="#parsing-main-inselect" title="insertion mode: in select">in select</a>", "<a href="#parsing-main-inselectintable" title="insertion mode: in select in table">in select in
1376: table</a>", "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in
1377: foreign content</a>", "<a href="#parsing-main-afterbody" title="insertion mode: after
1378: body">after body</a>", "<a href="#parsing-main-inframeset" title="insertion mode: in
1379: frameset">in frameset</a>", "<a href="#parsing-main-afterframeset" title="insertion mode: after
1380: frameset">after frameset</a>", "<a href="#the-after-after-body-insertion-mode" title="insertion mode:
1381: after after body">after after body</a>", and "<a href="#the-after-after-frameset-insertion-mode" title="insertion mode: after after frameset">after after
1382: frameset</a>" during the course of the parsing, as described in
1383: the <a href="#tree-construction">tree construction</a> stage. The insertion mode affects
1384: how tokens are processed and whether CDATA sections are
1385: supported.</p>
1386:
1387: <p>Seven of these modes, namely "<a href="#parsing-main-inhead" title="insertion mode: in
1388: head">in head</a>", "<a href="#parsing-main-inbody" title="insertion mode: in body">in
1389: body</a>", "<a href="#parsing-main-intable" title="insertion mode: in table">in
1390: table</a>", "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
1391: body</a>", "<a href="#parsing-main-intr" title="insertion mode: in row">in row</a>",
1392: "<a href="#parsing-main-intd" title="insertion mode: in cell">in cell</a>", and "<a href="#parsing-main-inselect" title="insertion mode: in select">in select</a>", are special, in
1393: that the other modes defer to them at various times. When the
1394: algorithm below says that the user agent is to do something
1395: "<dfn id="using-the-rules-for">using the rules for</dfn> the <var title="">m</var> insertion
1396: mode", where <var title="">m</var> is one of these modes, the user
1397: agent must use the rules described under the <var title="">m</var>
1398: <a href="#insertion-mode">insertion mode</a>'s section, but must leave the
1399: <a href="#insertion-mode">insertion mode</a> unchanged unless the rules in <var title="">m</var> themselves switch the <a href="#insertion-mode">insertion mode</a>
1400: to a new value.</p>
1401:
1402: <p>When the insertion mode is switched to "<a href="#parsing-main-incdata" title="insertion
1.91 mike 1403: mode: in RAWTEXT/RCDATA">in RAWTEXT/RCDATA</a>" or "<a href="#parsing-main-intabletext" title="insertion mode: in table text">in table text</a>", the
1.1 mike 1404: <dfn id="original-insertion-mode">original insertion mode</dfn> is also set. This is the
1405: insertion mode to which the tree construction stage will return.</p>
1406:
1407: <p>When the insertion mode is switched to "<a href="#parsing-main-inforeign" title="insertion
1408: mode: in foreign content">in foreign content</a>", the
1409: <dfn id="secondary-insertion-mode">secondary insertion mode</dfn> is also set. This secondary mode
1410: is used within the rules for the "<a href="#parsing-main-inforeign" title="insertion mode: in
1411: foreign content">in foreign content</a>" mode to handle HTML
1412: (i.e. not foreign) content.</p>
1413:
1414: <hr><p>When the steps below require the UA to <dfn id="reset-the-insertion-mode-appropriately">reset the insertion
1415: mode appropriately</dfn>, it means the UA must follow these
1416: steps:</p>
1417:
1418: <ol><li>Let <var title="">last</var> be false.</li>
1419:
1420: <li>Let <var title="">node</var> be the last node in the
1421: <a href="#stack-of-open-elements">stack of open elements</a>.</li>
1422:
1423: <li>If <var title="">node</var> is the first node in the stack of
1424: open elements, then set <var title="">last</var> to true and set
1425: <var title="">node</var> to the <var title="">context</var>
1426: element. (<a href="#fragment-case">fragment case</a>)</li>
1427:
1428: <li>If <var title="">node</var> is a <code><a href="forms.html#the-select-element">select</a></code> element,
1429: then switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inselect" title="insertion mode: in select">in select</a>" and abort these
1430: steps. (<a href="#fragment-case">fragment case</a>)</li>
1431:
1432: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-td-element">td</a></code> or
1433: <code><a href="tabular-data.html#the-th-element">th</a></code> element and <var title="">last</var> is false, then
1434: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intd" title="insertion
1435: mode: in cell">in cell</a>" and abort these steps.</li>
1436:
1437: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, then
1438: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intr" title="insertion
1439: mode: in row">in row</a>" and abort these steps.</li>
1440:
1441: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>,
1442: <code><a href="tabular-data.html#the-thead-element">thead</a></code>, or <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element, then switch the
1443: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intbody" title="insertion mode: in
1444: table body">in table body</a>" and abort these steps.</li>
1445:
1446: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-caption-element">caption</a></code> element,
1447: then switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incaption" title="insertion mode: in caption">in caption</a>" and abort
1448: these steps.</li>
1449:
1450: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element,
1451: then switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incolgroup" title="insertion mode: in column group">in column group</a>" and
1452: abort these steps. (<a href="#fragment-case">fragment case</a>)</li>
1453:
1454: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-table-element">table</a></code> element,
1455: then switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>" and abort these
1456: steps.</li>
1457:
1458: <li>If <var title="">node</var> is an element from the <a href="#mathml-namespace">MathML
1459: namespace</a> or the <a href="#svg-namespace">SVG namespace</a>, then switch the
1460: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inforeign" title="insertion mode: in
1461: foreign content">in foreign content</a>", let the
1462: <a href="#secondary-insertion-mode">secondary insertion mode</a> be "<a href="#parsing-main-inbody" title="insertion
1463: mode: in body">in body</a>", and abort these steps.</li>
1464:
1.159 mike 1465: <li>If <var title="">node</var> is a <code><a href="semantics.html#the-head-element-0">head</a></code> element,
1.1 mike 1466: then switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" ("<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>"! <em> not "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>"</em>!) and abort
1467: these steps. (<a href="#fragment-case">fragment case</a>)</li> <!-- This is only
1468: here for now in case people think that the spec accidentally
1469: omitted it and try to "fix" it. Note that noscript-in-head is also
1470: handled this way. This is all intentional. The only thing it
1471: doesn't handle is the scripting-disabled fragment parsing case for
1472: a <head> element containing a <noscript> which itself contains
1473: something other than a <link> or a <style> element; you'd expect
1474: that to break out of the <noscript> but it doesn't. This is an edge
1475: case that doesn't affect the spec, since the algorithm for fragment
1476: parsing is only used for innerHTML/outerHTML/insertAdjacentHTML(),
1477: where we know scripting is enabled. (XXX except maybe if innerHTML
1478: is set from another browsing context on a document with designMode
1479: set?) -->
1480:
1.159 mike 1481: <li>If <var title="">node</var> is a <code><a href="semantics.html#the-body-element-0">body</a></code> element,
1.1 mike 1482: then switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" and abort these
1483: steps.</li>
1484:
1.5 mike 1485: <li>If <var title="">node</var> is a <code><a href="obsolete.html#frameset">frameset</a></code> element,
1.1 mike 1486: then switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inframeset" title="insertion mode: in frameset">in frameset</a>" and abort
1487: these steps. (<a href="#fragment-case">fragment case</a>)</li>
1488:
1.159 mike 1489: <li>If <var title="">node</var> is an <code><a href="semantics.html#the-html-element-0">html</a></code> element,
1.1 mike 1490: then: if the <a href="#head-element-pointer"><code title="">head</code> element
1491: pointer</a> is null, switch the <a href="#insertion-mode">insertion mode</a> to
1492: "<a href="#the-before-head-insertion-mode" title="insertion mode: before head">before head</a>",
1493: otherwise, switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-after-head-insertion-mode" title="insertion mode: after head">after head</a>". In either
1494: case, abort these steps. (<a href="#fragment-case">fragment case</a>)</li> <!-- XXX
1495: can the head element pointer ever be non-null when we're going
1496: through these steps? -->
1497:
1498: <li>If <var title="">last</var> is true, then switch the
1499: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inbody" title="insertion mode: in
1500: body">in body</a>" and abort these steps. (<a href="#fragment-case">fragment
1501: case</a>)</li>
1502:
1503: <li>Let <var title="">node</var> now be the node before <var title="">node</var> in the <a href="#stack-of-open-elements">stack of open
1504: elements</a>.</li>
1505:
1506: <li>Return to step 3.</li>
1507:
1508: </ol><h5 id="the-stack-of-open-elements"><span class="secno">9.2.3.2 </span>The stack of open elements</h5>
1509:
1510: <p>Initially, the <dfn id="stack-of-open-elements">stack of open elements</dfn> is empty. The
1511: stack grows downwards; the topmost node on the stack is the first
1512: one added to the stack, and the bottommost node of the stack is the
1513: most recently added node in the stack (notwithstanding when the
1514: stack is manipulated in a random access fashion as part of <a href="#adoptionAgency">the handling for misnested tags</a>).</p>
1515:
1516: <p>The "<a href="#the-before-html-insertion-mode" title="insertion mode: before html">before
1517: html</a>" <a href="#insertion-mode">insertion mode</a> creates the
1.159 mike 1518: <code><a href="semantics.html#the-html-element-0">html</a></code> root element node, which is then added to the
1.1 mike 1519: stack.</p>
1520:
1521: <p>In the <a href="#fragment-case">fragment case</a>, the <a href="#stack-of-open-elements">stack of open
1.159 mike 1522: elements</a> is initialized to contain an <code><a href="semantics.html#the-html-element-0">html</a></code>
1.1 mike 1523: element that is created as part of <a href="#html-fragment-parsing-algorithm" title="html fragment
1524: parsing algorithm">that algorithm</a>. (The <a href="#fragment-case">fragment
1525: case</a> skips the "<a href="#the-before-html-insertion-mode" title="insertion mode: before
1526: html">before html</a>" <a href="#insertion-mode">insertion mode</a>.)</p>
1527:
1.159 mike 1528: <p>The <code><a href="semantics.html#the-html-element-0">html</a></code> node, however it is created, is the topmost
1.1 mike 1529: node of the stack. It never gets popped off the stack.</p>
1530:
1531: <p>The <dfn id="current-node">current node</dfn> is the bottommost node in this
1532: stack.</p>
1533:
1534: <p>The <dfn id="current-table">current table</dfn> is the last <code><a href="tabular-data.html#the-table-element">table</a></code>
1535: element in the <a href="#stack-of-open-elements">stack of open elements</a>, if there is
1536: one. If there is no <code><a href="tabular-data.html#the-table-element">table</a></code> element in the <a href="#stack-of-open-elements">stack of
1537: open elements</a> (<a href="#fragment-case">fragment case</a>), then the
1538: <a href="#current-table">current table</a> is the first element in the <a href="#stack-of-open-elements">stack
1.159 mike 1539: of open elements</a> (the <code><a href="semantics.html#the-html-element-0">html</a></code> element).</p>
1.1 mike 1540:
1541: <p>Elements in the stack fall into the following categories:</p>
1542:
1543: <dl><dt><dfn id="special">Special</dfn></dt>
1544:
1545: <dd><p>The following HTML elements have varying levels of special
1546: parsing rules: <code><a href="semantics.html#the-address-element">address</a></code>, <code><a href="the-canvas-element.html#the-area-element">area</a></code>,
1547: <code><a href="semantics.html#the-article-element">article</a></code>, <code><a href="semantics.html#the-aside-element">aside</a></code>, <code><a href="semantics.html#the-base-element">base</a></code>,
1.5 mike 1548: <code><a href="obsolete.html#basefont">basefont</a></code>, <code>bgsound</code>,
1.159 mike 1549: <code><a href="semantics.html#the-blockquote-element">blockquote</a></code>, <code><a href="semantics.html#the-body-element-0">body</a></code>, <code><a href="semantics.html#the-br-element">br</a></code>,
1.5 mike 1550: <code><a href="obsolete.html#center">center</a></code>, <code><a href="tabular-data.html#the-col-element">col</a></code>, <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code>,
1.86 mike 1551: <code><a href="interactive-elements.html#the-command">command</a></code>, <!--v2DDATAGRID--><code>datagrid</code>,
1552: <code><a href="semantics.html#the-dd-element">dd</a></code>, <code><a href="interactive-elements.html#the-details-element">details</a></code>, <code><a href="semantics.html#the-dialog-element">dialog</a></code>,
1553: <code><a href="obsolete.html#dir">dir</a></code>, <code><a href="interactive-elements.html#the-div-element">div</a></code>, <code><a href="semantics.html#the-dl-element">dl</a></code>,
1.159 mike 1554: <code><a href="semantics.html#the-dt-element">dt</a></code>, <code><a href="text-level-semantics.html#the-embed-element">embed</a></code>, <code><a href="forms.html#the-fieldset-element">fieldset</a></code>,
1555: <code><a href="text-level-semantics.html#the-figure-element">figure</a></code>, <code><a href="semantics.html#the-footer-element">footer</a></code>, <code><a href="forms.html#the-form-element">form</a></code>,
1.86 mike 1556: <code><a href="obsolete.html#frame">frame</a></code>, <code><a href="obsolete.html#frameset">frameset</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h1</a></code>,
1557: <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h2</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h3</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h4</a></code>, <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h5</a></code>,
1.159 mike 1558: <code><a href="semantics.html#the-h1-h2-h3-h4-h5-and-h6-elements">h6</a></code>, <code><a href="semantics.html#the-head-element-0">head</a></code>, <code><a href="semantics.html#the-header-element">header</a></code>,
1559: <code><a href="semantics.html#the-hgroup-element">hgroup</a></code>, <code><a href="semantics.html#the-hr-element">hr</a></code>, <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code>, <!--
1.86 mike 1560: <code>image</code>, (commented out because this isn't an element
1561: that can end up on the stack, so it doesn't matter) -->
1.159 mike 1562: <code><a href="text-level-semantics.html#the-img-element">img</a></code>, <code><a href="forms.html#the-input-element">input</a></code>, <code><a href="obsolete.html#isindex-0">isindex</a></code>,
1.86 mike 1563: <code><a href="semantics.html#the-li-element">li</a></code>, <code><a href="semantics.html#the-link-element">link</a></code>, <code><a href="obsolete.html#listing">listing</a></code>,
1564: <code><a href="interactive-elements.html#menus">menu</a></code>, <code><a href="semantics.html#meta">meta</a></code>, <code><a href="semantics.html#the-nav-element">nav</a></code>,
1565: <code><a href="obsolete.html#noembed">noembed</a></code>, <code><a href="obsolete.html#noframes">noframes</a></code>, <code><a href="semantics.html#the-noscript-element">noscript</a></code>,
1.159 mike 1566: <code><a href="semantics.html#the-ol-element">ol</a></code>, <code><a href="semantics.html#the-p-element">p</a></code>, <code><a href="text-level-semantics.html#the-param-element">param</a></code>,
1.86 mike 1567: <code><a href="obsolete.html#plaintext">plaintext</a></code>, <code><a href="semantics.html#the-pre-element">pre</a></code>, <code><a href="semantics.html#script">script</a></code>,
1568: <code><a href="semantics.html#the-section-element">section</a></code>, <code><a href="forms.html#the-select-element">select</a></code>, <code><a href="obsolete.html#spacer">spacer</a></code>,
1569: <code><a href="semantics.html#the-style-element">style</a></code>, <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>, <code><a href="forms.html#the-textarea-element">textarea</a></code>,
1.159 mike 1570: <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code>, <code><a href="tabular-data.html#the-thead-element">thead</a></code>, <code><a href="semantics.html#the-title-element-0">title</a></code>,
1.174 mike 1571: <code><a href="tabular-data.html#the-tr-element">tr</a></code>, <code><a href="semantics.html#the-ul-element">ul</a></code>, <code>wbr</code>, and
1572: <code><a href="obsolete.html#xmp">xmp</a></code>.</p></dd>
1.1 mike 1573:
1574: <dt><dfn id="scoping">Scoping</dfn></dt>
1575: <dd><p>The following HTML elements introduce new <a href="#has-an-element-in-scope" title="has
1576: an element in scope">scopes</a> for various parts of the
1.5 mike 1577: parsing: <code><a href="obsolete.html#the-applet-element">applet</a></code>, <code><a href="forms.html#the-button-element">button</a></code>,
1.159 mike 1578: <code><a href="tabular-data.html#the-caption-element">caption</a></code>, <code><a href="semantics.html#the-html-element-0">html</a></code>, <code><a href="obsolete.html#the-marquee-element">marquee</a></code>,
1579: <code><a href="text-level-semantics.html#the-object-element">object</a></code>, <code><a href="tabular-data.html#the-table-element">table</a></code>, <code><a href="tabular-data.html#the-td-element">td</a></code>,
1.1 mike 1580: <code><a href="tabular-data.html#the-th-element">th</a></code>, and SVG's <code>foreignObject</code>.</p></dd>
1581:
1582: <dt><dfn id="formatting">Formatting</dfn></dt>
1583: <dd><p>The following HTML elements are those that end up in the
1584: <a href="#list-of-active-formatting-elements">list of active formatting elements</a>: <code><a href="text-level-semantics.html#the-a-element">a</a></code>,
1.5 mike 1585: <code><a href="text-level-semantics.html#the-b-element">b</a></code>, <code><a href="obsolete.html#big">big</a></code>, <code><a href="text-level-semantics.html#the-code-element">code</a></code>,
1586: <code><a href="text-level-semantics.html#the-em-element">em</a></code>, <code><a href="obsolete.html#font">font</a></code>, <code><a href="text-level-semantics.html#the-i-element">i</a></code>,
1587: <code>nobr</code>, <code><a href="obsolete.html#s">s</a></code>, <code><a href="text-level-semantics.html#the-small-element">small</a></code>,
1588: <code><a href="obsolete.html#strike">strike</a></code>, <code><a href="text-level-semantics.html#the-strong-element">strong</a></code>, <code><a href="obsolete.html#tt">tt</a></code>, and
1589: <code><a href="obsolete.html#u">u</a></code>.</p></dd>
1.1 mike 1590:
1591: <dt><dfn id="phrasing">Phrasing</dfn></dt>
1592: <dd><p>All other elements found while parsing an HTML
1593: document.</p></dd>
1594:
1595: </dl><p>The <a href="#stack-of-open-elements">stack of open elements</a> is said to <dfn id="has-an-element-in-scope" title="has an element in scope">have an element in scope</dfn> when
1596: the following algorithm terminates in a match state:</p>
1597:
1598: <ol><li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
1599: node</a> (the bottommost node of the stack).</p></li>
1600:
1601: <li><p>If <var title="">node</var> is the target node, terminate in
1602: a match state.</p></li>
1603:
1604: <li><p>Otherwise, if <var title="">node</var> is one of the
1605: following elements, terminate in a failure state:</p>
1.5 mike 1606: <ul class="brief"><li><code><a href="obsolete.html#the-applet-element">applet</a></code> in the HTML namespace</li>
1.1 mike 1607: <li><code><a href="tabular-data.html#the-caption-element">caption</a></code> in the HTML namespace</li>
1.159 mike 1608: <li><code><a href="semantics.html#the-html-element-0">html</a></code> in the HTML namespace</li> <!-- (This can only happen if the <var title="">node</var> is the topmost node of the <span>stack of open elements</span>, and prevents the next step from being invoked if there are no more elements in the stack.) -->
1.1 mike 1609: <li><code><a href="tabular-data.html#the-table-element">table</a></code> in the HTML namespace</li>
1610: <li><code><a href="tabular-data.html#the-td-element">td</a></code> in the HTML namespace</li>
1611: <li><code><a href="tabular-data.html#the-th-element">th</a></code> in the HTML namespace</li>
1612: <li><code><a href="forms.html#the-button-element">button</a></code> in the HTML namespace</li>
1.159 mike 1613: <li><code><a href="obsolete.html#the-marquee-element">marquee</a></code> in the HTML namespace</li>
1614: <li><code><a href="text-level-semantics.html#the-object-element">object</a></code> in the HTML namespace</li>
1.1 mike 1615: <li><code title="">foreignObject</code> in the SVG namespace</li>
1616: </ul></li>
1617:
1618: <li><p>Otherwise, set <var title="">node</var> to the previous
1619: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to step
1620: 2. (This will never fail, since the loop will always terminate in
1621: the previous step if the top of the stack — an
1.159 mike 1622: <code><a href="semantics.html#the-html-element-0">html</a></code> element — is reached.)</p></li>
1.1 mike 1623:
1624: </ol><p>The <a href="#stack-of-open-elements">stack of open elements</a> is said to <dfn id="has-an-element-in-table-scope" title="has an element in table scope">have an element in <em>table
1625: scope</em></dfn> when the following algorithm terminates in a match
1626: state:</p>
1627:
1628: <ol><li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
1629: node</a> (the bottommost node of the stack).</p></li>
1630:
1631: <li><p>If <var title="">node</var> is the target node, terminate in
1632: a match state.</p></li>
1633:
1634: <li><p>Otherwise, if <var title="">node</var> is one of the
1635: following elements, terminate in a failure state:</p>
1.159 mike 1636: <ul class="brief"><li><code><a href="semantics.html#the-html-element-0">html</a></code> in the HTML namespace</li> <!-- (This can only happen if the <var title="">node</var> is the topmost node of the <span>stack of open elements</span>, and prevents the next step from being invoked if there are no more elements in the stack.) -->
1.1 mike 1637: <li><code><a href="tabular-data.html#the-table-element">table</a></code> in the HTML namespace</li>
1638: </ul></li>
1639:
1640: <li><p>Otherwise, set <var title="">node</var> to the previous
1641: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to step
1642: 2. (This will never fail, since the loop will always terminate in
1643: the previous step if the top of the stack — an
1.159 mike 1644: <code><a href="semantics.html#the-html-element-0">html</a></code> element — is reached.)</p></li>
1.1 mike 1645:
1646: </ol><p>Nothing happens if at any time any of the elements in the
1647: <a href="#stack-of-open-elements">stack of open elements</a> are moved to a new location in,
1648: or removed from, the <code>Document</code> tree. In particular, the
1649: stack is not changed in this situation. This can cause, amongst
1650: other strange effects, content to be appended to nodes that are no
1651: longer in the DOM.</p>
1652:
1653: <p class="note">In some cases (namely, when <a href="#adoptionAgency">closing misnested formatting elements</a>),
1654: the stack is manipulated in a random-access fashion.</p>
1655:
1656:
1657: <h5 id="the-list-of-active-formatting-elements"><span class="secno">9.2.3.3 </span>The list of active formatting elements</h5>
1658:
1659: <p>Initially, the <dfn id="list-of-active-formatting-elements">list of active formatting elements</dfn> is
1660: empty. It is used to handle mis-nested <a href="#formatting" title="formatting">formatting element tags</a>.</p>
1661:
1662: <p>The list contains elements in the <a href="#formatting">formatting</a>
1663: category, and scope markers. The scope markers are inserted when
1.159 mike 1664: entering <code><a href="obsolete.html#the-applet-element">applet</a></code> elements, buttons, <code><a href="text-level-semantics.html#the-object-element">object</a></code>
1.1 mike 1665: elements, marquees, table cells, and table captions, and are used to
1.5 mike 1666: prevent formatting from "leaking" <em>into</em> <code><a href="obsolete.html#the-applet-element">applet</a></code>
1.159 mike 1667: elements, buttons, <code><a href="text-level-semantics.html#the-object-element">object</a></code> elements, marquees, and
1.1 mike 1668: tables.</p>
1669:
1670: <p class="note">The scope markers are unrelated to the concept of an
1671: element being <a href="#has-an-element-in-scope" title="has an element in scope">in
1672: scope</a>.</p>
1673:
1674: <p>In addition, each element in the <a href="#list-of-active-formatting-elements">list of active formatting
1675: elements</a> is associated with the token for which it was
1676: created, so that further elements can be created for that token if
1677: necessary.</p>
1678:
1679: <p>When the steps below require the UA to <dfn id="reconstruct-the-active-formatting-elements">reconstruct the
1680: active formatting elements</dfn>, the UA must perform the following
1681: steps:</p>
1682:
1683: <ol><li>If there are no entries in the <a href="#list-of-active-formatting-elements">list of active formatting
1684: elements</a>, then there is nothing to reconstruct; stop this
1685: algorithm.</li>
1686:
1687: <li>If the last (most recently added) entry in the <a href="#list-of-active-formatting-elements">list of
1688: active formatting elements</a> is a marker, or if it is an
1689: element that is in the <a href="#stack-of-open-elements">stack of open elements</a>, then
1690: there is nothing to reconstruct; stop this algorithm.</li>
1691:
1692: <li>Let <var title="">entry</var> be the last (most recently added)
1693: element in the <a href="#list-of-active-formatting-elements">list of active formatting
1694: elements</a>.</li>
1695:
1696: <li>If there are no entries before <var title="">entry</var> in the
1697: <a href="#list-of-active-formatting-elements">list of active formatting elements</a>, then jump to step
1698: 8.</li>
1699:
1700: <li>Let <var title="">entry</var> be the entry one earlier than
1701: <var title="">entry</var> in the <a href="#list-of-active-formatting-elements">list of active formatting
1702: elements</a>.</li>
1703:
1704: <li>If <var title="">entry</var> is neither a marker nor an element
1705: that is also in the <a href="#stack-of-open-elements">stack of open elements</a>, go to step
1706: 4.</li>
1707:
1708: <li>Let <var title="">entry</var> be the element one later than
1709: <var title="">entry</var> in the <a href="#list-of-active-formatting-elements">list of active formatting
1710: elements</a>.</li>
1711:
1712: <li><a href="#create-an-element-for-the-token">Create an element for the token</a> for which the
1713: element <var title="">entry</var> was created, to obtain <var title="">new element</var>.</li>
1714:
1715: <li>Append <var title="">new element</var> to the <a href="#current-node">current
1716: node</a> and push it onto the <a href="#stack-of-open-elements">stack of open
1717: elements</a> so that it is the new <a href="#current-node">current
1718: node</a>.</li>
1719:
1720: <li>Replace the entry for <var title="">entry</var> in the list
1721: with an entry for <var title="">new element</var>.</li>
1722:
1723: <li>If the entry for <var title="">new element</var> in the
1724: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> is not the last
1725: entry in the list, return to step 7.</li>
1726:
1727: </ol><p>This has the effect of reopening all the formatting elements that
1728: were opened in the current body, cell, or caption (whichever is
1729: youngest) that haven't been explicitly closed.</p>
1730:
1731: <p class="note">The way this specification is written, the
1732: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> always consists of
1733: elements in chronological order with the least recently added
1734: element first and the most recently added element last (except for
1735: while steps 8 to 11 of the above algorithm are being executed, of
1736: course).</p>
1737:
1738: <p>When the steps below require the UA to <dfn id="clear-the-list-of-active-formatting-elements-up-to-the-last-marker">clear the list of
1739: active formatting elements up to the last marker</dfn>, the UA must
1740: perform the following steps:</p>
1741:
1742: <ol><li>Let <var title="">entry</var> be the last (most recently added)
1743: entry in the <a href="#list-of-active-formatting-elements">list of active formatting elements</a>.</li>
1744:
1745: <li>Remove <var title="">entry</var> from the <a href="#list-of-active-formatting-elements">list of active
1746: formatting elements</a>.</li>
1747:
1748: <li>If <var title="">entry</var> was a marker, then stop the
1749: algorithm at this point. The list has been cleared up to the last
1750: marker.</li>
1751:
1752: <li>Go to step 1.</li>
1753:
1754: </ol><h5 id="the-element-pointers"><span class="secno">9.2.3.4 </span>The element pointers</h5>
1755:
1756: <p>Initially, the <dfn id="head-element-pointer"><code title="">head</code> element
1757: pointer</dfn> and the <dfn id="form-element-pointer"><code title="">form</code> element
1758: pointer</dfn> are both null.</p>
1759:
1.159 mike 1760: <p>Once a <code><a href="semantics.html#the-head-element-0">head</a></code> element has been parsed (whether
1.1 mike 1761: implicitly or explicitly) the <a href="#head-element-pointer"><code title="">head</code>
1762: element pointer</a> gets set to point to this node.</p>
1763:
1764: <p>The <a href="#form-element-pointer"><code title="">form</code> element pointer</a>
1765: points to the last <code><a href="forms.html#the-form-element">form</a></code> element that was opened and
1766: whose end tag has not yet been seen. It is used to make form
1767: controls associate with forms in the face of dramatically bad
1768: markup, for historical reasons.</p>
1769:
1770:
1771: <h5 id="other-parsing-state-flags"><span class="secno">9.2.3.5 </span>Other parsing state flags</h5>
1772:
1773: <p>The <dfn id="scripting-flag">scripting flag</dfn> is set to "enabled" if <a href="browsers.html#concept-n-script" title="concept-n-script">scripting was enabled</a> for the
1774: <code>Document</code> with which the parser is associated when the
1775: parser was created, and "disabled" otherwise.</p>
1776:
1777: <p class="note">The <a href="#scripting-flag">scripting flag</a> can be enabled even
1778: when the parser was originally created for the <a href="#html-fragment-parsing-algorithm">HTML fragment
1779: parsing algorithm</a>, even though <code><a href="semantics.html#script">script</a></code> elements
1780: don't execute in that case.</p>
1781:
1782: <p>The <dfn id="frameset-ok-flag">frameset-ok flag</dfn> is set to "ok" when the parser is
1783: created. It is set to "not ok" after certain tokens are seen.</p>
1784:
1785:
1.159 mike 1786: <h4 id="tokenization"><span class="secno">9.2.4 </span><dfn>Tokenization</dfn></h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
1.1 mike 1787:
1788: <p>Implementations must act as if they used the following state
1789: machine to tokenize HTML. The state machine must start in the
1790: <a href="#data-state">data state</a>. Most states consume a single character,
1791: which may have various side-effects, and either switches the state
1792: machine to a new state to <em>reconsume</em> the same character, or
1793: switches it to a new state (to consume the next character), or
1794: repeats the same state (to consume the next character). Some states
1795: have more complicated behavior and can consume several characters
1796: before switching to another state.</p>
1797:
1798: <p>The exact behavior of certain states depends on a <dfn id="content-model-flag">content
1799: model flag</dfn> that is set after certain tokens are emitted. The
1.91 mike 1800: flag has several states: <i title="">PCDATA</i>, <i title="">RCDATA</i>, <i title="">RAWTEXT</i>, and <i title="">PLAINTEXT</i>. Initially, it must be in the PCDATA
1801: state. In the RCDATA and RAWTEXT states, a further <dfn id="escape-flag">escape
1.1 mike 1802: flag</dfn> is used to control the behavior of the tokenizer. It is
1803: either true or false, and initially must be set to the false
1804: state. The <a href="#insertion-mode">insertion mode</a> and the <a href="#stack-of-open-elements">stack of open
1805: elements</a> also affects tokenization.</p>
1806:
1807: <p>The output of the tokenization step is a series of zero or more
1808: of the following tokens: DOCTYPE, start tag, end tag, comment,
1809: character, end-of-file. DOCTYPE tokens have a name, a public
1810: identifier, a system identifier, and a <i>force-quirks
1811: flag</i>. When a DOCTYPE token is created, its name, public
1812: identifier, and system identifier must be marked as missing (which
1813: is a distinct state from the empty string), and the <i>force-quirks
1814: flag</i> must be set to <i>off</i> (its other state is
1815: <i>on</i>). Start and end tag tokens have a tag name, a
1816: <i>self-closing flag</i>, and a list of attributes, each of which
1817: has a name and a value. When a start or end tag token is created,
1818: its <i>self-closing flag</i> must be unset (its other state is that
1819: it be set), and its attributes list must be empty. Comment and
1820: character tokens have data.</p>
1821:
1822: <p>When a token is emitted, it must immediately be handled by the
1823: <a href="#tree-construction">tree construction</a> stage. The tree construction stage
1824: can affect the state of the <a href="#content-model-flag">content model flag</a>, and can
1825: insert additional characters into the stream. (For example, the
1826: <code><a href="semantics.html#script">script</a></code> element can result in scripts executing and
1.159 mike 1827: using the <a href="embedded-content-0.html#dynamic-markup-insertion">dynamic markup insertion</a> APIs to insert
1.1 mike 1828: characters into the stream being tokenized.)</p>
1829:
1830: <p>When a start tag token is emitted with its <i>self-closing
1831: flag</i> set, if the flag is not <dfn id="acknowledge-self-closing-flag" title="acknowledge
1832: self-closing flag">acknowledged</dfn> when it is processed by the
1833: tree construction stage, that is a <a href="#parse-error">parse error</a>.</p>
1834:
1835: <p>When an end tag token is emitted, the <a href="#content-model-flag">content model
1836: flag</a> must be switched to the PCDATA state.</p>
1837:
1838: <p>When an end tag token is emitted with attributes, that is a
1839: <a href="#parse-error">parse error</a>.</p>
1840:
1841: <p>When an end tag token is emitted with its <i>self-closing
1842: flag</i> set, that is a <a href="#parse-error">parse error</a>.</p>
1843:
1844: <p>Before each step of the tokenizer, the user agent must first
1845: check the <a href="#parser-pause-flag">parser pause flag</a>. If it is true, then the
1846: tokenizer must abort the processing of any nested invocations of the
1847: tokenizer, yielding control back to the caller. If it is false, then
1848: the user agent may then check to see if either one of the scripts in
1849: the <a href="semantics.html#list-of-scripts-that-will-execute-as-soon-as-possible">list of scripts that will execute as soon as
1850: possible</a> or the first script in the <a href="semantics.html#list-of-scripts-that-will-execute-asynchronously">list of scripts
1851: that will execute asynchronously</a>, has <a href="semantics.html#completed-loading">completed
1852: loading</a>. If one has, then it must be <a href="semantics.html#executing-a-script-block" title="executing a
1853: script block">executed</a> and removed from its list.</p>
1854:
1855: <p>The tokenizer state machine consists of the states defined in the
1856: following subsections.</p>
1857:
1858: <!-- XXX should go through these reordering the entries so that
1859: they're in some consistent order, like, by Unicode, errors last, or
1860: something -->
1861:
1862: <h5 id="data-state"><span class="secno">9.2.4.1 </span><dfn>Data state</dfn></h5>
1863:
1864: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
1865:
1866: <dl class="switch"><dt>U+0026 AMPERSAND (&)</dt>
1867: <dd>When the <a href="#content-model-flag">content model flag</a> is set to one of the
1868: PCDATA or RCDATA states and the <a href="#escape-flag">escape flag</a> is
1869: false: switch to the <a href="#character-reference-data-state">character reference data
1.56 mike 1870: state</a>.</dd>
1871: <dd>Otherwise: treat it as per the "anything else" entry
1872: below.</dd>
1.1 mike 1873:
1874: <dt>U+002D HYPHEN-MINUS (-)</dt>
1875: <dd>
1876:
1877: <p>If the <a href="#content-model-flag">content model flag</a> is set to either the
1.91 mike 1878: RCDATA state or the RAWTEXT state, and the <a href="#escape-flag">escape flag</a>
1.1 mike 1879: is false, and there are at least three characters before this
1880: one in the input stream, and the last four characters in the
1881: input stream, including this one, are U+003C LESS-THAN SIGN,
1882: U+0021 EXCLAMATION MARK, U+002D HYPHEN-MINUS, and U+002D
1883: HYPHEN-MINUS ("<!--"), then set the <a href="#escape-flag">escape flag</a>
1884: to true.</p>
1885:
1886: <p>In any case, emit the input character as a character
1887: token. Stay in the <a href="#data-state">data state</a>.</p>
1888:
1889: </dd>
1890:
1891: <dt>U+003C LESS-THAN SIGN (<)</dt>
1892: <dd>When the <a href="#content-model-flag">content model flag</a> is set to the PCDATA
1893: state: switch to the <a href="#tag-open-state">tag open state</a>.</dd>
1894: <dd>When the <a href="#content-model-flag">content model flag</a> is set to either the
1.91 mike 1895: RCDATA state or the RAWTEXT state, and the <a href="#escape-flag">escape flag</a>
1.1 mike 1896: is false: switch to the <a href="#tag-open-state">tag open state</a>.</dd>
1897: <dd>Otherwise: treat it as per the "anything else" entry
1898: below.</dd>
1899:
1900: <dt>U+003E GREATER-THAN SIGN (>)</dt>
1901: <dd>
1902:
1903: <p>If the <a href="#content-model-flag">content model flag</a> is set to either the
1.91 mike 1904: RCDATA state or the RAWTEXT state, and the <a href="#escape-flag">escape
1.1 mike 1905: flag</a> is true, and the last three characters in the input
1906: stream including this one are U+002D HYPHEN-MINUS, U+002D
1907: HYPHEN-MINUS, U+003E GREATER-THAN SIGN ("-->"), set the
1908: <a href="#escape-flag">escape flag</a> to false.</p> <!-- no need to check
1909: that there are enough characters, since you can only run into
1910: this if the flag is true in the first place, which requires four
1911: characters. -->
1912:
1913: <p>In any case, emit the input character as a character
1914: token. Stay in the <a href="#data-state">data state</a>.</p>
1915:
1916: </dd>
1917:
1918: <dt>EOF</dt>
1919: <dd>Emit an end-of-file token.</dd>
1920:
1921: <dt>Anything else</dt>
1922: <dd>Emit the input character as a character token. Stay in the
1923: <a href="#data-state">data state</a>.</dd>
1924:
1925: </dl><h5 id="character-reference-data-state"><span class="secno">9.2.4.2 </span><dfn>Character reference data state</dfn></h5>
1926:
1927: <p><i>(This cannot happen if the <a href="#content-model-flag">content model flag</a>
1.91 mike 1928: is set to the RAWTEXT state.)</i></p>
1.1 mike 1929:
1930: <p>Attempt to <a href="#consume-a-character-reference">consume a character reference</a>, with no
1931: <a href="#additional-allowed-character">additional allowed character</a>.</p>
1932:
1933: <p>If nothing is returned, emit a U+0026 AMPERSAND character
1934: token.</p>
1935:
1936: <p>Otherwise, emit the character token that was returned.</p>
1937:
1938: <p>Finally, switch to the <a href="#data-state">data state</a>.</p>
1939:
1940:
1941: <h5 id="tag-open-state"><span class="secno">9.2.4.3 </span><dfn>Tag open state</dfn></h5>
1942:
1943: <p>The behavior of this state depends on the <a href="#content-model-flag">content model
1944: flag</a>.</p>
1945:
1946: <dl><dt>If the <a href="#content-model-flag">content model flag</a> is set to the RCDATA
1.91 mike 1947: or RAWTEXT states</dt>
1.1 mike 1948:
1949: <dd>
1950:
1951: <p>Consume the <a href="#next-input-character">next input character</a>. If it is a
1952: U+002F SOLIDUS (/) character, switch to the <a href="#close-tag-open-state">close tag open
1953: state</a>. Otherwise, emit a U+003C LESS-THAN SIGN character
1954: token and reconsume the <a href="#current-input-character">current input character</a> in the
1955: <a href="#data-state">data state</a>.</p>
1956:
1957: </dd>
1958:
1959: <dt>If the <a href="#content-model-flag">content model flag</a> is set to the PCDATA
1960: state</dt>
1961:
1962: <dd>
1963:
1964: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
1965:
1966: <dl class="switch"><dt>U+0021 EXCLAMATION MARK (!)</dt>
1967: <dd>Switch to the <a href="#markup-declaration-open-state">markup declaration open state</a>.</dd>
1968:
1969: <dt>U+002F SOLIDUS (/)</dt>
1970: <dd>Switch to the <a href="#close-tag-open-state">close tag open state</a>.</dd>
1971:
1972: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
1973: <dd>Create a new start tag token, set its tag name to the
1974: lowercase version of the input character (add 0x0020 to the
1975: character's code point), then switch to the <a href="#tag-name-state">tag name
1976: state</a>. (Don't emit the token yet; further details will
1977: be filled in before it is emitted.)</dd>
1978:
1979: <dt>U+0061 LATIN SMALL LETTER A through to U+007A LATIN SMALL LETTER Z</dt>
1980: <dd>Create a new start tag token, set its tag name to the input
1981: character, then switch to the <a href="#tag-name-state">tag name
1982: state</a>. (Don't emit the token yet; further details will
1983: be filled in before it is emitted.)</dd>
1984:
1985: <dt>U+003E GREATER-THAN SIGN (>)</dt>
1986: <dd><a href="#parse-error">Parse error</a>. Emit a U+003C LESS-THAN SIGN
1987: character token and a U+003E GREATER-THAN SIGN character
1988: token. Switch to the <a href="#data-state">data state</a>.</dd>
1989:
1990: <dt>U+003F QUESTION MARK (?)</dt>
1991: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#bogus-comment-state">bogus
1992: comment state</a>.</dd>
1993:
1994: <dt>Anything else</dt>
1995: <dd><a href="#parse-error">Parse error</a>. Emit a U+003C LESS-THAN SIGN
1996: character token and reconsume the <a href="#current-input-character">current input character</a> in the
1997: <a href="#data-state">data state</a>.</dd>
1998:
1999: </dl></dd>
2000:
2001: </dl><h5 id="close-tag-open-state"><span class="secno">9.2.4.4 </span><dfn>Close tag open state</dfn></h5>
2002:
2003: <p>If the <a href="#content-model-flag">content model flag</a> is set to the RCDATA or
1.91 mike 2004: RAWTEXT states but no start tag token has ever been emitted by this
1.1 mike 2005: instance of the tokenizer (<a href="#fragment-case">fragment case</a>), or, if the
1.91 mike 2006: <a href="#content-model-flag">content model flag</a> is set to the RCDATA or RAWTEXT states
1.1 mike 2007: and the next few characters do not match the tag name of the last
2008: start tag token emitted (compared in an <a href="infrastructure.html#ascii-case-insensitive">ASCII
2009: case-insensitive</a> manner), or if they do but they are not
2010: immediately followed by one of the following characters:</p>
2011:
2012: <ul class="brief"><li>U+0009 CHARACTER TABULATION</li>
2013: <li>U+000A LINE FEED (LF)</li>
2014: <li>U+000C FORM FEED (FF)</li>
2015: <!--<li>U+000D CARRIAGE RETURN (CR)</li>-->
2016: <li>U+0020 SPACE</li>
2017: <li>U+003E GREATER-THAN SIGN (>)</li>
2018: <li>U+002F SOLIDUS (/)</li>
2019: <li>EOF</li>
2020: </ul><p>...then emit a U+003C LESS-THAN SIGN character token, a U+002F
2021: SOLIDUS character token, and switch to the <a href="#data-state">data state</a>
2022: to process the <a href="#next-input-character">next input character</a>.</p>
2023:
2024: <p>Otherwise, if the <a href="#content-model-flag">content model flag</a> is set to the
2025: PCDATA state, or if the next few characters <em>do</em> match that tag
2026: name, consume the <a href="#next-input-character">next input character</a>:</p>
2027:
2028: <dl class="switch"><dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2029: <dd>Create a new end tag token, set its tag name to the lowercase
2030: version of the input character (add 0x0020 to the character's
2031: code point), then switch to the <a href="#tag-name-state">tag name
2032: state</a>. (Don't emit the token yet; further details will be
2033: filled in before it is emitted.)</dd>
2034:
2035: <dt>U+0061 LATIN SMALL LETTER A through to U+007A LATIN SMALL LETTER Z</dt>
2036: <dd>Create a new end tag token, set its tag name to the input
2037: character, then switch to the <a href="#tag-name-state">tag name state</a>. (Don't
2038: emit the token yet; further details will be filled in before it
2039: is emitted.)</dd>
2040:
2041: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2042: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#data-state">data
2043: state</a>.</dd>
2044:
2045: <dt>EOF</dt>
2046: <dd><a href="#parse-error">Parse error</a>. Emit a U+003C LESS-THAN SIGN
2047: character token and a U+002F SOLIDUS character token. Reconsume
2048: the EOF character in the <a href="#data-state">data state</a>.</dd>
2049:
2050: <dt>Anything else</dt>
2051: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#bogus-comment-state">bogus
2052: comment state</a>.</dd>
2053:
2054: </dl><h5 id="tag-name-state"><span class="secno">9.2.4.5 </span><dfn>Tag name state</dfn></h5>
2055:
2056: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2057:
2058: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2059: <dt>U+000A LINE FEED (LF)</dt>
2060: <dt>U+000C FORM FEED (FF)</dt>
2061: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2062: <dt>U+0020 SPACE</dt>
2063: <dd>Switch to the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2064:
2065: <dt>U+002F SOLIDUS (/)</dt>
2066: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2067:
2068: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2069: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2070: state</a>.</dd>
2071:
2072: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2073: <dd>Append the lowercase version of the <a href="#current-input-character">current input character</a>
2074: (add 0x0020 to the character's code point) to the current tag
2075: token's tag name. Stay in the <a href="#tag-name-state">tag name state</a>.</dd>
2076:
2077: <dt>EOF</dt>
2078: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2079: <a href="#data-state">data state</a>.</dd>
2080:
2081: <dt>Anything else</dt>
2082: <dd>Append the <a href="#current-input-character">current input character</a> to the current tag token's
2083: tag name. Stay in the <a href="#tag-name-state">tag name state</a>.</dd>
2084:
2085: </dl><h5 id="before-attribute-name-state"><span class="secno">9.2.4.6 </span><dfn>Before attribute name state</dfn></h5>
2086:
2087: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2088:
2089: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2090: <dt>U+000A LINE FEED (LF)</dt>
2091: <dt>U+000C FORM FEED (FF)</dt>
2092: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2093: <dt>U+0020 SPACE</dt>
2094: <dd>Stay in the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2095:
2096: <dt>U+002F SOLIDUS (/)</dt>
2097: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2098:
2099: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2100: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2101: state</a>.</dd>
2102:
2103: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2104: <dd>Start a new attribute in the current tag token. Set that
2105: attribute's name to the lowercase version of the <a href="#current-input-character">current input
2106: character</a> (add 0x0020 to the character's code point), and its
2107: value to the empty string. Switch to the <a href="#attribute-name-state">attribute name
2108: state</a>.</dd>
2109:
2110: <dt>U+0022 QUOTATION MARK (")</dt>
2111: <dt>U+0027 APOSTROPHE (')</dt>
2112: <dt>U+003C LESS-THAN SIGN (<)</dt>
2113: <dt>U+003D EQUALS SIGN (=)</dt>
2114: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2115: entry below.</dd>
2116:
2117: <dt>EOF</dt>
2118: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2119: <a href="#data-state">data state</a>.</dd>
2120:
2121: <dt>Anything else</dt>
2122: <dd>Start a new attribute in the current tag token. Set that
2123: attribute's name to the <a href="#current-input-character">current input character</a>, and its value to
2124: the empty string. Switch to the <a href="#attribute-name-state">attribute name
2125: state</a>.</dd>
2126:
2127: </dl><h5 id="attribute-name-state"><span class="secno">9.2.4.7 </span><dfn>Attribute name state</dfn></h5>
2128:
2129: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2130:
2131: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2132: <dt>U+000A LINE FEED (LF)</dt>
2133: <dt>U+000C FORM FEED (FF)</dt>
2134: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2135: <dt>U+0020 SPACE</dt>
2136: <dd>Switch to the <a href="#after-attribute-name-state">after attribute name state</a>.</dd>
2137:
2138: <dt>U+002F SOLIDUS (/)</dt>
2139: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2140:
2141: <dt>U+003D EQUALS SIGN (=)</dt>
2142: <dd>Switch to the <a href="#before-attribute-value-state">before attribute value state</a>.</dd>
2143:
2144: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2145: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2146: state</a>.</dd>
2147:
2148: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2149: <dd>Append the lowercase version of the <a href="#current-input-character">current input character</a>
2150: (add 0x0020 to the character's code point) to the current
2151: attribute's name. Stay in the <a href="#attribute-name-state">attribute name
2152: state</a>.</dd>
2153:
2154: <dt>U+0022 QUOTATION MARK (")</dt>
2155: <dt>U+0027 APOSTROPHE (')</dt>
2156: <dt>U+003C LESS-THAN SIGN (<)</dt>
2157: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2158: entry below.</dd>
2159:
2160: <dt>EOF</dt>
2161: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2162: <a href="#data-state">data state</a>.</dd>
2163:
2164: <dt>Anything else</dt>
2165: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2166: name. Stay in the <a href="#attribute-name-state">attribute name state</a>.</dd>
2167:
2168: </dl><p>When the user agent leaves the attribute name state (and before
2169: emitting the tag token, if appropriate), the complete attribute's
2170: name must be compared to the other attributes on the same token;
2171: if there is already an attribute on the token with the exact same
2172: name, then this is a <a href="#parse-error">parse error</a> and the new
2173: attribute must be dropped, along with the value that gets
2174: associated with it (if any).</p>
2175:
2176:
2177: <h5 id="after-attribute-name-state"><span class="secno">9.2.4.8 </span><dfn>After attribute name state</dfn></h5>
2178:
2179: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2180:
2181: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2182: <dt>U+000A LINE FEED (LF)</dt>
2183: <dt>U+000C FORM FEED (FF)</dt>
2184: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2185: <dt>U+0020 SPACE</dt>
2186: <dd>Stay in the <a href="#after-attribute-name-state">after attribute name state</a>.</dd>
2187:
2188: <dt>U+002F SOLIDUS (/)</dt>
2189: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2190:
2191: <dt>U+003D EQUALS SIGN (=)</dt>
2192: <dd>Switch to the <a href="#before-attribute-value-state">before attribute value state</a>.</dd>
2193:
2194: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2195: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2196: state</a>.</dd>
2197:
2198: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2199: <dd>Start a new attribute in the current tag token. Set that
2200: attribute's name to the lowercase version of the <a href="#current-input-character">current input character</a>
2201: (add 0x0020 to the character's code point), and its value to
2202: the empty string. Switch to the <a href="#attribute-name-state">attribute name
2203: state</a>.</dd>
2204:
2205: <dt>U+0022 QUOTATION MARK (")</dt>
2206: <dt>U+0027 APOSTROPHE (')</dt>
2207: <dt>U+003C LESS-THAN SIGN (<)</dt>
2208: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2209: entry below.</dd>
2210:
2211: <dt>EOF</dt>
2212: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2213: <a href="#data-state">data state</a>.</dd>
2214:
2215: <dt>Anything else</dt>
2216: <dd>Start a new attribute in the current tag token. Set that
2217: attribute's name to the <a href="#current-input-character">current input character</a>, and its value to
2218: the empty string. Switch to the <a href="#attribute-name-state">attribute name
2219: state</a>.</dd>
2220:
2221: </dl><h5 id="before-attribute-value-state"><span class="secno">9.2.4.9 </span><dfn>Before attribute value state</dfn></h5>
2222:
2223: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2224:
2225: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2226: <dt>U+000A LINE FEED (LF)</dt>
2227: <dt>U+000C FORM FEED (FF)</dt>
2228: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2229: <dt>U+0020 SPACE</dt>
2230: <dd>Stay in the <a href="#before-attribute-value-state">before attribute value state</a>.</dd>
2231:
2232: <dt>U+0022 QUOTATION MARK (")</dt>
2233: <dd>Switch to the <a href="#attribute-value-double-quoted-state">attribute value (double-quoted) state</a>.</dd>
2234:
2235: <dt>U+0026 AMPERSAND (&)</dt>
2236: <dd>Switch to the <a href="#attribute-value-unquoted-state">attribute value (unquoted) state</a>
2237: and reconsume this input character.</dd>
2238:
2239: <dt>U+0027 APOSTROPHE (')</dt>
2240: <dd>Switch to the <a href="#attribute-value-single-quoted-state">attribute value (single-quoted) state</a>.</dd>
2241:
2242: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2243: <dd><a href="#parse-error">Parse error</a>. Emit the current tag token. Switch to
2244: the <a href="#data-state">data state</a>.</dd>
2245:
2246: <dt>U+003C LESS-THAN SIGN (<)</dt>
2247: <dt>U+003D EQUALS SIGN (=)</dt>
2248: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2249: entry below.</dd>
2250:
2251: <dt>EOF</dt>
2252: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2253: <a href="#data-state">data state</a>.</dd>
2254:
2255: <dt>Anything else</dt>
2256: <dd>Append the <a href="#current-input-character">current input character</a> to the current
2257: attribute's value. Switch to the <a href="#attribute-value-unquoted-state">attribute value (unquoted)
2258: state</a>.</dd>
2259:
2260: </dl><h5 id="attribute-value-double-quoted-state"><span class="secno">9.2.4.10 </span><dfn>Attribute value (double-quoted) state</dfn></h5>
2261:
2262: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2263:
2264: <dl class="switch"><dt>U+0022 QUOTATION MARK (")</dt>
2265: <dd>Switch to the <a href="#after-attribute-value-quoted-state">after attribute value (quoted)
2266: state</a>.</dd>
2267:
2268: <dt>U+0026 AMPERSAND (&)</dt>
2269: <dd>Switch to the <a href="#character-reference-in-attribute-value-state">character reference in attribute value
2270: state</a>, with the <a href="#additional-allowed-character">additional allowed character</a>
2271: being U+0022 QUOTATION MARK (").</dd>
2272:
2273: <dt>EOF</dt>
2274: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2275: <a href="#data-state">data state</a>.</dd>
2276:
2277: <dt>Anything else</dt>
2278: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2279: value. Stay in the <a href="#attribute-value-double-quoted-state">attribute value (double-quoted)
2280: state</a>.</dd>
2281:
2282: </dl><h5 id="attribute-value-single-quoted-state"><span class="secno">9.2.4.11 </span><dfn>Attribute value (single-quoted) state</dfn></h5>
2283:
2284: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2285:
2286: <dl class="switch"><dt>U+0027 APOSTROPHE (')</dt>
2287: <dd>Switch to the <a href="#after-attribute-value-quoted-state">after attribute value (quoted)
2288: state</a>.</dd>
2289:
2290: <dt>U+0026 AMPERSAND (&)</dt>
2291: <dd>Switch to the <a href="#character-reference-in-attribute-value-state">character reference in attribute value
2292: state</a>, with the <a href="#additional-allowed-character">additional allowed character</a>
2293: being U+0027 APOSTROPHE (').</dd>
2294:
2295: <dt>EOF</dt>
2296: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2297: <a href="#data-state">data state</a>.</dd>
2298:
2299: <dt>Anything else</dt>
2300: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2301: value. Stay in the <a href="#attribute-value-single-quoted-state">attribute value (single-quoted)
2302: state</a>.</dd>
2303:
2304: </dl><h5 id="attribute-value-unquoted-state"><span class="secno">9.2.4.12 </span><dfn>Attribute value (unquoted) state</dfn></h5>
2305:
2306: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2307:
2308: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2309: <dt>U+000A LINE FEED (LF)</dt>
2310: <dt>U+000C FORM FEED (FF)</dt>
2311: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2312: <dt>U+0020 SPACE</dt>
2313: <dd>Switch to the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2314:
2315: <dt>U+0026 AMPERSAND (&)</dt>
2316: <dd>Switch to the <a href="#character-reference-in-attribute-value-state">character reference in attribute value
2317: state</a>, with no <a href="#additional-allowed-character">additional allowed
2318: character</a>.</dd>
2319:
2320: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2321: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2322: state</a>.</dd>
2323:
2324: <dt>U+0022 QUOTATION MARK (")</dt>
2325: <dt>U+0027 APOSTROPHE (')</dt>
2326: <dt>U+003C LESS-THAN SIGN (<)</dt>
2327: <dt>U+003D EQUALS SIGN (=)</dt>
2328: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2329: entry below.</dd>
2330:
2331: <dt>EOF</dt>
2332: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2333: <a href="#data-state">data state</a>.</dd>
2334:
2335: <dt>Anything else</dt>
2336: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2337: value. Stay in the <a href="#attribute-value-unquoted-state">attribute value (unquoted)
2338: state</a>.</dd>
2339:
2340: </dl><h5 id="character-reference-in-attribute-value-state"><span class="secno">9.2.4.13 </span><dfn>Character reference in attribute value state</dfn></h5>
2341:
2342: <p>Attempt to <a href="#consume-a-character-reference">consume a character reference</a>.</p>
2343:
2344: <p>If nothing is returned, append a U+0026 AMPERSAND character to
2345: the current attribute's value.</p>
2346:
2347: <p>Otherwise, append the returned character token to the current
2348: attribute's value.</p>
2349:
2350: <p>Finally, switch back to the attribute value state that you were
2351: in when were switched into this state.</p>
2352:
2353:
2354: <h5 id="after-attribute-value-quoted-state"><span class="secno">9.2.4.14 </span><dfn>After attribute value (quoted) state</dfn></h5>
2355:
2356: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2357:
2358: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2359: <dt>U+000A LINE FEED (LF)</dt>
2360: <dt>U+000C FORM FEED (FF)</dt>
2361: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2362: <dt>U+0020 SPACE</dt>
2363: <dd>Switch to the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2364:
2365: <dt>U+002F SOLIDUS (/)</dt>
2366: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2367:
2368: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2369: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2370: state</a>.</dd>
2371:
2372: <dt>EOF</dt>
2373: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2374: <a href="#data-state">data state</a>.</dd>
2375:
2376: <dt>Anything else</dt>
2377: <dd><a href="#parse-error">Parse error</a>. Reconsume the character in
2378: the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2379:
2380: </dl><h5 id="self-closing-start-tag-state"><span class="secno">9.2.4.15 </span><dfn>Self-closing start tag state</dfn></h5>
2381:
2382: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2383:
2384: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2385: <dd>Set the <i>self-closing flag</i> of the current tag
2386: token. Emit the current tag token. Switch to the <a href="#data-state">data
2387: state</a>.</dd>
2388:
2389: <dt>EOF</dt>
2390: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2391: <a href="#data-state">data state</a>.</dd>
2392:
2393: <dt>Anything else</dt>
2394: <dd><a href="#parse-error">Parse error</a>. Reconsume the character in
2395: the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2396:
2397: </dl><h5 id="bogus-comment-state"><span class="secno">9.2.4.16 </span><dfn>Bogus comment state</dfn></h5>
2398:
2399: <p><i>(This can only happen if the <a href="#content-model-flag">content model
2400: flag</a> is set to the PCDATA state.)</i></p>
2401:
2402: <p>Consume every character up to and including the first U+003E
2403: GREATER-THAN SIGN character (>) or the end of the file (EOF),
2404: whichever comes first. Emit a comment token whose data is the
2405: concatenation of all the characters starting from and including
2406: the character that caused the state machine to switch into the
2407: bogus comment state, up to and including the character immediately
2408: before the last consumed character (i.e. up to the character just
2409: before the U+003E or EOF character). (If the comment was started
2410: by the end of the file (EOF), the token is empty.)</p>
2411:
2412: <p>Switch to the <a href="#data-state">data state</a>.</p>
2413:
2414: <p>If the end of the file was reached, reconsume the EOF
2415: character.</p>
2416:
2417:
2418: <h5 id="markup-declaration-open-state"><span class="secno">9.2.4.17 </span><dfn>Markup declaration open state</dfn></h5>
2419:
2420: <p><i>(This can only happen if the <a href="#content-model-flag">content model
2421: flag</a> is set to the PCDATA state.)</i></p>
2422:
2423: <p>If the next two characters are both U+002D HYPHEN-MINUS (-)
2424: characters, consume those two characters, create a comment token
2425: whose data is the empty string, and switch to the <a href="#comment-start-state">comment
2426: start state</a>.</p>
2427:
2428: <p>Otherwise, if the next seven characters are an <a href="infrastructure.html#ascii-case-insensitive">ASCII
2429: case-insensitive</a> match for the word "DOCTYPE", then consume
2430: those characters and switch to the <a href="#doctype-state">DOCTYPE state</a>.</p>
2431:
2432: <p>Otherwise, if the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in foreign
2433: content</a>" and the <a href="#current-node">current node</a> is not an element
2434: in the <a href="#html-namespace-0">HTML namespace</a> and the next seven characters are
2435: an <span>ASCII case-sensitive</span> match for the string "[CDATA["
2436: (the five uppercase letters "CDATA" with a U+005B LEFT SQUARE
2437: BRACKET character before and after), then consume those characters
1.91 mike 2438: and switch to the <a href="#cdata-section-state">CDATA section state</a>.</p>
1.1 mike 2439:
2440: <p>Otherwise, this is a <a href="#parse-error">parse error</a>. Switch to the
2441: <a href="#bogus-comment-state">bogus comment state</a>. The next character that is
2442: consumed, if any, is the first character that will be in the
2443: comment.</p>
2444:
2445:
2446: <h5 id="comment-start-state"><span class="secno">9.2.4.18 </span><dfn>Comment start state</dfn></h5>
2447:
2448: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2449:
2450: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2451: <dd>Switch to the <a href="#comment-start-dash-state">comment start dash state</a>.</dd>
2452:
2453: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2454: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Switch to the
2455: <a href="#data-state">data state</a>.</dd> <!-- see comment in comment end state
2456: -->
2457:
2458: <dt>EOF</dt>
2459: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2460: the EOF character in the <a href="#data-state">data state</a>.</dd>
2461:
2462: <dt>Anything else</dt>
2463: <dd>Append the input character to the comment token's
2464: data. Switch to the <a href="#comment-state">comment state</a>.</dd>
2465:
2466: </dl><h5 id="comment-start-dash-state"><span class="secno">9.2.4.19 </span><dfn>Comment start dash state</dfn></h5>
2467:
2468: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2469:
2470: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2471: <dd>Switch to the <a href="#comment-end-state">comment end state</a></dd>
2472:
2473: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2474: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Switch to
2475: the <a href="#data-state">data state</a>.</dd>
2476:
2477: <dt>EOF</dt>
2478: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume the
2479: EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see comment
2480: in comment end state -->
2481:
2482: <dt>Anything else</dt>
2483: <dd>Append a U+002D HYPHEN-MINUS (-) character and the input
2484: character to the comment token's data. Switch to the
2485: <a href="#comment-state">comment state</a>.</dd>
2486:
2487: </dl><h5 id="comment-state"><span class="secno">9.2.4.20 </span><dfn id="comment">Comment state</dfn></h5>
2488:
2489: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2490:
2491: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2492: <dd>Switch to the <a href="#comment-end-dash-state">comment end dash state</a></dd>
2493:
2494: <dt>EOF</dt>
2495: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume the
2496: EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see comment
2497: in comment end state -->
2498:
2499: <dt>Anything else</dt>
2500: <dd>Append the input character to the comment token's data. Stay
2501: in the <a href="#comment-state">comment state</a>.</dd>
2502:
2503: </dl><h5 id="comment-end-dash-state"><span class="secno">9.2.4.21 </span><dfn>Comment end dash state</dfn></h5>
2504:
2505: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2506:
2507: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2508: <dd>Switch to the <a href="#comment-end-state">comment end state</a></dd>
2509:
2510: <dt>EOF</dt>
2511: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume the
2512: EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see comment
2513: in comment end state -->
2514:
2515: <dt>Anything else</dt>
2516: <dd>Append a U+002D HYPHEN-MINUS (-) character and the input
2517: character to the comment token's data. Switch to the
2518: <a href="#comment-state">comment state</a>.</dd>
2519:
2520: </dl><h5 id="comment-end-state"><span class="secno">9.2.4.22 </span><dfn>Comment end state</dfn></h5>
2521:
2522: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2523:
2524: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2525: <dd>Emit the comment token. Switch to the <a href="#data-state">data
2526: state</a>.</dd>
2527:
2528: <dt>U+002D HYPHEN-MINUS (-)</dt>
2529: <dd><a href="#parse-error">Parse error</a>. Append a U+002D HYPHEN-MINUS
2530: (-) character to the comment token's data. Stay in the
2531: <a href="#comment-end-state">comment end state</a>.</dd>
2532:
2533: <dt>U+0009 CHARACTER TABULATION</dt>
2534: <dt>U+000A LINE FEED (LF)</dt>
2535: <dt>U+000C FORM FEED (FF)</dt>
2536: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2537: <dt>U+0020 SPACE</dt>
2538: <dd><a href="#parse-error">Parse error</a>. Append two U+002D HYPHEN-MINUS (-)
2539: characters and the input character to the comment token's
2540: data. Switch to the <a href="#comment-end-space-state">comment end space state</a>.</dd>
2541:
2542: <dt>U+0021 EXCLAMATION MARK (!)</dt>
2543: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#comment-end-bang-state">comment end bang
2544: state</a>.</dd>
2545:
2546: <dt>EOF</dt>
2547: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2548: the EOF character in the <a href="#data-state">data state</a>.</dd> <!-- For
2549: security reasons: otherwise, hostile user could put a <script> in
2550: a comment e.g. in a blog comment and then DOS the server so that
2551: the end tag isn't read, and then the commented <script> tag would
2552: be treated as live code -->
2553:
2554: <dt>Anything else</dt>
2555: <dd><a href="#parse-error">Parse error</a>. Append two U+002D HYPHEN-MINUS (-)
2556: characters and the input character to the comment token's
2557: data. Switch to the <a href="#comment-state">comment state</a>.</dd>
2558:
2559: </dl><h5 id="comment-end-bang-state"><span class="secno">9.2.4.23 </span><dfn>Comment end bang state</dfn></h5>
2560:
2561: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2562:
2563: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2564: <dd>Emit the comment token. Switch to the <a href="#data-state">data
2565: state</a>.</dd>
2566:
2567: <dt>U+002D HYPHEN-MINUS (-)</dt>
2568: <dd>Append two U+002D HYPHEN-MINUS (-) characters and a U+0021
2569: EXCLAMATION MARK (!) character to the comment token's data. Switch
2570: to the <a href="#comment-end-dash-state">comment end dash state</a>.</dd>
2571:
2572: <dt>EOF</dt>
2573: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2574: the EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see
2575: comment in comment end state -->
2576:
2577: <dt>Anything else</dt>
2578: <dd>Append two U+002D HYPHEN-MINUS (-) characters, a U+0021
2579: EXCLAMATION MARK (!) character, and the input character to the
2580: comment token's data. Switch to the <a href="#comment-state">comment
2581: state</a>.</dd>
2582:
2583: </dl><h5 id="comment-end-space-state"><span class="secno">9.2.4.24 </span><dfn>Comment end space state</dfn></h5>
2584:
2585: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2586:
2587: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2588: <dd>Emit the comment token. Switch to the <a href="#data-state">data
2589: state</a>.</dd>
2590:
2591: <dt>U+002D HYPHEN-MINUS (-)</dt>
2592: <dd>Switch to the <a href="#comment-end-dash-state">comment end dash state</a>.</dd>
2593:
2594: <dt>U+0009 CHARACTER TABULATION</dt>
2595: <dt>U+000A LINE FEED (LF)</dt>
2596: <dt>U+000C FORM FEED (FF)</dt>
2597: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2598: <dt>U+0020 SPACE</dt>
2599: <dd>Append the input character to the comment token's data. Stay in
2600: the <a href="#comment-end-space-state">comment end space state</a>.</dd>
2601:
2602: <dt>EOF</dt>
2603: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2604: the EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see
2605: comment in comment end state -->
2606:
2607: <dt>Anything else</dt>
2608: <dd>Append the input character to the comment token's data. Switch
2609: to the <a href="#comment-state">comment state</a>.</dd>
2610:
2611: </dl><h5 id="doctype-state"><span class="secno">9.2.4.25 </span><dfn>DOCTYPE state</dfn></h5>
2612:
2613: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2614:
2615: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2616: <dt>U+000A LINE FEED (LF)</dt>
2617: <dt>U+000C FORM FEED (FF)</dt>
2618: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2619: <dt>U+0020 SPACE</dt>
2620: <dd>Switch to the <a href="#before-doctype-name-state">before DOCTYPE name state</a>.</dd>
2621:
2622: <dt>EOF</dt>
2623: <dd><a href="#parse-error">Parse error</a>. Create a new DOCTYPE token. Set its
2624: <i>force-quirks flag</i> to <i>on</i>. Emit the token. Reconsume
2625: the EOF character in the <a href="#data-state">data state</a>.</dd>
2626:
2627: <dt>Anything else</dt>
2628: <dd><a href="#parse-error">Parse error</a>. Reconsume the current
2629: character in the <a href="#before-doctype-name-state">before DOCTYPE name state</a>.</dd>
2630:
2631: </dl><h5 id="before-doctype-name-state"><span class="secno">9.2.4.26 </span><dfn>Before DOCTYPE name state</dfn></h5>
2632:
2633: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2634:
2635: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2636: <dt>U+000A LINE FEED (LF)</dt>
2637: <dt>U+000C FORM FEED (FF)</dt>
2638: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2639: <dt>U+0020 SPACE</dt>
2640: <dd>Stay in the <a href="#before-doctype-name-state">before DOCTYPE name state</a>.</dd>
2641:
2642: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2643: <dd><a href="#parse-error">Parse error</a>. Create a new DOCTYPE token. Set its
2644: <i>force-quirks flag</i> to <i>on</i>. Emit the token. Switch to
2645: the <a href="#data-state">data state</a>.</dd>
2646:
2647: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2648: <dd>Create a new DOCTYPE token. Set the token's name to the
2649: lowercase version of the input character (add 0x0020 to the
2650: character's code point). Switch to the <a href="#doctype-name-state">DOCTYPE name
2651: state</a>.</dd>
2652:
2653: <dt>EOF</dt>
2654: <dd><a href="#parse-error">Parse error</a>. Create a new DOCTYPE token. Set its
2655: <i>force-quirks flag</i> to <i>on</i>. Emit the token. Reconsume
2656: the EOF character in the <a href="#data-state">data state</a>.</dd>
2657:
2658: <dt>Anything else</dt>
2659: <dd>Create a new DOCTYPE token. Set the token's name to the
2660: <a href="#current-input-character">current input character</a>. Switch to the <a href="#doctype-name-state">DOCTYPE name
2661: state</a>.</dd>
2662:
2663: </dl><h5 id="doctype-name-state"><span class="secno">9.2.4.27 </span><dfn>DOCTYPE name state</dfn></h5>
2664:
2665: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2666:
2667: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2668: <dt>U+000A LINE FEED (LF)</dt>
2669: <dt>U+000C FORM FEED (FF)</dt>
2670: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2671: <dt>U+0020 SPACE</dt>
2672: <dd>Switch to the <a href="#after-doctype-name-state">after DOCTYPE name state</a>.</dd>
2673:
2674: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2675: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2676: state</a>.</dd>
2677:
2678: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2679: <dd>Append the lowercase version of the input character (add 0x0020
2680: to the character's code point) to the current DOCTYPE token's
2681: name. Stay in the <a href="#doctype-name-state">DOCTYPE name state</a>.</dd>
2682:
2683: <dt>EOF</dt>
2684: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2685: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2686: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2687:
2688: <dt>Anything else</dt>
2689: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2690: token's name. Stay in the <a href="#doctype-name-state">DOCTYPE name state</a>.</dd>
2691:
2692: </dl><h5 id="after-doctype-name-state"><span class="secno">9.2.4.28 </span><dfn>After DOCTYPE name state</dfn></h5>
2693:
2694: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2695:
2696: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2697: <dt>U+000A LINE FEED (LF)</dt>
2698: <dt>U+000C FORM FEED (FF)</dt>
2699: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2700: <dt>U+0020 SPACE</dt>
2701: <dd>Stay in the <a href="#after-doctype-name-state">after DOCTYPE name state</a>.</dd>
2702:
2703: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2704: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2705: state</a>.</dd>
2706:
2707: <dt>EOF</dt>
2708: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2709: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2710: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2711:
2712: <dt>Anything else</dt>
2713: <dd>
2714:
2715: <p>If the six characters starting from the <a href="#current-input-character">current input
2716: character</a> are an <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> match
2717: for the word "PUBLIC", then consume those characters and switch to
2718: the <a href="#before-doctype-public-identifier-state">before DOCTYPE public identifier state</a>.</p>
2719:
2720: <p>Otherwise, if the six characters starting from the
2721: <a href="#current-input-character">current input character</a> are an <a href="infrastructure.html#ascii-case-insensitive">ASCII
2722: case-insensitive</a> match for the word "SYSTEM", then consume
2723: those characters and switch to the <a href="#before-doctype-system-identifier-state">before DOCTYPE system
2724: identifier state</a>.</p>
2725:
2726: <p>Otherwise, this is the <a href="#parse-error">parse error</a>. Set the
2727: DOCTYPE token's <i>force-quirks flag</i> to <i>on</i>. Switch to
2728: the <a href="#bogus-doctype-state">bogus DOCTYPE state</a>.</p>
2729:
2730: </dd>
2731:
2732: </dl><h5 id="before-doctype-public-identifier-state"><span class="secno">9.2.4.29 </span><dfn>Before DOCTYPE public identifier state</dfn></h5>
2733:
2734: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2735:
2736: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2737: <dt>U+000A LINE FEED (LF)</dt>
2738: <dt>U+000C FORM FEED (FF)</dt>
2739: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2740: <dt>U+0020 SPACE</dt>
2741: <dd>Stay in the <a href="#before-doctype-public-identifier-state">before DOCTYPE public identifier state</a>.</dd>
2742:
2743: <dt>U+0022 QUOTATION MARK (")</dt>
2744: <dd>Set the DOCTYPE token's public identifier to the empty string
2745: (not missing), then switch to the <a href="#doctype-public-identifier-double-quoted-state">DOCTYPE public identifier
2746: (double-quoted) state</a>.</dd>
2747:
2748: <dt>U+0027 APOSTROPHE (')</dt>
2749: <dd>Set the DOCTYPE token's public identifier to the empty string
2750: (not missing), then switch to the <a href="#doctype-public-identifier-single-quoted-state">DOCTYPE public identifier
2751: (single-quoted) state</a>.</dd>
2752:
2753: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2754: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2755: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2756: token. Switch to the <a href="#data-state">data state</a>.</dd>
2757:
2758: <dt>EOF</dt>
2759: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2760: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2761: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2762:
2763: <dt>Anything else</dt>
2764: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2765: <i>force-quirks flag</i> to <i>on</i>. Switch to the <a href="#bogus-doctype-state">bogus
2766: DOCTYPE state</a>.</dd>
2767:
2768: </dl><h5 id="doctype-public-identifier-double-quoted-state"><span class="secno">9.2.4.30 </span><dfn>DOCTYPE public identifier (double-quoted) state</dfn></h5>
2769:
2770: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2771:
2772: <dl class="switch"><dt>U+0022 QUOTATION MARK (")</dt>
2773: <dd>Switch to the <a href="#after-doctype-public-identifier-state">after DOCTYPE public identifier state</a>.</dd>
2774:
2775: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2776: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2777: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2778: token. Switch to the <a href="#data-state">data state</a>.</dd>
2779:
2780: <dt>EOF</dt>
2781: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2782: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2783: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2784:
2785: <dt>Anything else</dt>
2786: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2787: token's public identifier. Stay in the <a href="#doctype-public-identifier-double-quoted-state">DOCTYPE public
2788: identifier (double-quoted) state</a>.</dd>
2789:
2790: </dl><h5 id="doctype-public-identifier-single-quoted-state"><span class="secno">9.2.4.31 </span><dfn>DOCTYPE public identifier (single-quoted) state</dfn></h5>
2791:
2792: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2793:
2794: <dl class="switch"><dt>U+0027 APOSTROPHE (')</dt>
2795: <dd>Switch to the <a href="#after-doctype-public-identifier-state">after DOCTYPE public identifier state</a>.</dd>
2796:
2797: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2798: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2799: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2800: token. Switch to the <a href="#data-state">data state</a>.</dd>
2801:
2802: <dt>EOF</dt>
2803: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2804: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2805: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2806:
2807: <dt>Anything else</dt>
2808: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2809: token's public identifier. Stay in the <a href="#doctype-public-identifier-single-quoted-state">DOCTYPE public
2810: identifier (single-quoted) state</a>.</dd>
2811:
2812: </dl><h5 id="after-doctype-public-identifier-state"><span class="secno">9.2.4.32 </span><dfn>After DOCTYPE public identifier state</dfn></h5>
2813:
2814: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2815:
2816: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2817: <dt>U+000A LINE FEED (LF)</dt>
2818: <dt>U+000C FORM FEED (FF)</dt>
2819: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2820: <dt>U+0020 SPACE</dt>
2821: <dd>Stay in the <a href="#after-doctype-public-identifier-state">after DOCTYPE public identifier state</a>.</dd>
2822:
2823: <dt>U+0022 QUOTATION MARK (")</dt>
2824: <dd>Set the DOCTYPE token's system identifier to the empty string
2825: (not missing), then switch to the <a href="#doctype-system-identifier-double-quoted-state">DOCTYPE system identifier
2826: (double-quoted) state</a>.</dd>
2827:
2828: <dt>U+0027 APOSTROPHE (')</dt>
2829: <dd>Set the DOCTYPE token's system identifier to the empty string
2830: (not missing), then switch to the <a href="#doctype-system-identifier-single-quoted-state">DOCTYPE system identifier
2831: (single-quoted) state</a>.</dd>
2832:
2833: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2834: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2835: state</a>.</dd>
2836:
2837: <dt>EOF</dt>
2838: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2839: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2840: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2841:
2842: <dt>Anything else</dt>
2843: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2844: <i>force-quirks flag</i> to <i>on</i>. Switch to the <a href="#bogus-doctype-state">bogus
2845: DOCTYPE state</a>.</dd>
2846:
2847: </dl><h5 id="before-doctype-system-identifier-state"><span class="secno">9.2.4.33 </span><dfn>Before DOCTYPE system identifier state</dfn></h5>
2848:
2849: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2850:
2851: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2852: <dt>U+000A LINE FEED (LF)</dt>
2853: <dt>U+000C FORM FEED (FF)</dt>
2854: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2855: <dt>U+0020 SPACE</dt>
2856: <dd>Stay in the <a href="#before-doctype-system-identifier-state">before DOCTYPE system identifier state</a>.</dd>
2857:
2858: <dt>U+0022 QUOTATION MARK (")</dt>
2859: <dd>Set the DOCTYPE token's system identifier to the empty string
2860: (not missing), then switch to the <a href="#doctype-system-identifier-double-quoted-state">DOCTYPE system identifier
2861: (double-quoted) state</a>.</dd>
2862:
2863: <dt>U+0027 APOSTROPHE (')</dt>
2864: <dd>Set the DOCTYPE token's system identifier to the empty string
2865: (not missing), then switch to the <a href="#doctype-system-identifier-single-quoted-state">DOCTYPE system identifier
2866: (single-quoted) state</a>.</dd>
2867:
2868: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2869: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2870: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2871: token. Switch to the <a href="#data-state">data state</a>.</dd>
2872:
2873: <dt>EOF</dt>
2874: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2875: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2876: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2877:
2878: <dt>Anything else</dt>
2879: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2880: <i>force-quirks flag</i> to <i>on</i>. Switch to the <a href="#bogus-doctype-state">bogus
2881: DOCTYPE state</a>.</dd>
2882:
2883: </dl><h5 id="doctype-system-identifier-double-quoted-state"><span class="secno">9.2.4.34 </span><dfn>DOCTYPE system identifier (double-quoted) state</dfn></h5>
2884:
2885: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2886:
2887: <dl class="switch"><dt>U+0022 QUOTATION MARK (")</dt>
2888: <dd>Switch to the <a href="#after-doctype-system-identifier-state">after DOCTYPE system identifier state</a>.</dd>
2889:
2890: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2891: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2892: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2893: token. Switch to the <a href="#data-state">data state</a>.</dd>
2894:
2895: <dt>EOF</dt>
2896: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2897: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2898: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2899:
2900: <dt>Anything else</dt>
2901: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2902: token's system identifier. Stay in the <a href="#doctype-system-identifier-double-quoted-state">DOCTYPE system
2903: identifier (double-quoted) state</a>.</dd>
2904:
2905: </dl><h5 id="doctype-system-identifier-single-quoted-state"><span class="secno">9.2.4.35 </span><dfn>DOCTYPE system identifier (single-quoted) state</dfn></h5>
2906:
2907: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2908:
2909: <dl class="switch"><dt>U+0027 APOSTROPHE (')</dt>
2910: <dd>Switch to the <a href="#after-doctype-system-identifier-state">after DOCTYPE system identifier state</a>.</dd>
2911:
2912: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2913: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2914: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2915: token. Switch to the <a href="#data-state">data state</a>.</dd>
2916:
2917: <dt>EOF</dt>
2918: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2919: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2920: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2921:
2922: <dt>Anything else</dt>
2923: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2924: token's system identifier. Stay in the <a href="#doctype-system-identifier-single-quoted-state">DOCTYPE system
2925: identifier (single-quoted) state</a>.</dd>
2926:
2927: </dl><h5 id="after-doctype-system-identifier-state"><span class="secno">9.2.4.36 </span><dfn>After DOCTYPE system identifier state</dfn></h5>
2928:
2929: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2930:
2931: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2932: <dt>U+000A LINE FEED (LF)</dt>
2933: <dt>U+000C FORM FEED (FF)</dt>
2934: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2935: <dt>U+0020 SPACE</dt>
2936: <dd>Stay in the <a href="#after-doctype-system-identifier-state">after DOCTYPE system identifier state</a>.</dd>
2937:
2938: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2939: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2940: state</a>.</dd>
2941:
2942: <dt>EOF</dt>
2943: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2944: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2945: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2946:
2947: <dt>Anything else</dt>
2948: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#bogus-doctype-state">bogus DOCTYPE
2949: state</a>. (This does <em>not</em> set the DOCTYPE token's
2950: <i>force-quirks flag</i> to <i>on</i>.)</dd>
2951:
2952: </dl><h5 id="bogus-doctype-state"><span class="secno">9.2.4.37 </span><dfn>Bogus DOCTYPE state</dfn></h5>
2953:
2954: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2955:
2956: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2957: <dd>Emit the DOCTYPE token. Switch to the <a href="#data-state">data
2958: state</a>.</dd>
2959:
2960: <dt>EOF</dt>
2961: <dd>Emit the DOCTYPE token. Reconsume the EOF character in the
2962: <a href="#data-state">data state</a>.</dd>
2963:
2964: <dt>Anything else</dt>
2965: <dd>Stay in the <a href="#bogus-doctype-state">bogus DOCTYPE state</a>.</dd>
2966:
2967: </dl><h5 id="cdata-section-state"><span class="secno">9.2.4.38 </span><dfn>CDATA section state</dfn></h5>
2968:
2969: <p><i>(This can only happen if the <a href="#content-model-flag">content model
1.91 mike 2970: flag</a> is set to the PCDATA state.)</i></p>
1.1 mike 2971:
2972: <p>Consume every character up to the next occurrence of the three
2973: character sequence U+005D RIGHT SQUARE BRACKET U+005D RIGHT SQUARE
2974: BRACKET U+003E GREATER-THAN SIGN (<code title="">]]></code>), or the
2975: end of the file (EOF), whichever comes first. Emit a series of
2976: character tokens consisting of all the characters consumed except
2977: the matching three character sequence at the end (if one was found
2978: before the end of the file).</p>
2979:
2980: <p>Switch to the <a href="#data-state">data state</a>.</p>
2981:
2982: <p>If the end of the file was reached, reconsume the EOF
2983: character.</p>
2984:
2985:
2986:
2987: <h5 id="tokenizing-character-references"><span class="secno">9.2.4.39 </span>Tokenizing character references</h5>
2988:
2989: <p>This section defines how to <dfn id="consume-a-character-reference">consume a character
2990: reference</dfn>. This definition is used when parsing character
2991: references <a href="#character-reference-data-state" title="character reference data state">in
2992: text</a> and <a href="#character-reference-in-attribute-value-state" title="character reference in attribute value
2993: state">in attributes</a>.</p>
2994:
2995: <p>The behavior depends on the identity of the next character (the
2996: one immediately after the U+0026 AMPERSAND character):</p>
2997:
2998: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2999: <dt>U+000A LINE FEED (LF)</dt>
3000: <dt>U+000C FORM FEED (FF)</dt>
3001: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
3002: <dt>U+0020 SPACE</dt>
3003: <dt>U+003C LESS-THAN SIGN</dt>
3004: <dt>U+0026 AMPERSAND</dt>
3005: <dt>EOF</dt>
3006: <dt>The <dfn id="additional-allowed-character">additional allowed character</dfn>, if there is one</dt>
3007:
3008: <dd>Not a character reference. No characters are consumed, and
3009: nothing is returned. (This is not an error, either.)</dd>
3010:
3011:
3012: <dt>U+0023 NUMBER SIGN (#)</dt>
3013:
3014: <dd>
3015:
3016: <p>Consume the U+0023 NUMBER SIGN.</p>
3017:
3018: <p>The behavior further depends on the character after the U+0023
3019: NUMBER SIGN:</p>
3020:
3021: <dl class="switch"><dt>U+0078 LATIN SMALL LETTER X</dt>
3022: <dt>U+0058 LATIN CAPITAL LETTER X</dt>
3023:
3024: <dd>
3025:
3026: <p>Consume the X.</p>
3027:
3028: <p>Follow the steps below, but using the range of characters
3029: U+0030 DIGIT ZERO through to U+0039 DIGIT NINE, U+0061 LATIN
3030: SMALL LETTER A through to U+0066 LATIN SMALL LETTER F, and
3031: U+0041 LATIN CAPITAL LETTER A, through to U+0046 LATIN CAPITAL
3032: LETTER F (in other words, 0-9, A-F, a-f).</p>
3033:
3034: <p>When it comes to interpreting the number, interpret it as a
3035: hexadecimal number.</p>
3036:
3037: </dd>
3038:
3039:
3040: <dt>Anything else</dt>
3041:
3042: <dd>
3043:
3044: <p>Follow the steps below, but using the range of characters
3045: U+0030 DIGIT ZERO through to U+0039 DIGIT NINE (i.e. just
3046: 0-9).</p>
3047:
3048: <p>When it comes to interpreting the number, interpret it as a
3049: decimal number.</p>
3050:
3051: </dd>
3052:
3053: </dl><p>Consume as many characters as match the range of characters
3054: given above.</p>
3055:
3056: <p>If no characters match the range, then don't consume any
3057: characters (and unconsume the U+0023 NUMBER SIGN character and, if
3058: appropriate, the X character). This is a <a href="#parse-error">parse
3059: error</a>; nothing is returned.</p>
3060:
3061: <p>Otherwise, if the next character is a U+003B SEMICOLON, consume
3062: that too. If it isn't, there is a <a href="#parse-error">parse
3063: error</a>.</p>
3064:
3065: <p>If one or more characters match the range, then take them all
3066: and interpret the string of characters as a number (either
3067: hexadecimal or decimal as appropriate).</p>
3068:
3069: <p>If that number is one of the numbers in the first column of the
3070: following table, then this is a <a href="#parse-error">parse error</a>. Find the
3071: row with that number in the first column, and return a character
3072: token for the Unicode character given in the second column of that
3073: row.</p>
3074:
3075: <table><thead><tr><th>Number </th><th colspan="2">Unicode character
3076: </th></tr></thead><tbody><tr><td>0x00 </td><td>U+FFFD </td><td>REPLACEMENT CHARACTER
3077: </td></tr><tr><td>0x0D </td><td>U+000A </td><td>LINE FEED (LF)
3078: </td></tr><tr><td>0x80 </td><td>U+20AC </td><td>EURO SIGN ('€')
3079: </td></tr><tr><td>0x81 </td><td>U+0081 </td><td><control>
3080: </td></tr><tr><td>0x82 </td><td>U+201A </td><td>SINGLE LOW-9 QUOTATION MARK ('‚')
3081: </td></tr><tr><td>0x83 </td><td>U+0192 </td><td>LATIN SMALL LETTER F WITH HOOK ('ƒ')
3082: </td></tr><tr><td>0x84 </td><td>U+201E </td><td>DOUBLE LOW-9 QUOTATION MARK ('„')
3083: </td></tr><tr><td>0x85 </td><td>U+2026 </td><td>HORIZONTAL ELLIPSIS ('…')
3084: </td></tr><tr><td>0x86 </td><td>U+2020 </td><td>DAGGER ('†')
3085: </td></tr><tr><td>0x87 </td><td>U+2021 </td><td>DOUBLE DAGGER ('‡')
3086: </td></tr><tr><td>0x88 </td><td>U+02C6 </td><td>MODIFIER LETTER CIRCUMFLEX ACCENT ('ˆ')
3087: </td></tr><tr><td>0x89 </td><td>U+2030 </td><td>PER MILLE SIGN ('‰')
3088: </td></tr><tr><td>0x8A </td><td>U+0160 </td><td>LATIN CAPITAL LETTER S WITH CARON ('Š')
3089: </td></tr><tr><td>0x8B </td><td>U+2039 </td><td>SINGLE LEFT-POINTING ANGLE QUOTATION MARK ('‹')
3090: </td></tr><tr><td>0x8C </td><td>U+0152 </td><td>LATIN CAPITAL LIGATURE OE ('Œ')
3091: </td></tr><tr><td>0x8D </td><td>U+008D </td><td><control>
3092: </td></tr><tr><td>0x8E </td><td>U+017D </td><td>LATIN CAPITAL LETTER Z WITH CARON ('Ž')
3093: </td></tr><tr><td>0x8F </td><td>U+008F </td><td><control>
3094: </td></tr><tr><td>0x90 </td><td>U+0090 </td><td><control>
3095: </td></tr><tr><td>0x91 </td><td>U+2018 </td><td>LEFT SINGLE QUOTATION MARK ('‘')
3096: </td></tr><tr><td>0x92 </td><td>U+2019 </td><td>RIGHT SINGLE QUOTATION MARK ('’')
3097: </td></tr><tr><td>0x93 </td><td>U+201C </td><td>LEFT DOUBLE QUOTATION MARK ('“')
3098: </td></tr><tr><td>0x94 </td><td>U+201D </td><td>RIGHT DOUBLE QUOTATION MARK ('”')
3099: </td></tr><tr><td>0x95 </td><td>U+2022 </td><td>BULLET ('•')
3100: </td></tr><tr><td>0x96 </td><td>U+2013 </td><td>EN DASH ('–')
3101: </td></tr><tr><td>0x97 </td><td>U+2014 </td><td>EM DASH ('—')
3102: </td></tr><tr><td>0x98 </td><td>U+02DC </td><td>SMALL TILDE ('˜')
3103: </td></tr><tr><td>0x99 </td><td>U+2122 </td><td>TRADE MARK SIGN ('™')
3104: </td></tr><tr><td>0x9A </td><td>U+0161 </td><td>LATIN SMALL LETTER S WITH CARON ('š')
3105: </td></tr><tr><td>0x9B </td><td>U+203A </td><td>SINGLE RIGHT-POINTING ANGLE QUOTATION MARK ('›')
3106: </td></tr><tr><td>0x9C </td><td>U+0153 </td><td>LATIN SMALL LIGATURE OE ('œ')
3107: </td></tr><tr><td>0x9D </td><td>U+009D </td><td><control>
3108: </td></tr><tr><td>0x9E </td><td>U+017E </td><td>LATIN SMALL LETTER Z WITH CARON ('ž')
3109: </td></tr><tr><td>0x9F </td><td>U+0178 </td><td>LATIN CAPITAL LETTER Y WITH DIAERESIS ('Ÿ')
1.18 mike 3110: </td></tr></tbody></table><p>Otherwise, if the number is greater than 0x10FFFF, then this is
3111: a <a href="#parse-error">parse error</a>. Return a U+FFFD REPLACEMENT
3112: CHARACTER.</p>
3113:
3114: <p>Otherwise, return a character token for the Unicode character
1.1 mike 3115: whose code point is that number.
3116:
3117: <!-- this is the same as the equivalent list in the input stream
3118: section -->
3119: If the number is in the range 0x0001 to 0x0008, <!-- HT, LF
3120: allowed --> <!-- U+000B is in the next list --> <!-- FF, CR
3121: allowed --> 0x000E to 0x001F, <!-- ASCII allowed --> 0x007F <!--to
3122: 0x0084, (0x0085 NEL not allowed), 0x0086--> to 0x009F, 0xD800 to
3123: 0xDFFF<!-- surrogates not allowed -->, 0xFDD0 to 0xFDEF, or is one
3124: of 0x000B, 0xFFFE, 0xFFFF, 0x1FFFE, 0x1FFFF, 0x2FFFE, 0x2FFFF,
3125: 0x3FFFE, 0x3FFFF, 0x4FFFE, 0x4FFFF, 0x5FFFE, 0x5FFFF, 0x6FFFE,
3126: 0x6FFFF, 0x7FFFE, 0x7FFFF, 0x8FFFE, 0x8FFFF, 0x9FFFE, 0x9FFFF,
3127: 0xAFFFE, 0xAFFFF, 0xBFFFE, 0xBFFFF, 0xCFFFE, 0xCFFFF, 0xDFFFE,
3128: 0xDFFFF, 0xEFFFE, 0xEFFFF, 0xFFFFE, 0xFFFFF, 0x10FFFE, or
1.18 mike 3129: 0x10FFFF, then this is a <a href="#parse-error">parse error</a>.</p>
1.1 mike 3130:
3131: </dd>
3132:
3133:
3134: <dt>Anything else</dt>
3135:
3136: <dd>
3137:
3138: <p>Consume the maximum number of characters possible, with the
3139: consumed characters matching one of the identifiers in the first
3140: column of the <a href="named-character-references.html#named-character-references">named character references</a> table (in a
3141: <a href="infrastructure.html#case-sensitive">case-sensitive</a> manner).</p>
3142:
3143: <p>If no match can be made, then this is a <a href="#parse-error">parse
3144: error</a>. No characters are consumed, and nothing is
3145: returned.</p>
3146:
3147: <p>If the last character matched is not a U+003B SEMICOLON (<code title="">;</code>), there is a <a href="#parse-error">parse error</a>.</p>
3148:
3149: <p>If the character reference is being consumed <a href="#character-reference-in-attribute-value-state" title="character reference in attribute value state">as part of an
3150: attribute</a>, and the last character matched is not a U+003B
3151: SEMICOLON (<code title="">;</code>), and the next character is in
3152: the range U+0030 DIGIT ZERO to U+0039 DIGIT NINE, U+0041 LATIN
3153: CAPITAL LETTER A to U+005A LATIN CAPITAL LETTER Z, or U+0061 LATIN
3154: SMALL LETTER A to U+007A LATIN SMALL LETTER Z, then, for
3155: historical reasons, all the characters that were matched after the
3156: U+0026 AMPERSAND (&) must be unconsumed, and nothing is
3157: returned.</p>
3158:
3159: <p>Otherwise, return a character token for the character
3160: corresponding to the character reference name (as given by the
3161: second column of the <a href="named-character-references.html#named-character-references">named character references</a>
3162: table).</p>
3163:
3164: <div class="example">
3165:
3166: <p>If the markup contains <code title="">I'm &notit; I tell
3167: you</code>, the character reference is parsed as "not", as in,
3168: <code title="">I'm ¬it; I tell you</code>. But if the markup
3169: was <code title="">I'm &notin; I tell you</code>, the
3170: character reference would be parsed as "notin;", resulting in
3171: <code title="">I'm ∉ I tell you</code>.</p>
3172:
3173: </div>
3174:
3175: </dd>
3176:
3177: </dl><h4 id="tree-construction"><span class="secno">9.2.5 </span><dfn>Tree construction</dfn></h4>
3178:
3179: <p>The input to the tree construction stage is a sequence of tokens
3180: from the <a href="#tokenization">tokenization</a> stage. The tree construction
3181: stage is associated with a DOM <code>Document</code> object when a
3182: parser is created. The "output" of this stage consists of
3183: dynamically modifying or extending that document's DOM tree.</p>
3184:
3185: <p>This specification does not define when an interactive user agent
3186: has to render the <code>Document</code> so that it is available to
3187: the user, or when it has to begin accepting user input.</p>
3188:
3189: <p>As each token is emitted from the tokenizer, the user agent must
3190: process the token according to the rules given in the section
3191: corresponding to the current <a href="#insertion-mode">insertion mode</a>.</p>
3192:
3193: <p>When the steps below require the UA to <dfn id="insert-a-character">insert a
3194: character</dfn> into a node, if that node has a child immediately
3195: before where the character is to be inserted, and that child is a
3196: <code>Text</code> node, and that <code>Text</code> node was the last
3197: node that the parser inserted into the document, then the character
3198: must be appended to that <code>Text</code> node; otherwise, a new
3199: <code>Text</code> node whose data is just that character must be
3200: inserted in the appropriate place.</p>
3201:
3202: <div class="example">
3203:
3204: <p>Here are some sample inputs to the parser and the corresponding
3205: number of text nodes that they result in, assuming a user agent
3206: that executes scripts.</p>
3207:
3208: <table><thead><tr><th>Input </th><th>Number of text nodes
3209: </th></tr></thead><tbody><tr><td><pre>A<script>
3210: var script = document.getElementsByTagName('script')[0];
3211: document.body.removeChild(script);
3212: </script>B</pre>
3213: </td><td>Two adjacent text nodes in the document, containing "A" and "B".
3214: </td></tr><tr><td><pre>A<script>
3215: var text = document.createTextNode('B');
3216: document.body.appendChild(text);
3217: </script>C</pre>
3218: </td><td>Four text nodes; "A" before the script, the script's contents, "B" after the script, and then, immediately after that, "C".
3219: </td></tr><tr><td><pre>A<script>
3220: var text = document.getElementsByTagName('script')[0].firstChild;
3221: text.data = 'B';
3222: document.body.appendChild(text);
3223: </script>B</pre>
3224: </td><td>Two adjacent text nodes in the document, containing "A" and "BB".
3225: </td></tr><tr><td><pre>A<table>B<tr>C</tr>C</table></pre>
3226: </td><td>Three adjacent text nodes before the table, containing "A", "B", and "CC" respectively. (This is caused by <a href="#foster-parent" title="foster parent">foster parenting</a>.)
3227: </td></tr><tr><td><pre>A<table><tr> B</tr> B</table></pre>
3228: </td><td>Two adjacent text nodes before the table, containing "A" and " B B" (space-B-space-B) respectively. (This is caused by <a href="#foster-parent" title="foster parent">foster parenting</a>.)
3229: </td></tr><tr><td><pre>A<table><tr> B</tr> </em>C</table></pre>
3230: </td><td>Three adjacent text nodes before the table, containing "A", " B" (space-B), and "C" respectively, and one text node inside the table (as a child of a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>) with a single space character. (Space characters separated from non-space characters by non-character tokens are not affected by <a href="#foster-parent" title="foster parent">foster parenting</a>, even if those other tokens then get ignored.)
3231: </td></tr></tbody></table></div>
3232:
3233: <p id="mutation-during-parsing">DOM mutation events must not fire
3234: for changes caused by the UA parsing the document. (Conceptually,
3235: the parser is not mutating the DOM, it is constructing it.) This
1.159 mike 3236: includes the parsing of any content inserted using <code title="dom-document-write"><a href="embedded-content-0.html#dom-document-write">document.write()</a></code> and <code title="dom-document-writeln"><a href="embedded-content-0.html#dom-document-writeln">document.writeln()</a></code> calls. <a href="references.html#refsDOMEVENTS">[DOMEVENTS]</a></p>
1.1 mike 3237:
3238: <p class="note">Not all of the tag names mentioned below are
3239: conformant tag names in this specification; many are included to
3240: handle legacy content. They still form part of the algorithm that
3241: implementations are required to implement to claim conformance.</p>
3242:
3243: <p class="note">The algorithm described below places no limit on the
3244: depth of the DOM tree generated, or on the length of tag names,
3245: attribute names, attribute values, text nodes, etc. While
3246: implementors are encouraged to avoid arbitrary limits, it is
3247: recognized that <a href="infrastructure.html#hardwareLimitations">practical
3248: concerns</a> will likely force user agents to impose nesting
3249: depths.</p>
3250:
3251:
3252: <h5 id="creating-and-inserting-elements"><span class="secno">9.2.5.1 </span>Creating and inserting elements</h5>
3253:
3254: <p>When the steps below require the UA to <dfn id="create-an-element-for-the-token" title="create an
3255: element for the token">create an element for a token</dfn> in a
3256: particular namespace, the UA must create a node implementing the
3257: interface appropriate for the element type corresponding to the tag
3258: name of the token in the given namespace (as given in the
3259: specification that defines that element, e.g. for an <code><a href="text-level-semantics.html#the-a-element">a</a></code>
3260: element in the <a href="#html-namespace-0">HTML namespace</a>, this specification
3261: defines it to be the <code><a href="text-level-semantics.html#htmlanchorelement">HTMLAnchorElement</a></code> interface), with
3262: the tag name being the name of that element, with the node being in
3263: the given namespace, and with the attributes on the node being those
3264: given in the given token.</p>
3265:
3266: <p>The interface appropriate for an element in the <a href="#html-namespace-0">HTML
3267: namespace</a> that is not defined in this specification is
1.44 mike 3268: <code><a href="dom.html#htmlunknownelement">HTMLUnknownElement</a></code>. Element in other namespaces whose
1.1 mike 3269: interface is not defined by that namespace's specification must use
3270: the interface <code>Element</code>.</p>
3271:
3272: <p>When a <a href="forms.html#category-reset" title="category-reset">resettable</a> element is
3273: created in this manner, its <a href="forms.html#concept-form-reset-control" title="concept-form-reset-control">reset algorithm</a> must be
3274: invoked once the attributes are set. (This initializes the element's
3275: <a href="forms.html#concept-fe-value" title="concept-fe-value">value</a> and <a href="forms.html#concept-fe-checked" title="concept-fe-checked">checkedness</a> based on the element's
3276: attributes.)</p>
3277:
3278: <hr><p>When the steps below require the UA to <dfn id="insert-an-html-element">insert an HTML
3279: element</dfn> for a token, the UA must first <a href="#create-an-element-for-the-token">create an element
3280: for the token</a> in the <a href="#html-namespace-0">HTML namespace</a>, and then
3281: append this node to the <a href="#current-node">current node</a>, and push it onto
3282: the <a href="#stack-of-open-elements">stack of open elements</a> so that it is the new
3283: <a href="#current-node">current node</a>.</p>
3284:
3285: <p>The steps below may also require that the UA insert an HTML
3286: element in a particular place, in which case the UA must follow the
3287: same steps except that it must insert or append the new node in the
3288: location specified instead of appending it to the <a href="#current-node">current
3289: node</a>. (This happens in particular during the parsing of
3290: tables with invalid content.)</p>
3291:
3292: <p>If an element created by the <a href="#insert-an-html-element">insert an HTML element</a>
3293: algorithm is a <a href="forms.html#form-associated-element">form-associated element</a>, and the
3294: <a href="#form-element-pointer"><code title="">form</code> element pointer</a> is not null,
3295: and the newly created element doesn't have a <code title="attr-fae-form"><a href="forms.html#attr-fae-form">form</a></code> attribute, the user agent must
3296: <a href="forms.html#concept-form-association" title="concept-form-association">associate</a> the newly
3297: created element with the <code><a href="forms.html#the-form-element">form</a></code> element pointed to by the
3298: <a href="#form-element-pointer"><code title="">form</code> element pointer</a> before
3299: inserting it wherever it is to be inserted.</p>
3300:
3301: <hr><p>When the steps below require the UA to <dfn id="insert-a-foreign-element">insert a foreign
3302: element</dfn> for a token, the UA must first <a href="#create-an-element-for-the-token">create an element
3303: for the token</a> in the given namespace, and then append this
3304: node to the <a href="#current-node">current node</a>, and push it onto the
3305: <a href="#stack-of-open-elements">stack of open elements</a> so that it is the new
3306: <a href="#current-node">current node</a>. If the newly created element has an <code title="">xmlns</code> attribute in the <a href="#xmlns-namespace">XMLNS namespace</a>
3307: whose value is not exactly the same as the element's namespace, that
3308: is a <a href="#parse-error">parse error</a>. Similarly, if the newly created
3309: element has an <code title="">xmlns:xlink</code> attribute in the
3310: <a href="#xmlns-namespace">XMLNS namespace</a> whose value is not the <a href="#xlink-namespace">XLink
3311: Namespace</a>, that is a <a href="#parse-error">parse error</a>.</p>
3312:
3313: <p>When the steps below require the user agent to <dfn id="adjust-mathml-attributes">adjust MathML
3314: attributes</dfn> for a token, then, if the token has an attribute
3315: named <code title="">definitionurl</code>, change its name to <code title="">definitionURL</code> (note the case difference).</p>
3316:
3317: <p>When the steps below require the user agent to <dfn id="adjust-svg-attributes">adjust SVG
3318: attributes</dfn> for a token, then, for each attribute on the token
3319: whose attribute name is one of the ones in the first column of the
3320: following table, change the attribute's name to the name given in
3321: the corresponding cell in the second column. (This fixes the case of
3322: SVG attributes that are not all lowercase.)</p>
3323:
3324: <table><thead><tr><th> Attribute name on token </th><th> Attribute name on element
3325: </th></tr></thead><tbody><tr><td> <code title="">attributename</code> </td><td> <code title="">attributeName</code>
3326: </td></tr><tr><td> <code title="">attributetype</code> </td><td> <code title="">attributeType</code>
3327: </td></tr><tr><td> <code title="">basefrequency</code> </td><td> <code title="">baseFrequency</code>
3328: </td></tr><tr><td> <code title="">baseprofile</code> </td><td> <code title="">baseProfile</code>
3329: </td></tr><tr><td> <code title="">calcmode</code> </td><td> <code title="">calcMode</code>
3330: </td></tr><tr><td> <code title="">clippathunits</code> </td><td> <code title="">clipPathUnits</code>
3331: </td></tr><tr><td> <code title="">contentscripttype</code> </td><td> <code title="">contentScriptType</code>
3332: </td></tr><tr><td> <code title="">contentstyletype</code> </td><td> <code title="">contentStyleType</code>
3333: </td></tr><tr><td> <code title="">diffuseconstant</code> </td><td> <code title="">diffuseConstant</code>
3334: </td></tr><tr><td> <code title="">edgemode</code> </td><td> <code title="">edgeMode</code>
3335: </td></tr><tr><td> <code title="">externalresourcesrequired</code> </td><td> <code title="">externalResourcesRequired</code>
3336: </td></tr><tr><td> <code title="">filterres</code> </td><td> <code title="">filterRes</code>
3337: </td></tr><tr><td> <code title="">filterunits</code> </td><td> <code title="">filterUnits</code>
3338: </td></tr><tr><td> <code title="">glyphref</code> </td><td> <code title="">glyphRef</code>
3339: </td></tr><tr><td> <code title="">gradienttransform</code> </td><td> <code title="">gradientTransform</code>
3340: </td></tr><tr><td> <code title="">gradientunits</code> </td><td> <code title="">gradientUnits</code>
3341: </td></tr><tr><td> <code title="">kernelmatrix</code> </td><td> <code title="">kernelMatrix</code>
3342: </td></tr><tr><td> <code title="">kernelunitlength</code> </td><td> <code title="">kernelUnitLength</code>
3343: </td></tr><tr><td> <code title="">keypoints</code> </td><td> <code title="">keyPoints</code>
3344: </td></tr><tr><td> <code title="">keysplines</code> </td><td> <code title="">keySplines</code>
3345: </td></tr><tr><td> <code title="">keytimes</code> </td><td> <code title="">keyTimes</code>
3346: </td></tr><tr><td> <code title="">lengthadjust</code> </td><td> <code title="">lengthAdjust</code>
3347: </td></tr><tr><td> <code title="">limitingconeangle</code> </td><td> <code title="">limitingConeAngle</code>
3348: </td></tr><tr><td> <code title="">markerheight</code> </td><td> <code title="">markerHeight</code>
3349: </td></tr><tr><td> <code title="">markerunits</code> </td><td> <code title="">markerUnits</code>
3350: </td></tr><tr><td> <code title="">markerwidth</code> </td><td> <code title="">markerWidth</code>
3351: </td></tr><tr><td> <code title="">maskcontentunits</code> </td><td> <code title="">maskContentUnits</code>
3352: </td></tr><tr><td> <code title="">maskunits</code> </td><td> <code title="">maskUnits</code>
3353: </td></tr><tr><td> <code title="">numoctaves</code> </td><td> <code title="">numOctaves</code>
3354: </td></tr><tr><td> <code title="">pathlength</code> </td><td> <code title="">pathLength</code>
3355: </td></tr><tr><td> <code title="">patterncontentunits</code> </td><td> <code title="">patternContentUnits</code>
3356: </td></tr><tr><td> <code title="">patterntransform</code> </td><td> <code title="">patternTransform</code>
3357: </td></tr><tr><td> <code title="">patternunits</code> </td><td> <code title="">patternUnits</code>
3358: </td></tr><tr><td> <code title="">pointsatx</code> </td><td> <code title="">pointsAtX</code>
3359: </td></tr><tr><td> <code title="">pointsaty</code> </td><td> <code title="">pointsAtY</code>
3360: </td></tr><tr><td> <code title="">pointsatz</code> </td><td> <code title="">pointsAtZ</code>
3361: </td></tr><tr><td> <code title="">preservealpha</code> </td><td> <code title="">preserveAlpha</code>
3362: </td></tr><tr><td> <code title="">preserveaspectratio</code> </td><td> <code title="">preserveAspectRatio</code>
3363: </td></tr><tr><td> <code title="">primitiveunits</code> </td><td> <code title="">primitiveUnits</code>
3364: </td></tr><tr><td> <code title="">refx</code> </td><td> <code title="">refX</code>
3365: </td></tr><tr><td> <code title="">refy</code> </td><td> <code title="">refY</code>
3366: </td></tr><tr><td> <code title="">repeatcount</code> </td><td> <code title="">repeatCount</code>
3367: </td></tr><tr><td> <code title="">repeatdur</code> </td><td> <code title="">repeatDur</code>
3368: </td></tr><tr><td> <code title="">requiredextensions</code> </td><td> <code title="">requiredExtensions</code>
3369: </td></tr><tr><td> <code title="">requiredfeatures</code> </td><td> <code title="">requiredFeatures</code>
3370: </td></tr><tr><td> <code title="">specularconstant</code> </td><td> <code title="">specularConstant</code>
3371: </td></tr><tr><td> <code title="">specularexponent</code> </td><td> <code title="">specularExponent</code>
3372: </td></tr><tr><td> <code title="">spreadmethod</code> </td><td> <code title="">spreadMethod</code>
3373: </td></tr><tr><td> <code title="">startoffset</code> </td><td> <code title="">startOffset</code>
3374: </td></tr><tr><td> <code title="">stddeviation</code> </td><td> <code title="">stdDeviation</code>
3375: </td></tr><tr><td> <code title="">stitchtiles</code> </td><td> <code title="">stitchTiles</code>
3376: </td></tr><tr><td> <code title="">surfacescale</code> </td><td> <code title="">surfaceScale</code>
3377: </td></tr><tr><td> <code title="">systemlanguage</code> </td><td> <code title="">systemLanguage</code>
3378: </td></tr><tr><td> <code title="">tablevalues</code> </td><td> <code title="">tableValues</code>
3379: </td></tr><tr><td> <code title="">targetx</code> </td><td> <code title="">targetX</code>
3380: </td></tr><tr><td> <code title="">targety</code> </td><td> <code title="">targetY</code>
3381: </td></tr><tr><td> <code title="">textlength</code> </td><td> <code title="">textLength</code>
3382: </td></tr><tr><td> <code title="">viewbox</code> </td><td> <code title="">viewBox</code>
3383: </td></tr><tr><td> <code title="">viewtarget</code> </td><td> <code title="">viewTarget</code>
3384: </td></tr><tr><td> <code title="">xchannelselector</code> </td><td> <code title="">xChannelSelector</code>
3385: </td></tr><tr><td> <code title="">ychannelselector</code> </td><td> <code title="">yChannelSelector</code>
3386: </td></tr><tr><td> <code title="">zoomandpan</code> </td><td> <code title="">zoomAndPan</code>
3387: </td></tr></tbody></table><p>When the steps below require the user agent to <dfn id="adjust-foreign-attributes">adjust
3388: foreign attributes</dfn> for a token, then, if any of the attributes
3389: on the token match the strings given in the first column of the
3390: following table, let the attribute be a namespaced attribute, with
3391: the prefix being the string given in the corresponding cell in the
3392: second column, the local name being the string given in the
3393: corresponding cell in the third column, and the namespace being the
3394: namespace given in the corresponding cell in the fourth
3395: column. (This fixes the use of namespaced attributes, in particular
3396: <a href="dom.html#attr-xml-lang" title="attr-xml-lang"><code title="">lang</code> attributes in
3397: the <span>XML namespace</span></a>.)</p>
3398:
3399: <table><thead><tr><th> Attribute name </th><th> Prefix </th><th> Local name </th><th> Namespace
3400: </th></tr></thead><tbody><tr><td> <code title="">xlink:actuate</code> </td><td> <code title="">xlink</code> </td><td> <code title="">actuate</code> </td><td> <a href="#xlink-namespace">XLink namespace</a>
3401: </td></tr><tr><td> <code title="">xlink:arcrole</code> </td><td> <code title="">xlink</code> </td><td> <code title="">arcrole</code> </td><td> <a href="#xlink-namespace">XLink namespace</a>
3402: </td></tr><tr><td> <code title="">xlink:href</code> </td><td> <code title="">xlink</code> </td><td> <code title="">href</code> </td><td> <a href="#xlink-namespace">XLink namespace</a>
3403: </td></tr><tr><td> <code title="">xlink:role</code> </td><td> <code title="">xlink</code> </td><td> <code title="">role</code> </td><td> <a href="#xlink-namespace">XLink namespace</a>
3404: </td></tr><tr><td> <code title="">xlink:show</code> </td><td> <code title="">xlink</code> </td><td> <code title="">show</code> </td><td> <a href="#xlink-namespace">XLink namespace</a>
3405: </td></tr><tr><td> <code title="">xlink:title</code> </td><td> <code title="">xlink</code> </td><td> <code title="">title</code> </td><td> <a href="#xlink-namespace">XLink namespace</a>
3406: </td></tr><tr><td> <code title="">xlink:type</code> </td><td> <code title="">xlink</code> </td><td> <code title="">type</code> </td><td> <a href="#xlink-namespace">XLink namespace</a>
3407: </td></tr><tr><td> <code title="">xml:base</code> </td><td> <code title="">xml</code> </td><td> <code title="">base</code> </td><td> <a href="#xml-namespace">XML namespace</a> <!-- attr-xml-base -->
3408: </td></tr><tr><td> <code title="">xml:lang</code> </td><td> <code title="">xml</code> </td><td> <code title="">lang</code> </td><td> <a href="#xml-namespace">XML namespace</a>
3409: </td></tr><tr><td> <code title="">xml:space</code> </td><td> <code title="">xml</code> </td><td> <code title="">space</code> </td><td> <a href="#xml-namespace">XML namespace</a>
3410: </td></tr><tr><td> <code title="">xmlns</code> </td><td> (none) </td><td> <code title="">xmlns</code> </td><td> <a href="#xmlns-namespace">XMLNS namespace</a>
3411: </td></tr><tr><td> <code title="">xmlns:xlink</code> </td><td> <code title="">xmlns</code> </td><td> <code title="">xlink</code> </td><td> <a href="#xmlns-namespace">XMLNS namespace</a>
1.91 mike 3412: </td></tr></tbody></table><hr><p>The <dfn id="generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</dfn> and the
1.1 mike 3413: <dfn id="generic-rcdata-element-parsing-algorithm">generic RCDATA element parsing algorithm</dfn> consist of the
3414: following steps. These algorithms are always invoked in response to
3415: a start tag token.</p>
3416:
3417: <ol><li><p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p></li>
3418:
1.91 mike 3419: <li><p>If the algorithm that was invoked is the <a href="#generic-raw-text-element-parsing-algorithm">generic raw
3420: text element parsing algorithm</a>, switch the tokenizer's
3421: <a href="#content-model-flag">content model flag</a> to the RAWTEXT state; otherwise the
1.1 mike 3422: algorithm invoked was the <a href="#generic-rcdata-element-parsing-algorithm">generic RCDATA element parsing
3423: algorithm</a>, switch the tokenizer's <a href="#content-model-flag">content model
3424: flag</a> to the RCDATA state.</p></li>
3425:
3426: <li><p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the current
3427: <a href="#insertion-mode">insertion mode</a>.</p>
3428:
1.91 mike 3429: </li><li><p>Then, switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incdata" title="insertion mode: in RAWTEXT/RCDATA">in
3430: RAWTEXT/RCDATA</a>".</p></li>
1.1 mike 3431:
3432: </ol><h5 id="closing-elements-that-have-implied-end-tags"><span class="secno">9.2.5.2 </span>Closing elements that have implied end tags</h5>
3433:
3434: <p>When the steps below require the UA to <dfn id="generate-implied-end-tags">generate implied end
3435: tags</dfn>, then, while the <a href="#current-node">current node</a> is a
3436: <code><a href="semantics.html#the-dd-element">dd</a></code> element, a <code><a href="semantics.html#the-dt-element">dt</a></code> element, an
3437: <code><a href="semantics.html#the-li-element">li</a></code> element, an <code><a href="forms.html#the-option-element">option</a></code> element, an
3438: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, a <code><a href="semantics.html#the-p-element">p</a></code> element, an
3439: <code><a href="text-level-semantics.html#the-rp-element">rp</a></code> element, or an <code><a href="text-level-semantics.html#the-rt-element">rt</a></code> element, the UA must
3440: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
3441: elements</a>.</p>
3442:
3443: <p>If a step requires the UA to generate implied end tags but lists
3444: an element to exclude from the process, then the UA must perform the
3445: above steps as if that element was not in the above list.</p>
3446:
3447:
3448: <h5 id="foster-parenting"><span class="secno">9.2.5.3 </span>Foster parenting</h5>
3449:
3450: <p>Foster parenting happens when content is misnested in tables.</p>
3451:
3452: <p>When a node <var title="">node</var> is to be <dfn id="foster-parent" title="foster
3453: parent">foster parented</dfn>, the node <var title="">node</var>
3454: must be inserted into the <i><a href="#foster-parent-element">foster parent element</a></i>.</p>
3455:
3456: <p>The <dfn id="foster-parent-element">foster parent element</dfn> is the parent element of the
3457: last <code><a href="tabular-data.html#the-table-element">table</a></code> element in the <a href="#stack-of-open-elements">stack of open
3458: elements</a>, if there is a <code><a href="tabular-data.html#the-table-element">table</a></code> element and it has
3459: such a parent element. If there is no <code><a href="tabular-data.html#the-table-element">table</a></code> element in
3460: the <a href="#stack-of-open-elements">stack of open elements</a> (<a href="#fragment-case">fragment
3461: case</a>), then the <i><a href="#foster-parent-element">foster parent element</a></i> is the first
3462: element in the <a href="#stack-of-open-elements">stack of open elements</a> (the
1.159 mike 3463: <code><a href="semantics.html#the-html-element-0">html</a></code> element). Otherwise, if there is a
1.1 mike 3464: <code><a href="tabular-data.html#the-table-element">table</a></code> element in the <a href="#stack-of-open-elements">stack of open
3465: elements</a>, but the last <code><a href="tabular-data.html#the-table-element">table</a></code> element in the
3466: <a href="#stack-of-open-elements">stack of open elements</a> has no parent, or its parent
3467: node is not an element, then the <i><a href="#foster-parent-element">foster parent element</a></i> is
3468: the element before the last <code><a href="tabular-data.html#the-table-element">table</a></code> element in the
3469: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
3470:
3471: <p>If the <i><a href="#foster-parent-element">foster parent element</a></i> is the parent element of the
3472: last <code><a href="tabular-data.html#the-table-element">table</a></code> element in the <a href="#stack-of-open-elements">stack of open
3473: elements</a>, then <var title="">node</var> must be inserted
3474: immediately <em>before</em> the last <code><a href="tabular-data.html#the-table-element">table</a></code> element in
3475: the <a href="#stack-of-open-elements">stack of open elements</a> in the <i><a href="#foster-parent-element">foster parent
3476: element</a></i>; otherwise, <var title="">node</var> must be
3477: <em>appended</em> to the <i><a href="#foster-parent-element">foster parent element</a></i>.</p>
3478:
3479:
3480:
3481: <h5 id="the-initial-insertion-mode"><span class="secno">9.2.5.4 </span>The "<dfn title="insertion mode: initial">initial</dfn>" insertion mode</h5>
3482:
3483: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-initial-insertion-mode" title="insertion
3484: mode: initial">initial</a>", tokens must be handled as follows:</p>
3485:
3486: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
3487: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3488: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3489: <dd>
3490: <p>Ignore the token.</p>
3491: </dd>
3492:
3493: <dt>A comment token</dt>
3494: <dd>
3495: <p>Append a <code>Comment</code> node to the <code>Document</code>
3496: object with the <code title="">data</code> attribute set to the
3497: data given in the comment token.</p>
3498: </dd>
3499:
3500: <dt>A DOCTYPE token</dt>
3501: <dd>
3502:
3503: <p>If the DOCTYPE token's name is not a
3504: <a href="infrastructure.html#case-sensitive">case-sensitive</a> match for the string "<code title="">html</code>", or the token's public identifier is not
3505: missing, or the token's system identifier is neither missing nor a
3506: <a href="infrastructure.html#case-sensitive">case-sensitive</a> match for the string
3507: "<code>about:legacy-compat</code>", and none of the sets of
3508: conditions in the following list are matched, then there is a
3509: <a href="#parse-error">parse error</a>. If one of the sets of conditions in the
3510: following list is matched, then there is an <dfn id="obsolete-permitted-doctype">obsolete
3511: permitted DOCTYPE</dfn>.</p>
3512:
3513: <ul><!-- only things that trigger no-quirks mode and were valid in
3514: some other spec are allowed in this list --><li>The DOCTYPE token's name is an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.98 mike 3515: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3516: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD HTML 4.0//EN</code>", and the
3517: token's system identifier is either missing or the
3518: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">http://www.w3.org/TR/REC-html40/strict.dtd</code>".</li>
3519:
3520: <li>The DOCTYPE token's name is an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.98 mike 3521: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3522: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD HTML 4.01//EN</code>", and the
3523: token's system identifier is either missing or the
3524: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">http://www.w3.org/TR/html4/strict.dtd</code>".</li>
3525:
3526: <li>The DOCTYPE token's name is an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.98 mike 3527: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3528: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD XHTML 1.0 Strict//EN</code>",
3529: and the token's system identifier is the
3530: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</code>".</li>
3531:
3532: <li>The DOCTYPE token's name is an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.98 mike 3533: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3534: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD XHTML 1.1//EN</code>", and the
3535: token's system identifier is the <a href="infrastructure.html#case-sensitive">case-sensitive</a>
3536: string "<code title="">http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd</code>".</li>
3537:
3538: </ul><p>Conformance checkers may, based on the values (including
3539: presence or lack thereof) of the DOCTYPE token's name, public
3540: identifier, or system identifier, switch to a conformance checking
3541: mode for another language (e.g. based on the DOCTYPE token a
3542: conformance checker could recognize that the document is an
1.183 mike 3543: HTML4-era document, and defer to an HTML4 conformance
1.1 mike 3544: checker.)</p>
3545:
3546: <p>Append a <code>DocumentType</code> node to the
3547: <code>Document</code> node, with the <code title="">name</code>
3548: attribute set to the name given in the DOCTYPE token, or the empty
3549: string if the name was missing; the <code title="">publicId</code>
3550: attribute set to the public identifier given in the DOCTYPE token,
3551: or the empty string if the public identifier was missing; the
3552: <code title="">systemId</code> attribute set to the system
3553: identifier given in the DOCTYPE token, or the empty string if the
3554: system identifier was missing; and the other attributes specific
3555: to <code>DocumentType</code> objects set to null and empty lists
3556: as appropriate. Associate the <code>DocumentType</code> node with
3557: the <code>Document</code> object so that it is returned as the
3558: value of the <code title="">doctype</code> attribute of the
3559: <code>Document</code> object.</p>
3560:
3561: <p id="quirks-mode-doctypes">Then, if the DOCTYPE token matches
3562: one of the conditions in the following list, then set the
3563: <code>Document</code> to <a href="dom.html#quirks-mode">quirks mode</a>:</p>
3564:
3565: <ul class="brief"><li> The <i>force-quirks flag</i> is set to <i>on</i>. </li>
3566: <li> The name is set to anything other than "<code title="">HTML</code>". </li>
3567: <li> The public identifier starts with: "<code title="">+//Silmaril//dtd html Pro v0r11 19970101//<!--EN--></code>" </li>
3568: <li> The public identifier starts with: "<code title="">-//AdvaSoft Ltd//DTD HTML 3.0 asWedit + extensions//<!--EN--></code>" </li>
3569: <li> The public identifier starts with: "<code title="">-//AS//DTD HTML 3.0 asWedit + extensions//<!--EN--></code>" </li>
3570: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Level 1//<!--EN--></code>" </li>
3571: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Level 2//<!--EN--></code>" </li>
3572: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Strict Level 1//<!--EN--></code>" </li>
3573: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Strict Level 2//<!--EN--></code>" </li>
3574: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Strict//<!--EN--></code>" </li>
3575: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0//<!--EN--></code>" </li>
3576: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.1E//<!--EN--></code>" </li>
3577: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3.0//<!--EN--></code>" </li>
3578: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML 3.0//EN//</code>" </li>-->
3579: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3.2 Final//<!--EN--></code>" </li>
3580: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3.2//<!--EN--></code>" </li>
3581: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3//<!--EN--></code>" </li>
3582: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 0//<!--EN--></code>" </li>
3583: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 0//EN//2.0</code>" </li>-->
3584: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 1//<!--EN--></code>" </li>
3585: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 1//EN//2.0</code>" </li>-->
3586: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 2//<!--EN--></code>" </li>
3587: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 2//EN//2.0</code>" </li>-->
3588: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 3//<!--EN--></code>" </li>
3589: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 3//EN//3.0</code>" </li>-->
3590: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 0//<!--EN--></code>" </li>
3591: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 0//EN//2.0</code>" </li>-->
3592: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 1//<!--EN--></code>" </li>
3593: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 1//EN//2.0</code>" </li>-->
3594: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 2//<!--EN--></code>" </li>
3595: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 2//EN//2.0</code>" </li>-->
3596: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 3//<!--EN--></code>" </li>
3597: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 3//EN//3.0</code>" </li>-->
3598: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict//<!--EN--></code>" </li>
3599: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict//EN//2.0</code>" </li>-->
3600: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict//EN//3.0</code>" </li>-->
3601: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML//<!--EN--></code>" </li>
3602: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML//EN//2.0</code>" </li>-->
3603: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML//EN//3.0</code>" </li>-->
3604: <li> The public identifier starts with: "<code title="">-//Metrius//DTD Metrius Presentational//<!--EN--></code>" </li>
3605: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 2.0 HTML Strict//<!--EN--></code>" </li>
3606: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 2.0 HTML//<!--EN--></code>" </li>
3607: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 2.0 Tables//<!--EN--></code>" </li>
3608: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 3.0 HTML Strict//<!--EN--></code>" </li>
3609: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 3.0 HTML//<!--EN--></code>" </li>
3610: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 3.0 Tables//<!--EN--></code>" </li>
3611: <li> The public identifier starts with: "<code title="">-//Netscape Comm. Corp.//DTD HTML//<!--EN--></code>" </li>
3612: <li> The public identifier starts with: "<code title="">-//Netscape Comm. Corp.//DTD Strict HTML//<!--EN--></code>" </li>
3613: <li> The public identifier starts with: "<code title="">-//O'Reilly and Associates//DTD HTML 2.0//<!--EN--></code>" </li>
3614: <li> The public identifier starts with: "<code title="">-//O'Reilly and Associates//DTD HTML Extended 1.0//<!--EN--></code>" </li>
3615: <li> The public identifier starts with: "<code title="">-//O'Reilly and Associates//DTD HTML Extended Relaxed 1.0//<!--EN--></code>" </li>
3616: <li> The public identifier starts with: "<code title="">-//SoftQuad Software//DTD HoTMetaL PRO 6.0::19990601::extensions to HTML 4.0//<!--EN--></code>" </li>
3617: <li> The public identifier starts with: "<code title="">-//SoftQuad//DTD HoTMetaL PRO 4.0::19971010::extensions to HTML 4.0//<!--EN--></code>" </li>
3618: <li> The public identifier starts with: "<code title="">-//Spyglass//DTD HTML 2.0 Extended//<!--EN--></code>" </li>
3619: <li> The public identifier starts with: "<code title="">-//SQ//DTD HTML 2.0 HoTMetaL + extensions//<!--EN--></code>" </li>
3620: <li> The public identifier starts with: "<code title="">-//Sun Microsystems Corp.//DTD HotJava HTML//<!--EN--></code>" </li>
3621: <li> The public identifier starts with: "<code title="">-//Sun Microsystems Corp.//DTD HotJava Strict HTML//<!--EN--></code>" </li>
3622: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3 1995-03-24//<!--EN--></code>" </li>
3623: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2 Draft//<!--EN--></code>" </li>
3624: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2 Final//<!--EN--></code>" </li>
3625: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2//<!--EN--></code>" </li>
3626: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2S Draft//<!--EN--></code>" </li>
3627: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 4.0 Frameset//<!--EN--></code>" </li>
3628: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 4.0 Transitional//<!--EN--></code>" </li>
3629: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML Experimental 19960712//<!--EN--></code>" </li>
3630: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML Experimental 970421//<!--EN--></code>" </li>
3631: <li> The public identifier starts with: "<code title="">-//W3C//DTD W3 HTML//<!--EN--></code>" </li>
3632: <li> The public identifier starts with: "<code title="">-//W3O//DTD W3 HTML 3.0//<!--EN--></code>" </li>
3633: <!--<li> The public identifier is set to: "<code title="">-//W3O//DTD W3 HTML 3.0//EN//</code>" </li>-->
3634: <li> The public identifier is set to: "<code title="">-//W3O//DTD W3 HTML Strict 3.0//EN//</code>" </li>
3635: <li> The public identifier starts with: "<code title="">-//WebTechs//DTD Mozilla HTML 2.0//<!--EN--></code>" </li>
3636: <li> The public identifier starts with: "<code title="">-//WebTechs//DTD Mozilla HTML//<!--EN--></code>" </li>
3637: <li> The public identifier is set to: "<code title="">-/W3C/DTD HTML 4.0 Transitional/EN</code>" </li>
3638: <li> The public identifier is set to: "<code title="">HTML</code>" </li>
3639: <li> The system identifier is set to: "<code title="">http://www.ibm.com/data/dtd/v11/ibmxhtml1-transitional.dtd</code>" </li>
3640: <li> The system identifier is missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Frameset//<!--EN--></code>" </li>
3641: <li> The system identifier is missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Transitional//<!--EN--></code>" </li>
3642: </ul><p>Otherwise, if the DOCTYPE token matches one of the conditions
3643: in the following list, then set the <code>Document</code> to
3644: <a href="dom.html#limited-quirks-mode">limited quirks mode</a>:</p>
3645:
3646: <ul class="brief"><li> The public identifier starts with: "<code title="">-//W3C//DTD XHTML 1.0 Frameset//<!--EN--></code>" </li>
3647: <li> The public identifier starts with: "<code title="">-//W3C//DTD XHTML 1.0 Transitional//<!--EN--></code>" </li>
3648: <li> The system identifier is not missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Frameset//<!--EN--></code>" </li>
3649: <li> The system identifier is not missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Transitional//<!--EN--></code>" </li>
3650: </ul><p>The name, system identifier, and public identifier strings must
3651: be compared to the values given in the lists above in an
3652: <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> manner. A system identifier
3653: whose value is the empty string is not considered missing for the
3654: purposes of the conditions above.</p>
3655:
3656: <p>Then, switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-before-html-insertion-mode" title="insertion mode: before html">before html</a>".</p>
3657:
3658: </dd>
3659:
3660: <dt>Anything else</dt>
3661: <dd>
3662:
3663: <p><a href="#parse-error">Parse error</a>.</p>
3664:
3665: <p>Set the <code>Document</code> to <a href="dom.html#quirks-mode">quirks mode</a>.</p>
3666:
3667: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-before-html-insertion-mode" title="insertion mode: before html">before html</a>", then
3668: reprocess the current token.</p>
3669:
3670: </dd>
3671:
3672: </dl><h5 id="the-before-html-insertion-mode"><span class="secno">9.2.5.5 </span>The "<dfn title="insertion mode: before html">before html</dfn>" insertion mode</h5>
3673:
3674: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-before-html-insertion-mode" title="insertion
3675: mode: before html">before html</a>", tokens must be handled as follows:</p>
3676:
3677: <dl class="switch"><dt>A DOCTYPE token</dt>
3678: <dd>
3679: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3680: </dd>
3681:
3682: <dt>A comment token</dt>
3683: <dd>
3684: <p>Append a <code>Comment</code> node to the <code>Document</code>
3685: object with the <code title="">data</code> attribute set to the
3686: data given in the comment token.</p>
3687: </dd>
3688:
3689: <dt>A character token that is one of U+0009 CHARACTER
3690: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3691: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3692: <dd>
3693: <p>Ignore the token.</p>
3694: </dd>
3695:
3696: <dt>A start tag whose tag name is "html"</dt>
3697: <dd>
3698:
3699: <p><a href="#create-an-element-for-the-token">Create an element for the token</a> in the <a href="#html-namespace-0">HTML
3700: namespace</a>. Append it to the <code>Document</code>
3701: object. Put this element in the <a href="#stack-of-open-elements">stack of open
3702: elements</a>.</p>
3703:
3704: <p id="parser-appcache">If the <code>Document</code> is being
3705: loaded as part of <a href="history.html#navigate" title="navigate">navigation</a> of a
3706: <a href="browsers.html#browsing-context">browsing context</a>, then: if the newly created element
3707: has a <code title="attr-html-manifest"><a href="semantics.html#attr-html-manifest">manifest</a></code> attribute,
3708: then <a href="infrastructure.html#resolve-a-url" title="resolve a url">resolve</a> the value of that
3709: attribute to an <a href="infrastructure.html#absolute-url">absolute URL</a>, relative to the newly
3710: created element, and if that is successful, run the <a href="offline.html#concept-appcache-init" title="concept-appcache-init">application cache selection
1.29 mike 3711: algorithm</a> with the resulting <a href="infrastructure.html#absolute-url">absolute URL</a> with
3712: any <a href="infrastructure.html#url-fragment" title="url-fragment"><fragment></a> component
3713: removed; otherwise, if there is no such attribute or resolving it
3714: fails, run the <a href="offline.html#concept-appcache-init" title="concept-appcache-init">application
3715: cache selection algorithm</a> with no manifest. The algorithm
3716: must be passed the <code>Document</code> object.</p>
1.1 mike 3717:
3718: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-before-head-insertion-mode" title="insertion mode: before head">before head</a>".</p>
3719:
3720: </dd>
3721:
3722: <dt>Anything else</dt>
3723: <dd>
3724:
1.159 mike 3725: <p>Create an <code><a href="semantics.html#the-html-element-0">html</a></code> element. Append it to the
1.1 mike 3726: <code>Document</code> object. Put this element in the <a href="#stack-of-open-elements">stack
3727: of open elements</a>.</p>
3728:
3729: <p>If the <code>Document</code> is being loaded as part of <a href="history.html#navigate" title="navigate">navigation</a> of a <a href="browsers.html#browsing-context">browsing
3730: context</a>, then: run the <a href="offline.html#concept-appcache-init" title="concept-appcache-init">application cache selection
3731: algorithm</a> with no manifest, passing it the
3732: <code>Document</code> object.</p>
3733:
3734: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-before-head-insertion-mode" title="insertion mode: before head">before head</a>", then
3735: reprocess the current token.</p>
3736:
3737: <p class="XXX">Should probably make end tags be ignored, so
3738: that "</head><!-- --><html>" puts the comment before the
3739: root node (or should we?)</p>
3740:
3741: </dd>
3742:
3743: </dl><p>The root element can end up being removed from the
3744: <code>Document</code> object, e.g. by scripts; nothing in particular
3745: happens in such cases, content continues being appended to the nodes
3746: as described in the next section.</p>
3747:
3748:
3749: <h5 id="the-before-head-insertion-mode"><span class="secno">9.2.5.6 </span>The "<dfn title="insertion mode: before head">before head</dfn>" insertion mode</h5>
3750:
3751: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-before-head-insertion-mode" title="insertion
3752: mode: before head">before head</a>", tokens must be handled as follows:</p>
3753:
3754: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
3755: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3756: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3757: <dd>
3758: <p>Ignore the token.</p> <!-- :-( -->
3759: </dd>
3760:
3761: <dt>A comment token</dt>
3762: <dd>
3763: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
3764: node</a> with the <code title="">data</code> attribute set to
3765: the data given in the comment token.</p>
3766: </dd>
3767:
3768: <dt>A DOCTYPE token</dt>
3769: <dd>
3770: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3771: </dd>
3772:
3773: <dt>A start tag whose tag name is "html"</dt>
3774: <dd>
3775: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
3776: mode</a>.</p>
3777: </dd>
3778:
3779: <dt>A start tag whose tag name is "head"</dt>
3780: <dd>
3781:
3782: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
3783:
3784: <p>Set the <a href="#head-element-pointer"><code title="">head</code> element pointer</a>
1.159 mike 3785: to the newly created <code><a href="semantics.html#the-head-element-0">head</a></code> element.</p>
1.1 mike 3786:
3787: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>".</p>
3788:
3789: </dd>
3790:
3791: <dt>An end tag whose tag name is one of: "head", "body", "html", "br"</dt>
3792: <dd>
3793:
3794: <p>Act as if a start tag token with the tag name "head" and no
3795: attributes had been seen, then reprocess the current token.</p>
3796:
3797: </dd>
3798:
3799: <dt>Any other end tag</dt>
3800: <dd>
3801:
3802: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3803:
3804: </dd>
3805:
3806: <dt>Anything else</dt>
3807: <dd>
3808:
3809: <p>Act as if a start tag token with the tag name "head" and no
3810: attributes had been seen, then reprocess the current
3811: token.</p>
3812:
3813: </dd>
3814:
3815: </dl><h5 id="parsing-main-inhead"><span class="secno">9.2.5.7 </span>The "<dfn title="insertion mode: in head">in head</dfn>" insertion mode</h5>
3816:
3817: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inhead" title="insertion
3818: mode: in head">in head</a>", tokens must be handled as follows:</p>
3819:
3820: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
3821: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3822: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3823: <dd>
3824: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
3825: the <a href="#current-node">current node</a>.</p>
3826: </dd>
3827:
3828: <dt>A comment token</dt>
3829: <dd>
3830: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
3831: node</a> with the <code title="">data</code> attribute set to
3832: the data given in the comment token.</p>
3833: </dd>
3834:
3835: <dt>A DOCTYPE token</dt>
3836: <dd>
3837: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3838: </dd>
3839:
3840: <dt>A start tag whose tag name is "html"</dt>
3841: <dd>
3842: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
3843: mode</a>.</p>
3844: </dd>
3845:
3846: <dt>A start tag whose tag name is one of: "base", "command",
3847: "link"</dt>
3848: <dd>
3849:
3850: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
3851: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
3852: elements</a>.</p>
3853:
3854: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
3855: token's <i>self-closing flag</i></a>, if it is set.</p>
3856:
3857: </dd>
3858:
3859: <dt>A start tag whose tag name is "meta"</dt>
3860: <dd>
3861:
3862: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
3863: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
3864: elements</a>.</p>
3865:
3866: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
3867: token's <i>self-closing flag</i></a>, if it is set.</p>
3868:
3869: <p id="meta-charset-during-parse">If the element has a <code title="attr-meta-charset"><a href="semantics.html#attr-meta-charset">charset</a></code> attribute, and its
3870: value is a supported encoding, and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
3871: currently <i>tentative</i>, then <a href="#change-the-encoding">change the
3872: encoding</a> to the encoding given by the value of the
3873: <code title="attr-meta-charset"><a href="semantics.html#attr-meta-charset">charset</a></code> attribute.</p>
3874:
3875: <p>Otherwise, if the element has a <code title="attr-meta-charset"><a href="semantics.html#attr-meta-charset">content</a></code> attribute, and
3876: applying the <a href="infrastructure.html#algorithm-for-extracting-an-encoding-from-a-content-type">algorithm for extracting an encoding from a
3877: Content-Type</a> to its value returns a supported encoding
3878: <var title="">encoding</var>, and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
3879: currently <i>tentative</i>, then <a href="#change-the-encoding">change the
3880: encoding</a> to the encoding <var title="">encoding</var>.</p>
3881:
3882: </dd>
3883:
3884: <dt>A start tag whose tag name is "title"</dt>
3885: <dd>
3886: <p>Follow the <a href="#generic-rcdata-element-parsing-algorithm">generic RCDATA element parsing algorithm</a>.</p>
3887: </dd>
3888:
3889: <dt>A start tag whose tag name is "noscript", if the <a href="#scripting-flag">scripting flag</a> is enabled</dt>
3890: <dt>A start tag whose tag name is one of: "noframes", "style"</dt>
3891: <dd>
1.91 mike 3892: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 3893: </dd>
3894:
3895: <dt>A start tag whose tag name is "noscript", if the <a href="#scripting-flag">scripting flag</a> is disabled</dt>
3896: <dd>
3897:
3898: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
3899:
3900: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inheadnoscript" title="insertion mode: in head noscript">in head
3901: noscript</a>".</p>
3902:
3903: </dd>
3904:
3905: <dt id="scriptTag">A start tag whose tag name is "script"</dt>
3906: <dd>
3907:
3908: <ol><li><p><a href="#create-an-element-for-the-token">Create an element for the token</a> in the
3909: <a href="#html-namespace-0">HTML namespace</a>.</p></li>
3910:
3911: <li>
3912:
3913: <p>Mark the element as being <a href="semantics.html#parser-inserted">"parser-inserted"</a>.</p>
3914:
3915: <p class="note">This ensures that, if the script is external,
1.159 mike 3916: any <code title="dom-document-write"><a href="embedded-content-0.html#dom-document-write">document.write()</a></code>
1.1 mike 3917: calls in the script will execute in-line, instead of blowing the
3918: document away, as would happen in most other cases. It also
3919: prevents the script from executing until the end tag is
3920: seen.</p>
3921:
3922: </li>
3923:
3924: <li><p>If the parser was originally created for the <a href="#html-fragment-parsing-algorithm">HTML
3925: fragment parsing algorithm</a>, then mark the
3926: <code><a href="semantics.html#script">script</a></code> element as <a href="semantics.html#already-executed">"already
3927: executed"</a>. (<a href="#fragment-case">fragment case</a>)</p></li>
3928:
3929: <li><p>Append the new element to the <a href="#current-node">current node</a>
3930: and push it onto the <a href="#stack-of-open-elements">stack of open
3931: elements</a>.</p></li>
3932:
3933: <li><p>Switch the tokenizer's <a href="#content-model-flag">content model flag</a> to
1.91 mike 3934: the RAWTEXT state.</p></li>
1.1 mike 3935:
3936: <li><p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the current
3937: <a href="#insertion-mode">insertion mode</a>.</p>
3938:
1.91 mike 3939: </li><li><p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incdata" title="insertion mode: in RAWTEXT/RCDATA">in
3940: RAWTEXT/RCDATA</a>".</p></li>
1.1 mike 3941:
3942: </ol></dd>
3943:
3944: <dt>An end tag whose tag name is "head"</dt>
3945: <dd>
3946:
3947: <p>Pop the <a href="#current-node">current node</a> (which will be the
1.159 mike 3948: <code><a href="semantics.html#the-head-element-0">head</a></code> element) off the <a href="#stack-of-open-elements">stack of open
1.1 mike 3949: elements</a>.</p>
3950:
3951: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-after-head-insertion-mode" title="insertion mode: after head">after head</a>".</p>
3952:
3953: </dd>
3954:
3955: <dt>An end tag whose tag name is one of: "body", "html", "br"</dt>
3956: <dd>
3957: <p>Act as described in the "anything else" entry below.</p>
3958: </dd>
3959:
3960: <dt>A start tag whose tag name is "head"</dt>
3961: <dt>Any other end tag</dt>
3962: <dd>
3963: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3964: </dd>
3965:
3966: <dt>Anything else</dt>
3967: <dd>
3968:
3969: <!-- can't get here with an EOF and a fragment case -->
3970:
3971: <p>Act as if an end tag token with the tag name "head" had
3972: been seen, and reprocess the current token.</p>
3973:
3974: <p class="XXX">In certain UAs, <a href="https://bugzilla.mozilla.org/attachment.cgi?id=180157&action=view">some
3975: elements</a> don't trigger the "in body" mode straight away,
3976: but instead get put into the head. Do we want to copy
3977: that?</p>
3978:
3979: </dd>
3980:
3981: </dl><h5 id="parsing-main-inheadnoscript"><span class="secno">9.2.5.8 </span>The "<dfn title="insertion mode: in head noscript">in head noscript</dfn>" insertion mode</h5>
3982:
3983: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inheadnoscript" title="insertion
3984: mode: in head noscript">in head noscript</a>", tokens must be handled as follows:</p>
3985:
3986: <dl class="switch"><dt>A DOCTYPE token</dt>
3987: <dd>
3988: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3989: </dd>
3990:
3991: <dt>A start tag whose tag name is "html"</dt>
3992: <dd>
3993: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
3994: mode</a>.</p>
3995: </dd>
3996:
3997: <dt>An end tag whose tag name is "noscript"</dt>
3998: <dd>
3999:
4000: <p>Pop the <a href="#current-node">current node</a> (which will be a
4001: <code><a href="semantics.html#the-noscript-element">noscript</a></code> element) from the <a href="#stack-of-open-elements">stack of open
4002: elements</a>; the new <a href="#current-node">current node</a> will be a
1.159 mike 4003: <code><a href="semantics.html#the-head-element-0">head</a></code> element.</p>
1.1 mike 4004:
4005: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>".</p>
4006:
4007: </dd>
4008:
4009: <dt>A character token that is one of U+0009 CHARACTER
4010: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
4011: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
4012: <dt>A comment token</dt>
4013: <dt>A start tag whose tag name is one of: "link", "meta", "noframes", "style"</dt>
4014: <dd>
4015: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
4016: mode</a>.</p>
4017: </dd>
4018:
4019: <dt>An end tag whose tag name is "br"</dt>
4020: <dd>
4021: <p>Act as described in the "anything else" entry below.</p>
4022: </dd>
4023:
4024: <dt>A start tag whose tag name is one of: "head", "noscript"</dt>
4025: <dt>Any other end tag</dt>
4026: <dd>
4027: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4028: </dd>
4029:
4030: <dt>Anything else</dt>
4031: <dd>
4032:
4033: <!-- can't get here with an EOF and a fragment case -->
4034:
4035: <p><a href="#parse-error">Parse error</a>. Act as if an end tag with the tag
4036: name "noscript" had been seen and reprocess the current
4037: token.</p>
4038:
4039: </dd>
4040:
4041: </dl><h5 id="the-after-head-insertion-mode"><span class="secno">9.2.5.9 </span>The "<dfn title="insertion mode: after head">after head</dfn>" insertion mode</h5>
4042:
4043: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-after-head-insertion-mode" title="insertion
4044: mode: after head">after head</a>", tokens must be handled as follows:</p>
4045:
4046: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
4047: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
4048: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
4049: <dd>
4050: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
4051: the <a href="#current-node">current node</a>.</p>
4052: </dd>
4053:
4054: <dt>A comment token</dt>
4055: <dd>
4056: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
4057: node</a> with the <code title="">data</code> attribute set to
4058: the data given in the comment token.</p>
4059: </dd>
4060:
4061: <dt>A DOCTYPE token</dt>
4062: <dd>
4063: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4064: </dd>
4065:
4066: <dt>A start tag whose tag name is "html"</dt>
4067: <dd>
4068: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
4069: mode</a>.</p>
4070: </dd>
4071:
4072: <dt>A start tag whose tag name is "body"</dt>
4073: <dd>
4074:
4075: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4076:
4077: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4078:
4079: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>".</p>
4080:
4081: </dd>
4082:
4083: <dt>A start tag whose tag name is "frameset"</dt>
4084: <dd>
4085:
4086: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4087:
4088: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inframeset" title="insertion mode: in frameset">in frameset</a>".</p>
4089:
4090: </dd>
4091:
4092: <dt>A start tag token whose tag name is one of: "base", "link",
4093: "meta", "noframes", "script", "style", "title"</dt>
4094: <dd>
4095:
4096: <p><a href="#parse-error">Parse error</a>.</p>
4097:
4098: <p>Push the node pointed to by the <a href="#head-element-pointer"><code title="">head</code> element pointer</a> onto the
4099: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
4100:
4101: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
4102: mode</a>.</p>
4103:
4104: <p>Remove the node pointed to by the <a href="#head-element-pointer"><code title="">head</code> element pointer</a> from the <a href="#stack-of-open-elements">stack
4105: of open elements</a>.</p>
4106:
4107: <p class="note">The <a href="#head-element-pointer"><code title="">head</code> element
4108: pointer</a> cannot be null at this point.</p>
4109:
4110: </dd>
4111:
4112: <dt>An end tag whose tag name is one of: "body", "html", "br"</dt>
4113: <dd>
4114: <p>Act as described in the "anything else" entry below.</p>
4115: </dd>
4116:
4117: <dt>A start tag whose tag name is "head"</dt>
4118: <dt>Any other end tag</dt>
4119: <dd>
4120: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4121: </dd>
4122:
4123: <dt>Anything else</dt>
4124: <dd>
4125: <p>Act as if a start tag token with the tag name "body" and no
4126: attributes had been seen, then set the <a href="#frameset-ok-flag">frameset-ok
4127: flag</a> back to "ok", and then reprocess the current
4128: token.</p>
4129: </dd>
4130:
4131: </dl><h5 id="parsing-main-inbody"><span class="secno">9.2.5.10 </span>The "<dfn title="insertion mode: in body">in body</dfn>" insertion mode</h5>
4132:
4133: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inbody" title="insertion
4134: mode: in body">in body</a>", tokens must be handled as follows:</p>
4135:
4136: <dl class="switch"><dt>A character token</dt>
4137: <dd>
4138:
4139: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4140: any.</p>
4141:
4142: <p><a href="#insert-a-character" title="insert a character">Insert the token's
4143: character</a> into the <a href="#current-node">current node</a>.</p>
4144:
4145: <p>If the token is not one of U+0009 CHARACTER TABULATION, U+000A
4146: LINE FEED (LF), U+000C FORM FEED (FF), <!--U+000D CARRIAGE RETURN
4147: (CR),--> or U+0020 SPACE, then set the <a href="#frameset-ok-flag">frameset-ok
4148: flag</a> to "not ok".</p>
4149:
4150: </dd>
4151:
4152: <dt>A comment token</dt>
4153: <dd>
4154: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
4155: node</a> with the <code title="">data</code> attribute set to
4156: the data given in the comment token.</p>
4157: </dd>
4158:
4159: <dt>A DOCTYPE token</dt>
4160: <dd>
4161: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4162: </dd>
4163:
4164: <dt>A start tag whose tag name is "html"</dt>
4165: <dd>
4166: <p><a href="#parse-error">Parse error</a>. For each attribute on the token,
4167: check to see if the attribute is already present on the top
4168: element of the <a href="#stack-of-open-elements">stack of open elements</a>. If it is not,
4169: add the attribute and its corresponding value to that element.</p>
4170: </dd>
4171:
4172: <dt>A start tag token whose tag name is one of: "base", "command",
4173: "link", "meta", "noframes", "script", "style", "title"</dt>
4174: <dd>
4175: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
4176: mode</a>.</p>
4177: </dd>
4178:
4179: <dt>A start tag whose tag name is "body"</dt>
4180: <dd>
4181:
4182: <p><a href="#parse-error">Parse error</a>.</p>
4183:
4184: <p>If the second element on the <a href="#stack-of-open-elements">stack of open
1.159 mike 4185: elements</a> is not a <code><a href="semantics.html#the-body-element-0">body</a></code> element, or, if the
1.1 mike 4186: <a href="#stack-of-open-elements">stack of open elements</a> has only one node on it,
4187: then ignore the token. (<a href="#fragment-case">fragment case</a>)</p>
4188:
4189: <p>Otherwise, for each attribute on the token, check to see if
1.159 mike 4190: the attribute is already present on the <code><a href="semantics.html#the-body-element-0">body</a></code>
1.1 mike 4191: element (the second element) on the <a href="#stack-of-open-elements">stack of open
4192: elements</a>. If it is not, add the attribute and its
4193: corresponding value to that element.</p>
4194:
4195: </dd>
4196:
4197: <dt>A start tag whose tag name is "frameset"</dt>
4198: <dd>
4199:
4200: <p><a href="#parse-error">Parse error</a>.</p>
4201:
4202: <p>If the second element on the <a href="#stack-of-open-elements">stack of open
1.159 mike 4203: elements</a> is not a <code><a href="semantics.html#the-body-element-0">body</a></code> element, or, if the
1.1 mike 4204: <a href="#stack-of-open-elements">stack of open elements</a> has only one node on it,
4205: then ignore the token. (<a href="#fragment-case">fragment case</a>)</p>
4206:
4207: <p>If the <a href="#frameset-ok-flag">frameset-ok flag</a> is set to "not ok", ignore
4208: the token.</p>
4209:
4210: <p>Otherwise, run the following steps:</p>
4211:
4212: <ol><li><p>Remove the second element on the <a href="#stack-of-open-elements">stack of open
4213: elements</a> from its parent node, if it has one.</p></li>
4214:
4215: <li><p>Pop all the nodes from the bottom of the <a href="#stack-of-open-elements">stack of
4216: open elements</a>, from the <a href="#current-node">current node</a> up to,
1.159 mike 4217: but not including, the root <code><a href="semantics.html#the-html-element-0">html</a></code> element.</p>
1.1 mike 4218:
4219: </li><li><p><a href="#insert-an-html-element">Insert an HTML element</a> for the
4220: token.</p></li>
4221:
4222: <li><p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inframeset" title="insertion mode: in frameset">in frameset</a>".</p>
4223:
4224: </li></ol></dd>
4225:
4226: <dt>An end-of-file token</dt>
4227: <dd>
4228:
4229: <p>If there is a node in the <a href="#stack-of-open-elements">stack of open elements</a>
4230: that is not either a <code><a href="semantics.html#the-dd-element">dd</a></code> element, a <code><a href="semantics.html#the-dt-element">dt</a></code>
4231: element, an <code><a href="semantics.html#the-li-element">li</a></code> element, a <code><a href="semantics.html#the-p-element">p</a></code> element, a
4232: <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element, a <code><a href="tabular-data.html#the-td-element">td</a></code> element, a
4233: <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element, a <code><a href="tabular-data.html#the-th-element">th</a></code> element, a
4234: <code><a href="tabular-data.html#the-thead-element">thead</a></code> element, a <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, the
1.159 mike 4235: <code><a href="semantics.html#the-body-element-0">body</a></code> element, or the <code><a href="semantics.html#the-html-element-0">html</a></code> element, then
1.1 mike 4236: this is a <a href="#parse-error">parse error</a>.</p> <!-- (some of those are
4237: fragment cases) -->
4238:
4239: <p><a href="#stop-parsing">Stop parsing</a>.</p>
4240:
4241: </dd>
4242:
4243: <dt>An end tag whose tag name is "body"</dt>
4244: <dd>
4245:
4246: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-scope" title="has an element in scope">have a <code>body</code> element
4247: in scope</a>, this is a <a href="#parse-error">parse error</a>; ignore the
4248: token.</p>
4249:
4250: <!-- if we get here, the insertion mode here is forcibly "in
4251: body". -->
4252:
4253: <p>Otherwise, if there is a node in the <a href="#stack-of-open-elements">stack of open
4254: elements</a> that is not either a <code><a href="semantics.html#the-dd-element">dd</a></code> element, a
4255: <code><a href="semantics.html#the-dt-element">dt</a></code> element, an <code><a href="semantics.html#the-li-element">li</a></code> element, an
4256: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, an <code><a href="forms.html#the-option-element">option</a></code> element, a
4257: <code><a href="semantics.html#the-p-element">p</a></code> element, an <code><a href="text-level-semantics.html#the-rp-element">rp</a></code> element, an
4258: <code><a href="text-level-semantics.html#the-rt-element">rt</a></code> element, a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element, a
4259: <code><a href="tabular-data.html#the-td-element">td</a></code> element, a <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element, a
4260: <code><a href="tabular-data.html#the-th-element">th</a></code> element, a <code><a href="tabular-data.html#the-thead-element">thead</a></code> element, a
1.159 mike 4261: <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, the <code><a href="semantics.html#the-body-element-0">body</a></code> element, or the
4262: <code><a href="semantics.html#the-html-element-0">html</a></code> element, then this is a <a href="#parse-error">parse
1.1 mike 4263: error</a>.</p> <!-- (some of those are fragment cases, e.g. for
4264: <tbody> you'd have hit the first paragraph since the <body>
4265: wouldn't be in scope, unless it was a fragment case) -->
4266:
4267: <!-- If we ever change the frameset-ok flag to an insertion mode,
4268: then we'd have to somehow keep track of its state when we switch
4269: to after-body. -->
4270:
4271: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-afterbody" title="insertion mode: after body">after body</a>".</p>
4272:
4273: </dd>
4274:
4275: <dt>An end tag whose tag name is "html"</dt>
4276: <dd>
4277:
4278: <p>Act as if an end tag with tag name "body" had been seen,
4279: then, if that token wasn't ignored, reprocess the current
4280: token.</p>
4281:
4282: <p class="note">The fake end tag token here can only be
4283: ignored in the <a href="#fragment-case">fragment case</a>.</p>
4284:
4285: </dd>
4286:
4287: <!-- start tags for non-phrasing flow content elements -->
4288:
4289: <!-- the normal ones -->
4290: <dt>A start tag whose tag name is one of: "address", "article",
1.86 mike 4291: "aside", "blockquote", "center", <!--v2DATAGRID-->"datagrid",
4292: "details", "dialog", "dir", "div", "dl", "fieldset", "figure",
4293: "footer", "header", "hgroup", "menu", "nav", "ol", "p", "section",
4294: "ul"</dt>
1.1 mike 4295: <dd>
4296:
4297: <!-- As of May 2008 this doesn't match any browser exactly, but is
4298: as close to what IE does as I can get without doing the non-tree
4299: DOM nonsense, and thus should actually afford better compatibility
4300: when implemented by the other browsers. -->
4301:
4302: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4303: an element in scope">has a <code>p</code> element in
4304: scope</a>, then act as if an end tag with the tag name
4305: "p" had been seen.</p>
4306:
4307: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4308:
4309: </dd>
4310:
4311: <!-- as normal, but close h1-h6 if it's the current node -->
4312: <dt>A start tag whose tag name is one of: "h1", "h2", "h3", "h4",
4313: "h5", "h6"</dt>
4314: <dd>
4315:
4316: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4317: an element in scope">has a <code>p</code> element in
4318: scope</a>, then act as if an end tag with the tag name
4319: "p" had been seen.</p>
4320:
4321: <p>If the <a href="#current-node">current node</a> is an element whose tag name
4322: is one of "h1", "h2", "h3", "h4", "h5", or "h6", then this is a
4323: <a href="#parse-error">parse error</a>; pop the <a href="#current-node">current node</a> off
4324: the <a href="#stack-of-open-elements">stack of open elements</a>.</p>
4325: <!-- See https://bugs.webkit.org/show_bug.cgi?id=12646 -->
4326:
4327: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4328:
4329: </dd>
4330:
4331: <!-- as normal, but drops leading newline -->
4332: <dt>A start tag whose tag name is one of: "pre", "listing"</dt>
4333: <dd>
4334:
4335: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4336: an element in scope">has a <code>p</code> element in
4337: scope</a>, then act as if an end tag with the tag name
4338: "p" had been seen.</p>
4339:
4340: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4341:
4342: <p>If the next token is a U+000A LINE FEED (LF) character
4343: token, then ignore that token and move on to the next
4344: one. (Newlines at the start of <code><a href="semantics.html#the-pre-element">pre</a></code> blocks are
4345: ignored as an authoring convenience.)</p>
4346:
4347: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4348:
4349: </dd>
4350:
4351: <!-- as normal, but interacts with the form element pointer -->
4352: <dt>A start tag whose tag name is "form"</dt>
4353: <dd>
4354:
4355: <p>If the <a href="#form-element-pointer"><code title="form">form</code> element
4356: pointer</a> is not null, then this is a <a href="#parse-error">parse
4357: error</a>; ignore the token.</p>
4358:
4359: <p>Otherwise:</p>
4360:
4361: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4362: an element in scope">has a <code>p</code> element in
4363: scope</a>, then act as if an end tag with the tag name
4364: "p" had been seen.</p>
4365:
4366: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, and set the
4367: <a href="#form-element-pointer"><code title="form">form</code> element pointer</a> to
4368: point to the element created.</p>
4369:
4370: </dd>
4371:
4372: <!-- as normal, but imply </li> when there's another <li> open in weird cases -->
4373: <dt>A start tag whose tag name is "li"</dt>
4374: <dd>
4375:
4376: <p>Run the following algorithm:</p>
4377:
4378: <ol><li><p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p></li>
4379:
4380: <li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
4381: node</a> (the bottommost node of the stack).</p></li>
4382:
4383: <li><p>If <var title="">node</var> is an <code><a href="semantics.html#the-li-element">li</a></code> element,
4384: then act as if an end tag with the tag name "li" had
4385: been seen, then jump to the last step.</p></li>
4386:
4387: <li><p><i>Loop</i>: If <var title="">node</var> is not in the
4388: <a href="#formatting">formatting</a> category, and is not in the
4389: <a href="#phrasing">phrasing</a> category, and is not an
4390: <code><a href="semantics.html#the-address-element">address</a></code>, <code><a href="interactive-elements.html#the-div-element">div</a></code>, or <code><a href="semantics.html#the-p-element">p</a></code>
4391: element, then jump to the last step.</p></li> <!-- an element
4392: <foo> is in this list if the following markup:
4393:
4394: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><body><ol><li><foo><li>
4395:
4396: ...results in the second <li> not being (in any way) a descendant
4397: of the first <li>, or if <foo> is a formatting element that gets
4398: reopened later. -->
4399:
4400: <li><p>Otherwise, set <var title="">node</var> to the previous
4401: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to
4402: the step labeled <i>loop</i>.</p></li>
4403:
4404: <li>
4405:
4406: <p>This is the last step.</p>
4407:
4408: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4409: an element in scope">has a <code>p</code> element in
4410: scope</a>, then act as if an end tag with the tag name
4411: "p" had been seen.</p>
4412:
4413: <p>Finally, <a href="#insert-an-html-element">insert an HTML element</a> for the
4414: token.</p>
4415:
4416: </li>
4417:
4418: </ol></dd>
4419:
4420: <!-- as normal, but imply </dt> or </dd> when there's another <dt> or <dd> open in weird cases -->
4421: <dt>A start tag whose tag name is one of: "dd", "dt"</dt>
4422: <dd>
4423:
4424: <p>Run the following algorithm:</p>
4425:
4426: <ol><li><p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p></li>
4427:
4428: <li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
4429: node</a> (the bottommost node of the stack).</p></li>
4430:
4431: <li><p><i>Loop</i>: If <var title="">node</var> is a
4432: <code><a href="semantics.html#the-dd-element">dd</a></code> or <code><a href="semantics.html#the-dt-element">dt</a></code> element, then act as if an end
4433: tag with the same tag name as <var title="">node</var> had been
4434: seen, then jump to the last step.</p></li>
4435:
4436: <li><p>If <var title="">node</var> is not in the
4437: <a href="#formatting">formatting</a> category, and is not in the
4438: <a href="#phrasing">phrasing</a> category, and is not an
4439: <code><a href="semantics.html#the-address-element">address</a></code>, <code><a href="interactive-elements.html#the-div-element">div</a></code>, or <code><a href="semantics.html#the-p-element">p</a></code>
4440: element, then jump to the last step.</p></li> <!-- an element
4441: <foo> is in this list if the following markup:
4442:
4443: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><body><dl><dt><foo><dt>
4444:
4445: ...results in the second <dt> not being (in any way) a descendant
4446: of the first <dt>, or if <foo> is a formatting element that gets
4447: reopened later. -->
4448:
4449: <li><p>Otherwise, set <var title="">node</var> to the previous
4450: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to
4451: the step labeled <i>loop</i>.</p></li>
4452:
4453: <li>
4454:
4455: <p>This is the last step.</p>
4456:
4457: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4458: an element in scope">has a <code>p</code> element in
4459: scope</a>, then act as if an end tag with the tag name
4460: "p" had been seen.</p>
4461:
4462: <p>Finally, <a href="#insert-an-html-element">insert an HTML element</a> for the
4463: token.</p>
4464:
4465: </li>
4466:
4467: </ol></dd>
4468:
4469: <!-- same as normal, but effectively ends parsing -->
4470: <dt>A start tag whose tag name is "plaintext"</dt>
4471: <dd>
4472:
4473: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4474: an element in scope">has a <code>p</code> element in
4475: scope</a>, then act as if an end tag with the tag name
4476: "p" had been seen.</p>
4477:
4478: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4479:
4480: <p>Switch the <a href="#content-model-flag">content model flag</a> to the PLAINTEXT
4481: state.</p>
4482:
4483: <p class="note">Once a start tag with the tag name "plaintext"
4484: has been seen, that will be the last token ever seen other
4485: than character tokens (and the end-of-file token), because
4486: there is no way to switch the <a href="#content-model-flag">content model flag</a>
4487: out of the PLAINTEXT state.</p>
4488:
4489: </dd>
4490:
4491: <!-- end tags for non-phrasing flow content elements -->
4492:
4493: <!-- the normal ones -->
4494: <dt>An end tag whose tag name is one of: "address", "article",
1.86 mike 4495: "aside", "blockquote", "center", <!--v2DATAGRID-->"datagrid",
4496: "details", "dialog", "dir", "div", "dl", "fieldset", "figure",
4497: "footer", "header", "hgroup", "listing", "menu", "nav", "ol",
4498: "pre", "section", "ul"</dt>
1.1 mike 4499: <dd>
4500:
4501: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-scope" title="has an element in scope">have an element in scope</a>
4502: with the same tag name as that of the token, then this is a
4503: <a href="#parse-error">parse error</a>; ignore the token.</p>
4504:
4505: <p>Otherwise, run these steps:</p>
4506:
4507: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4508:
4509: <li><p>If the <a href="#current-node">current node</a> is not an element with
4510: the same tag name as that of the token, then this is a
4511: <a href="#parse-error">parse error</a>.</p></li>
4512:
4513: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4514: until an element with the same tag name as the token has been
4515: popped from the stack.</p></li>
4516:
4517: </ol></dd>
4518:
4519: <!-- removes the form element pointer instead of the matching node -->
4520: <dt>An end tag whose tag name is "form"</dt>
4521: <dd>
4522:
4523: <p>Let <var title="">node</var> be the element that the
4524: <a href="#form-element-pointer"><code title="">form</code> element pointer</a> is set
4525: to.</p>
4526:
4527: <p>Set the <a href="#form-element-pointer"><code title="">form</code> element pointer</a>
4528: to null.</p>
4529:
4530: <p>If <var title="">node</var> is null or the <a href="#stack-of-open-elements">stack of open
4531: elements</a> does not <a href="#has-an-element-in-scope" title="has an element in
4532: scope">have <var title="">node</var> in scope</a>, then this is
4533: a <a href="#parse-error">parse error</a>; ignore the token.</p>
4534:
4535: <p>Otherwise, run these steps:</p>
4536:
4537: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4538:
4539: <li><p>If the <a href="#current-node">current node</a> is not <var title="">node</var>, then this is a <a href="#parse-error">parse
4540: error</a>.</p></li>
4541:
4542: <li><p>Remove <var title="">node</var> from the <a href="#stack-of-open-elements">stack of
4543: open elements</a>.</p></li>
4544:
4545: </ol></dd>
4546:
4547: <!-- as normal, except </p> implies <p> if there's no <p> in scope, and needs care as the elements have optional tags -->
4548: <dt>An end tag whose tag name is "p"</dt>
4549: <dd>
4550:
4551: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-scope" title="has an element in scope">have an element in scope</a>
4552: with the same tag name as that of the token, then this is a
4553: <a href="#parse-error">parse error</a>; act as if a start tag with the tag name
4554: "p" had been seen, then reprocess the current token.</p>
4555:
4556: <p>Otherwise, run these steps:</p>
4557:
4558: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>, except
4559: for elements with the same tag name as the token.</p></li>
4560:
4561: <li><p>If the <a href="#current-node">current node</a> is not an element with
4562: the same tag name as that of the token, then this is a
4563: <a href="#parse-error">parse error</a>.</p></li>
4564:
4565: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4566: until an element with the same tag name as the token has been
4567: popped from the stack.</p></li>
4568:
4569: </ol></dd>
4570:
4571: <!-- as normal, but needs care as the elements have optional tags -->
4572: <dt>An end tag whose tag name is one of: "dd", "dt", "li"</dt>
4573: <dd>
4574:
4575: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-scope" title="has an element in scope">have an element in scope</a>
4576: with the same tag name as that of the token, then this is a
4577: <a href="#parse-error">parse error</a>; ignore the token.</p>
4578:
4579: <p>Otherwise, run these steps:</p>
4580:
4581: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>, except
4582: for elements with the same tag name as the token.</p></li>
4583:
4584: <li><p>If the <a href="#current-node">current node</a> is not an element with
4585: the same tag name as that of the token, then this is a
4586: <a href="#parse-error">parse error</a>.</p></li>
4587:
4588: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4589: until an element with the same tag name as the token has been
4590: popped from the stack.</p></li>
4591:
4592: </ol></dd>
4593:
4594: <!-- as normal, except acts as a closer for any of the h1-h6 elements -->
4595: <dt>An end tag whose tag name is one of: "h1", "h2", "h3", "h4", "h5", "h6"</dt>
4596: <dd>
4597:
4598: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-scope" title="has an element in scope">have an element in scope</a>
4599: whose tag name is one of "h1", "h2", "h3", "h4", "h5", or "h6",
4600: then this is a <a href="#parse-error">parse error</a>; ignore the token.</p>
4601:
4602: <p>Otherwise, run these steps:</p>
4603:
4604: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4605:
4606: <li><p>If the <a href="#current-node">current node</a> is not an element with
4607: the same tag name as that of the token, then this is a
4608: <a href="#parse-error">parse error</a>.</p></li>
4609:
4610: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4611: until an element whose tag name is one of "h1", "h2", "h3", "h4",
4612: "h5", or "h6" has been popped from the stack.</p></li>
4613:
4614: </ol></dd>
4615:
4616: <dt>An end tag whose tag name is "sarcasm"</dt>
4617: <dd>
4618: <p>Take a deep breath, then act as described in the "any other end
4619: tag" entry below.</p>
4620: </dd>
4621:
4622: <!-- ADOPTION AGENCY ELEMENTS
4623: Mozilla-only: bdo blink del ins sub sup q
4624: Safari-only: code dfn kbd nobr samp var wbr
4625: Both: a b big em font i s small strike strong tt u -->
4626:
4627: <dt>A start tag whose tag name is "a"</dt>
4628: <dd>
4629:
4630: <p>If the <a href="#list-of-active-formatting-elements">list of active formatting elements</a>
4631: contains an element whose tag name is "a" between the end of
4632: the list and the last marker on the list (or the start of the
4633: list if there is no marker on the list), then this is a
4634: <a href="#parse-error">parse error</a>; act as if an end tag with the tag
4635: name "a" had been seen, then remove that element from the
4636: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> and the
4637: <a href="#stack-of-open-elements">stack of open elements</a> if the end tag didn't
4638: already remove it (it might not have if the element is not
4639: <a href="#has-an-element-in-table-scope" title="has an element in table scope">in table
4640: scope</a>).</p>
4641:
4642: <p class="example">In the non-conforming stream
4643: <code><a href="a">a<table><a href="b">b</table>x</code>,
4644: the first <code><a href="text-level-semantics.html#the-a-element">a</a></code> element would be closed upon seeing
4645: the second one, and the "x" character would be inside a link
4646: to "b", not to "a". This is despite the fact that the outer
4647: <code><a href="text-level-semantics.html#the-a-element">a</a></code> element is not in table scope (meaning that a
4648: regular <code></a></code> end tag at the start of the table
4649: wouldn't close the outer <code><a href="text-level-semantics.html#the-a-element">a</a></code> element).</p>
4650:
4651: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4652: any.</p>
4653:
4654: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Add that
4655: element to the <a href="#list-of-active-formatting-elements">list of active formatting
4656: elements</a>.</p>
4657:
4658: </dd>
4659:
4660: <dt>A start tag whose tag name is one of: "b", "big", "code", "em",
4661: "font", "i", "s", "small", "strike", "strong", "tt", "u"</dt>
4662: <dd>
4663:
4664: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4665: any.</p>
4666:
4667: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Add that
4668: element to the <a href="#list-of-active-formatting-elements">list of active formatting
4669: elements</a>.</p>
4670:
4671: </dd>
4672:
4673: <dt>A start tag whose tag name is "nobr"</dt>
4674: <dd>
4675:
4676: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4677: any.</p>
4678:
4679: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has an
4680: element in scope">has a <code>nobr</code> element in scope</a>,
4681: then this is a <a href="#parse-error">parse error</a>; act as if an end tag with
4682: the tag name "nobr" had been seen, then once again
4683: <a href="#reconstruct-the-active-formatting-elements">reconstruct the active formatting elements</a>, if
4684: any.</p>
4685:
4686: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Add that
4687: element to the <a href="#list-of-active-formatting-elements">list of active formatting
4688: elements</a>.</p>
4689:
4690: </dd>
4691:
4692: <dt id="adoptionAgency">An end tag whose tag name is one of: "a",
4693: "b", "big", "code", "em", "font", "i", "nobr", "s", "small",
4694: "strike", "strong", "tt", "u"</dt>
4695: <dd>
4696:
4697: <p>Follow these steps:</p>
4698:
4699: <ol><li>
4700:
4701: <p>Let the <var title="">formatting element</var> be the
4702: last element in the <a href="#list-of-active-formatting-elements">list of active formatting
4703: elements</a> that:</p>
4704:
4705: <ul><li>is between the end of the list and the last scope
4706: marker in the list, if any, or the start of the list
4707: otherwise, and</li>
4708:
4709: <li>has the same tag name as the token.</li>
4710:
4711: </ul><p>If there is no such node, or, if that node is also in the
4712: <a href="#stack-of-open-elements">stack of open elements</a> but the element is not <a href="#has-an-element-in-scope" title="has an element in scope">in scope</a>, then this is a
4713: <a href="#parse-error">parse error</a>; ignore the token, and abort these
4714: steps.</p>
4715:
4716: <p>Otherwise, if there is such a node, but that node is not
4717: in the <a href="#stack-of-open-elements">stack of open elements</a>, then this is a
4718: <a href="#parse-error">parse error</a>; remove the element from the list,
4719: and abort these steps.</p>
4720:
4721: <p>Otherwise, there is a <var title="">formatting
4722: element</var> and that element is in <a href="#stack-of-open-elements" title="stack of
4723: open elements">the stack</a> and is <a href="#has-an-element-in-scope" title="has an
4724: element in scope">in scope</a>. If the element is not the
4725: <a href="#current-node">current node</a>, this is a <a href="#parse-error">parse
4726: error</a>. In any case, proceed with the algorithm as
4727: written in the following steps.</p>
4728:
4729: </li>
4730:
4731: <li><p>Let the <var title="">furthest block</var> be the
4732: topmost node in the <a href="#stack-of-open-elements">stack of open elements</a> that
4733: is lower in the stack than the <var title="">formatting
4734: element</var>, and is not an element in the
4735: <a href="#phrasing">phrasing</a> or <a href="#formatting">formatting</a>
4736: categories. There might not be one.</p></li>
4737:
4738: <li><p>If there is no <var title="">furthest block</var>,
4739: then the UA must skip the subsequent steps and instead just
4740: pop all the nodes from the bottom of the <a href="#stack-of-open-elements">stack of open
4741: elements</a>, from the <a href="#current-node">current node</a> up to and
4742: including the <var title="">formatting element</var>, and
4743: remove the <var title="">formatting element</var> from the
4744: <a href="#list-of-active-formatting-elements">list of active formatting elements</a>.</p></li>
4745:
4746: <li><p>Let the <var title="">common ancestor</var> be the element
4747: immediately above the <var title="">formatting element</var> in the
4748: <a href="#stack-of-open-elements">stack of open elements</a>.</p></li>
4749:
4750: <li><p>Let a bookmark note the position of the <var title="">formatting element</var> in the <a href="#list-of-active-formatting-elements">list of active
4751: formatting elements</a> relative to the elements on either
4752: side of it in the list.</p></li>
4753:
4754: <li>
4755:
4756: <p>Let <var title="">node</var> and <var title="">last node</var> be the
4757: <var title="">furthest block</var>. Follow these steps:</p>
4758:
4759: <ol><li>Let <var title="">node</var> be the element immediately
4760: above <var title="">node</var> in the <a href="#stack-of-open-elements">stack of open
4761: elements</a>.</li>
4762:
4763: <li>If <var title="">node</var> is not in the <a href="#list-of-active-formatting-elements">list of
4764: active formatting elements</a>, then remove <var title="">node</var> from the <a href="#stack-of-open-elements">stack of open
4765: elements</a> and then go back to step 1.</li>
4766:
4767: <li>Otherwise, if <var title="">node</var> is the <var title="">formatting element</var>, then go to the next step
4768: in the overall algorithm.</li>
4769:
4770: <li>Otherwise, if <var title="">last node</var> is the <var title="">furthest block</var>, then move the aforementioned
4771: bookmark to be immediately after the <var title="">node</var> in the <a href="#list-of-active-formatting-elements">list of active formatting
4772: elements</a>.</li>
4773:
4774: <li><a href="#create-an-element-for-the-token">Create an element for the token</a> for which the
4775: element <var title="">node</var> was created, replace the entry
4776: for <var title="">node</var> in the <a href="#list-of-active-formatting-elements">list of active
4777: formatting elements</a> with an entry for the new element,
4778: replace the entry for <var title="">node</var> in the
4779: <a href="#stack-of-open-elements">stack of open elements</a> with an entry for the new
4780: element, and let <var title="">node</var> be the new
4781: element.</li>
4782:
4783: <li>Insert <var title="">last node</var> into <var title="">node</var>, first removing it from its previous
4784: parent node if any.</li>
4785:
4786: <li>Let <var title="">last node</var> be <var title="">node</var>.</li>
4787:
4788: <li>Return to step 1 of this inner set of steps.</li>
4789:
4790: </ol></li>
4791:
4792: <li>
4793:
4794: <p>If the <var title="">common ancestor</var> node is a
4795: <code><a href="tabular-data.html#the-table-element">table</a></code>, <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>, <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code>,
4796: <code><a href="tabular-data.html#the-thead-element">thead</a></code>, or <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, then,
4797: <a href="#foster-parent">foster parent</a> whatever <var title="">last
4798: node</var> ended up being in the previous step, first removing
4799: it from its previous parent node if any.</p>
4800:
4801: <p>Otherwise, append whatever <var title="">last node</var>
4802: ended up being in the previous step to the <var title="">common
4803: ancestor</var> node, first removing it from its previous parent
4804: node if any.</p>
4805:
4806: </li>
4807:
4808: <li><p><a href="#create-an-element-for-the-token">Create an element for the token</a> for which the
4809: <var title="">formatting element</var> was created.</p></li>
4810:
4811: <li><p>Take all of the child nodes of the <var title="">furthest
4812: block</var> and append them to the element created in the last
4813: step.</p></li>
4814:
4815: <li><p>Append that new element to the <var title="">furthest
4816: block</var>.</p></li>
4817:
4818: <li><p>Remove the <var title="">formatting element</var> from the
4819: <a href="#list-of-active-formatting-elements">list of active formatting elements</a>, and insert the
4820: new element into the <a href="#list-of-active-formatting-elements">list of active formatting
4821: elements</a> at the position of the aforementioned
4822: bookmark.</p></li>
4823:
4824: <li><p>Remove the <var title="">formatting element</var> from the
4825: <a href="#stack-of-open-elements">stack of open elements</a>, and insert the new element
4826: into the <a href="#stack-of-open-elements">stack of open elements</a> immediately below
4827: the position of the <var title="">furthest block</var> in that
4828: stack.</p></li>
4829:
4830: <li><p>Jump back to step 1 in this series of steps.</p></li>
4831:
4832: </ol><!--XXX
4833: <div class="example">
4834: <p class="XXX">Need an example.</p>
4835: </div>
4836: --><p class="note">Because of the way this algorithm causes elements to
4837: change parents, it has been dubbed the "adoption agency algorithm"
4838: (in contrast with other possibly algorithms for dealing with
4839: misnested content, which included the "incest algorithm", the
4840: "secret affair algorithm", and the "Heisenberg algorithm").</p>
4841:
4842: </dd>
4843:
4844: <dt>A start tag whose tag name is "button"</dt>
4845: <dd>
4846:
4847: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4848: an element in scope">has a <code>button</code> element in
4849: scope</a>, then this is a <a href="#parse-error">parse error</a>;
4850: act as if an end tag with the tag name "button" had been seen,
4851: then reprocess the token.</p>
4852:
4853: <p>Otherwise:</p>
4854:
4855: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4856: any.</p>
4857:
4858: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4859:
4860: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
4861: formatting elements</a>.</p>
4862:
4863: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4864:
4865: </dd>
4866:
4867: <dt>A start tag token whose tag name is one of: "applet",
4868: "marquee", "object"</dt>
4869: <dd>
4870:
4871: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4872: any.</p>
4873:
4874: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4875:
4876: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
4877: formatting elements</a>.</p>
4878:
4879: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4880:
4881: </dd>
4882:
4883: <dt>An end tag token whose tag name is one of: "applet", "button",
4884: "marquee", "object"</dt>
4885: <dd>
4886:
4887: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-scope" title="has an element in scope">have an element in scope</a>
4888: with the same tag name as that of the token, then this is a
4889: <a href="#parse-error">parse error</a>; ignore the token.</p>
4890:
4891: <p>Otherwise, run these steps:</p>
4892:
4893: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4894:
4895: <li><p>If the <a href="#current-node">current node</a> is not an element with
4896: the same tag name as that of the token, then this is a
4897: <a href="#parse-error">parse error</a>.</p></li>
4898:
4899: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4900: until an element with the same tag name as the token has been
4901: popped from the stack.</p></li>
4902:
4903: <li><a href="#clear-the-list-of-active-formatting-elements-up-to-the-last-marker">Clear the list of active formatting elements up to the
4904: last marker</a>.</li>
4905:
4906: </ol></dd>
4907:
4908: <dt>A start tag whose tag name is "table"</dt>
4909: <dd>
4910:
4911: <p>If the <code>Document</code> is <em>not</em> set to
4912: <a href="dom.html#quirks-mode">quirks mode</a>, and the <a href="#stack-of-open-elements">stack of open
4913: elements</a> <a href="#has-an-element-in-scope" title="has an element in scope">has a
4914: <code>p</code> element in scope</a>, then act as if an end tag
4915: with the tag name "p" had been seen.</p> <!-- i hate myself (this
4916: quirk was basically caused by acid2; if i'd realised we could
4917: change the specs when i wrote acid2, we could have avoided having
4918: any parsing-mode quirks) -Hixie -->
4919:
4920: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4921:
4922: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4923:
4924: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>".</p>
4925:
4926: </dd>
4927:
4928: <dt>A start tag whose tag name is one of: "area", "basefont",
4929: "bgsound", "br", "embed", "img", "input", "keygen", "spacer",
4930: "wbr"</dt>
4931: <dd>
4932:
4933: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4934: any.</p>
4935:
4936: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
4937: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
4938: elements</a>.</p>
4939:
4940: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
4941: token's <i>self-closing flag</i></a>, if it is set.</p>
4942:
4943: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p> <!--
4944: shouldn't really do it for <area>, <basefont>, <bgsound>, and
4945: <spacer> -->
4946:
4947: </dd>
4948:
4949: <dt>A start tag whose tag name is one of: "param", "source"</dt>
4950: <dd>
4951:
4952: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
4953: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
4954: elements</a>.</p>
4955:
4956: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
4957: token's <i>self-closing flag</i></a>, if it is set.</p>
4958:
4959: </dd>
4960:
4961: <dt>A start tag whose tag name is "hr"</dt>
4962: <dd>
4963:
4964: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4965: an element in scope">has a <code>p</code> element in
4966: scope</a>, then act as if an end tag with the tag name
4967: "p" had been seen.</p>
4968:
4969: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
4970: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
4971: elements</a>.</p>
4972:
4973: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
4974: token's <i>self-closing flag</i></a>, if it is set.</p>
4975:
4976: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4977:
4978: </dd>
4979:
4980: <dt>A start tag whose tag name is "image"</dt>
4981: <dd>
4982: <p><a href="#parse-error">Parse error</a>. Change the token's tag name
4983: to "img" and reprocess it. (Don't ask.)</p> <!-- As of
4984: 2005-12, studies showed that around 0.2% of pages used the
4985: <image> element. -->
4986: </dd>
4987:
4988: <dt id="isindex">A start tag whose tag name is "isindex"</dt>
4989: <dd>
4990:
4991: <p><a href="#parse-error">Parse error</a>.</p>
4992:
4993: <p>If the <a href="#form-element-pointer"><code title="">form</code> element
4994: pointer</a> is not null, then ignore the token.</p>
4995:
4996: <p>Otherwise:</p>
4997:
4998: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
4999: token's <i>self-closing flag</i></a>, if it is set.</p> <!--
5000: purely to reduce the number of errors (we don't care if they
5001: included the /, they're not supposed to be including the tag at
5002: all! -->
5003:
5004: <p>Act as if a start tag token with the tag name "form" had been seen.</p>
5005:
5006: <p>If the token has an attribute called "action", set the
5007: <code title="attr-form-action">action</code> attribute on the
5008: resulting <code><a href="forms.html#the-form-element">form</a></code> element to the value of the
5009: "action" attribute of the token.</p>
5010:
5011: <p>Act as if a start tag token with the tag name "hr" had been
5012: seen.</p>
5013:
5014: <p>Act as if a start tag token with the tag name "label" had been
5015: seen.</p>
5016:
5017: <p>Act as if a stream of character tokens had been seen (see below
5018: for what they should say).</p>
5019:
5020: <p>Act as if a start tag token with the tag name "input" had been
5021: seen, with all the attributes from the "isindex" token except
5022: "name", "action", and "prompt". Set the <code title="attr-fe-name"><a href="forms.html#attr-fe-name">name</a></code> attribute of the resulting
5023: <code><a href="forms.html#the-input-element">input</a></code> element to the value "<code title="">isindex</code>".</p>
5024:
5025: <p>Act as if a stream of character tokens had been seen (see
5026: below for what they should say).</p>
5027:
5028: <p>Act as if an end tag token with the tag name "label" had been
5029: seen.</p>
5030:
5031: <p>Act as if a start tag token with the tag name "hr" had been
5032: seen.</p>
5033:
5034: <p>Act as if an end tag token with the tag name "form" had been
5035: seen.</p>
5036:
5037: <p>If the token has an attribute with the name "prompt", then the
5038: first stream of characters must be the same string as given in
5039: that attribute, and the second stream of characters must be
5040: empty. Otherwise, the two streams of character tokens together
5041: should, together with the <code><a href="forms.html#the-input-element">input</a></code> element, express the
5042: equivalent of "This is a searchable index. Insert your search
5043: keywords here: (input field)" in the user's preferred
5044: language.</p>
5045:
5046: </dd>
5047:
5048: <dt>A start tag whose tag name is "textarea"</dt>
5049: <dd>
5050:
5051: <ol><li><p><a href="#insert-an-html-element">Insert an HTML element</a> for the
5052: token.</p></li>
5053:
5054: <li><p>If the next token is a U+000A LINE FEED (LF) character
5055: token, then ignore that token and move on to the next
5056: one. (Newlines at the start of <code><a href="forms.html#the-textarea-element">textarea</a></code> elements are
5057: ignored as an authoring convenience.)</p></li>
5058:
5059: <li><p>Switch the tokenizer's <a href="#content-model-flag">content model flag</a> to
5060: the RCDATA state.</p></li>
5061:
5062: <li><p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the
5063: current <a href="#insertion-mode">insertion mode</a>.</p>
5064:
5065: </li><li><p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not
5066: ok".</p></li>
5067:
1.91 mike 5068: <li><p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incdata" title="insertion mode: in RAWTEXT/RCDATA">in
5069: RAWTEXT/RCDATA</a>".</p></li>
1.1 mike 5070:
5071: </ol></dd>
5072:
5073: <dt>A start tag whose tag name is "xmp"</dt>
5074: <dd>
5075:
5076: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5077: any.</p>
5078:
5079: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
5080:
1.91 mike 5081: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 5082:
5083: </dd>
5084:
5085: <dt>A start tag whose tag name is "iframe"</dt>
5086: <dd>
5087:
5088: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
5089:
1.91 mike 5090: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 5091:
5092: </dd>
5093:
5094: <dt>A start tag whose tag name is "noembed"</dt>
5095: <dt>A start tag whose tag name is "noscript", if the <a href="#scripting-flag">scripting flag</a> is enabled</dt>
5096: <dd>
5097:
1.91 mike 5098: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 5099:
5100: </dd>
5101:
5102: <dt>A start tag whose tag name is "select"</dt>
5103: <dd>
5104:
5105: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5106: any.</p>
5107:
5108: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5109:
5110: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
5111:
5112: <p>If the <a href="#insertion-mode">insertion mode</a> is one of <a href="#parsing-main-intable" title="insertion mode: in table">in table</a>", "<a href="#parsing-main-incaption" title="insertion mode: in caption">in caption</a>", "<a href="#parsing-main-incolgroup" title="insertion mode: in column group">in column group</a>",
5113: "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
5114: body</a>", "<a href="#parsing-main-intr" title="insertion mode: in row">in
5115: row</a>", or "<a href="#parsing-main-intd" title="insertion mode: in cell">in
5116: cell</a>", then switch the <a href="#insertion-mode">insertion mode</a> to
5117: "<a href="#parsing-main-inselectintable" title="insertion mode: in select in table">in select in
5118: table</a>". Otherwise, switch the <a href="#insertion-mode">insertion mode</a>
5119: to "<a href="#parsing-main-inselect" title="insertion mode: in select">in select</a>".</p>
5120:
5121: </dd>
5122:
5123: <dt>A start tag whose tag name is one of: "optgroup", "option"</dt>
5124: <dd>
5125:
5126: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has an
5127: element in scope">has an <code>option</code> element in
5128: scope</a>, then act as if an end tag with the tag name "option"
5129: had been seen.</p>
5130:
5131: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5132: any.</p>
5133:
5134: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5135:
5136: </dd>
5137:
5138: <dt>A start tag whose tag name is one of: "rp", "rt"</dt>
5139: <dd>
5140:
5141: <!-- the parsing rules for ruby really don't match IE much at all,
5142: but in practice the markup used is very simple and so strict
5143: compatibility with IE isn't required. For example, as defined
5144: here we get very, very different behaviour than IE for
5145: pathological cases like:
5146:
5147: <ruby><ol><li><p>a<rt>b
5148: <ruby>a<rt>b<p>c
5149:
5150: But in practice most ruby markup falls into these cases:
5151:
5152: <ruby>a<rt>b</ruby>
5153: <ruby>a<rp>b<rt>c<rp>d</ruby>
5154: <ruby>a<rt>b</rt></ruby>
5155: <ruby>a<rp>b</rp><rt>c</rt><rp>d</rp></ruby>
5156:
5157: -->
5158:
5159: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has an
5160: element in scope">has a <code>ruby</code> element in scope</a>,
5161: then <a href="#generate-implied-end-tags">generate implied end tags</a>. If the <a href="#current-node">current
5162: node</a> is not then a <code><a href="text-level-semantics.html#the-ruby-element">ruby</a></code> element, this is a
5163: <a href="#parse-error">parse error</a>; pop all the nodes from the <a href="#current-node">current
5164: node</a> up to the node immediately before the bottommost
5165: <code><a href="text-level-semantics.html#the-ruby-element">ruby</a></code> element on the <a href="#stack-of-open-elements">stack of open
5166: elements</a>.</p>
5167:
5168: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5169:
5170: </dd>
5171:
5172: <dt>An end tag whose tag name is "br"</dt>
5173: <dd>
5174: <p><a href="#parse-error">Parse error</a>. Act as if a start tag token with
5175: the tag name "br" had been seen. Ignore the end tag token.</p>
5176: </dd>
5177:
5178: <dt>A start tag whose tag name is "math"</dt>
5179: <dd>
5180:
5181: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5182: any.</p>
5183:
5184: <p><a href="#adjust-mathml-attributes">Adjust MathML attributes</a> for the token. (This
5185: fixes the case of MathML attributes that are not all
5186: lowercase.)</p>
5187:
5188: <p><a href="#adjust-foreign-attributes">Adjust foreign attributes</a> for the token. (This
5189: fixes the use of namespaced attributes, in particular XLink.)</p>
5190:
5191: <p><a href="#insert-a-foreign-element">Insert a foreign element</a> for the token, in the
5192: <a href="#mathml-namespace">MathML namespace</a>.</p>
5193:
5194: <!-- If we ever change the frameset-ok flag to an insertion mode,
5195: the following change would be implied, except we'd have to do it
5196: even in the face of a self-closed tag:
5197: <p>Set the <span>frameset-ok flag</span> to "not ok".</p>
5198: -->
5199:
5200: <p>If the token has its <i>self-closing flag</i> set, pop the
5201: <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5202: elements</a> and <a href="#acknowledge-self-closing-flag" title="acknowledge self-closing
5203: flag">acknowledge the token's <i>self-closing flag</i></a>.</p>
5204:
5205: <p>Otherwise, if the <a href="#insertion-mode">insertion mode</a> is not already
5206: "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in foreign
5207: content</a>", let the <a href="#secondary-insertion-mode">secondary insertion mode</a> be
5208: the current <a href="#insertion-mode">insertion mode</a>, and then switch the
5209: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inforeign" title="insertion mode: in
5210: foreign content">in foreign content</a>".</p>
5211:
5212: </dd>
5213:
5214: <dt>A start tag whose tag name is "svg"</dt>
5215: <dd>
5216:
5217: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5218: any.</p>
5219:
5220: <p><a href="#adjust-svg-attributes">Adjust SVG attributes</a> for the token. (This fixes
5221: the case of SVG attributes that are not all lowercase.)</p>
5222:
5223: <p><a href="#adjust-foreign-attributes">Adjust foreign attributes</a> for the token. (This
5224: fixes the use of namespaced attributes, in particular XLink in
5225: SVG.)</p>
5226:
5227: <p><a href="#insert-a-foreign-element">Insert a foreign element</a> for the token, in the
5228: <a href="#svg-namespace">SVG namespace</a>.</p>
5229:
5230: <!-- If we ever change the frameset-ok flag to an insertion mode,
5231: the following change would be implied, except we'd have to do it
5232: even in the face of a self-closed tag:
5233: <p>Set the <span>frameset-ok flag</span> to "not ok".</p>
5234: -->
5235:
5236: <p>If the token has its <i>self-closing flag</i> set, pop the
5237: <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5238: elements</a> and <a href="#acknowledge-self-closing-flag" title="acknowledge self-closing
5239: flag">acknowledge the token's <i>self-closing flag</i></a>.</p>
5240:
5241: <p>Otherwise, if the <a href="#insertion-mode">insertion mode</a> is not already
5242: "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in foreign
5243: content</a>", let the <a href="#secondary-insertion-mode">secondary insertion mode</a> be
5244: the current <a href="#insertion-mode">insertion mode</a>, and then switch the
5245: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inforeign" title="insertion mode: in
5246: foreign content">in foreign content</a>".</p>
5247:
5248: </dd>
5249:
5250: <dt>A start <!--or end--> tag whose tag name is one of: "caption",
5251: "col", "colgroup", "frame", "head", "tbody", "td", "tfoot", "th",
5252: "thead", "tr"</dt>
5253: <!--<dt>An end tag whose tag name is one of: "area", "base",
5254: "basefont", "bgsound", "command", "embed", "hr", "iframe", "image",
5255: "img", "input", "isindex", "keygen", "link", "meta", "noembed",
5256: "noframes", "param", "script", "select", "source", "spacer",
5257: "style", "table", "textarea", "title", "wbr"</dt>-->
5258: <!--<dt>An end tag whose tag name is "noscript", if the
5259: <span>scripting flag</span> is enabled</dt>-->
5260: <dd>
5261: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5262: <!-- end tags are commented out because since they can never end
5263: up on the stack anyway, the default end tag clause will
5264: automatically handle them. we don't want to have text in the spec
5265: that is just an optimisation, as that detracts from the spec
5266: itself -->
5267: </dd>
5268:
5269: <dt>Any other start tag</dt>
5270: <dd>
5271:
5272: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5273: any.</p>
5274:
5275: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5276:
5277: <p class="note">This element will be a <a href="#phrasing">phrasing</a>
5278: element.</p>
5279:
5280: </dd>
5281:
5282: <dt>Any other end tag</dt>
5283: <dd>
5284:
5285: <p>Run the following steps:</p>
5286:
5287: <ol><li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
5288: node</a> (the bottommost node of the stack).</p></li>
5289:
5290: <li><p>If <var title="">node</var> has the same tag name as
5291: the end tag token, then:</p>
5292:
5293: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
5294:
5295: <li><p>If the tag name of the end tag token does not match
5296: the tag name of the <a href="#current-node">current node</a>, this is a
5297: <a href="#parse-error">parse error</a>.</p></li>
5298:
5299: <li><p>Pop all the nodes from the <a href="#current-node">current node</a> up
5300: to <var title="">node</var>, including <var title="">node</var>, then stop these steps.</p></li>
5301:
5302: </ol></li>
5303:
5304: <li><p>Otherwise, if <var title="">node</var> is in neither the
5305: <a href="#formatting">formatting</a> category nor the <a href="#phrasing">phrasing</a>
5306: category, then this is a <a href="#parse-error">parse error</a>; ignore the
5307: token, and abort these steps.</p></li>
5308:
5309: <li><p>Set <var title="">node</var> to the previous entry in the
5310: <a href="#stack-of-open-elements">stack of open elements</a>.</p></li>
5311:
5312: <li><p>Return to step 2.</p></li>
5313:
5314: </ol></dd>
5315:
1.91 mike 5316: </dl><h5 id="parsing-main-incdata"><span class="secno">9.2.5.11 </span>The "<dfn title="insertion mode: in RAWTEXT/RCDATA">in RAWTEXT/RCDATA</dfn>" insertion mode</h5>
1.1 mike 5317:
5318: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-incdata" title="insertion
1.91 mike 5319: mode: in RAWTEXT/RCDATA">in RAWTEXT/RCDATA</a>", tokens must be
1.1 mike 5320: handled as follows:</p>
5321:
5322: <dl class="switch"><dt>A character token</dt>
5323: <dd>
5324:
5325: <p><a href="#insert-a-character" title="insert a character">Insert the token's
5326: character</a> into the <a href="#current-node">current node</a>.</p>
5327:
5328: </dd>
5329:
5330: <dt>An end-of-file token</dt>
5331: <dd>
5332:
5333: <!-- can't be the fragment case -->
5334: <p><a href="#parse-error">Parse error</a>.</p>
5335:
5336: <p>If the <a href="#current-node">current node</a> is a <code><a href="semantics.html#script">script</a></code>
5337: element, mark the <code><a href="semantics.html#script">script</a></code> element as <a href="semantics.html#already-executed">"already
5338: executed"</a>.</p>
5339:
5340: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5341: elements</a>.</p>
5342:
5343: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5344: insertion mode</a> and reprocess the current token.</p>
5345:
5346: </dd>
5347:
5348: <dt>An end tag whose tag name is "script"</dt>
5349: <dd>
5350:
5351: <p>Let <var title="">script</var> be the <a href="#current-node">current node</a>
5352: (which will be a <code><a href="semantics.html#script">script</a></code> element).</p>
5353:
5354: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5355: elements</a>.</p>
5356:
5357: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5358: insertion mode</a>.</p>
5359:
5360: <p>Let the <var title="">old insertion point</var> have the
5361: same value as the current <a href="#insertion-point">insertion point</a>. Let
5362: the <a href="#insertion-point">insertion point</a> be just before the <a href="#next-input-character">next
5363: input character</a>.</p>
5364:
5365: <p>Increment the parser's <a href="#script-nesting-level">script nesting level</a> by
5366: one.</p>
5367:
5368: <p><a href="semantics.html#running-a-script" title="running a script">Run</a> the <var title="">script</var>. This might cause some script to execute,
1.159 mike 5369: which might cause <a href="embedded-content-0.html#dom-document-write" title="dom-document-write">new characters
1.1 mike 5370: to be inserted into the tokenizer</a>, and might cause the
5371: tokenizer to output more tokens, resulting in a <a href="#nestedParsing">reentrant invocation of the parser</a>.</p>
5372:
5373: <p>Decrement the parser's <a href="#script-nesting-level">script nesting level</a> by
5374: one. If the parser's <a href="#script-nesting-level">script nesting level</a> is zero,
5375: then set the <a href="#parser-pause-flag">parser pause flag</a> to false.</p>
5376:
5377: <p>Let the <a href="#insertion-point">insertion point</a> have the value of the <var title="">old insertion point</var>. (In other words, restore the
5378: <a href="#insertion-point">insertion point</a> to its previous value. This value
5379: might be the "undefined" value.)</p>
5380:
5381: <p id="scriptTagParserResumes">At this stage, if there is a
5382: <a href="semantics.html#pending-external-script">pending external script</a>, then:</p>
5383:
5384: <dl class="switch"><dt>If the <a href="#script-nesting-level">script nesting level</a> is not zero:</dt>
5385:
5386: <dd>
5387:
5388: <p>Set the <a href="#parser-pause-flag">parser pause flag</a> to true, and abort the
5389: processing of any nested invocations of the tokenizer, yielding
5390: control back to the caller. (Tokenization will resume when the
5391: caller returns to the "outer" tree construction stage.)</p>
5392:
5393: <p class="note">The tree construction stage of this particular
5394: parser is <a href="#nestedParsing">being called reentrantly</a>,
1.159 mike 5395: say from a call to <code title="dom-document-write"><a href="embedded-content-0.html#dom-document-write">document.write()</a></code>.</p>
1.1 mike 5396:
5397: </dd>
5398:
5399:
5400: <dt>Otherwise:</dt>
5401:
5402: <dd>
5403:
5404: <p>Follow these steps:</p>
5405:
5406: <ol><li><p>Let <var title="">the script</var> be the <a href="semantics.html#pending-external-script">pending
5407: external script</a>. There is no longer a <a href="semantics.html#pending-external-script">pending
5408: external script</a>.</p></li>
5409:
5410: <li><p><a href="browsers.html#pause">Pause</a> until the script has <a href="semantics.html#completed-loading">completed
5411: loading</a>.</p></li>
5412:
5413: <li><p>Let the <a href="#insertion-point">insertion point</a> be just before the
5414: <a href="#next-input-character">next input character</a>.</p></li>
5415:
5416: <li><p>Increment the parser's <a href="#script-nesting-level">script nesting level</a>
5417: by one (it should be zero before this step, so this sets it to
5418: one).</p></li>
5419:
5420: <li><p><a href="semantics.html#executing-a-script-block" title="executing a script block">Execute the
5421: script</a>.</p></li>
5422:
5423: <li><p>Decrement the parser's <a href="#script-nesting-level">script nesting level</a>
5424: by one. If the parser's <a href="#script-nesting-level">script nesting level</a> is
5425: zero (which it always should be at this point), then set the
5426: <a href="#parser-pause-flag">parser pause flag</a> to false.</p>
5427:
5428: </li><li><p>Let the <a href="#insertion-point">insertion point</a> be undefined
5429: again.</p></li>
5430:
5431: <li><p>If there is once again a <a href="semantics.html#pending-external-script">pending external
5432: script</a>, then repeat these steps from step 1.</p></li>
5433:
5434: </ol></dd>
5435:
5436: </dl></dd>
5437:
5438: <dt>Any other end tag</dt>
5439: <dd>
5440:
5441: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5442: elements</a>.</p>
5443:
5444: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5445: insertion mode</a>.</p>
5446:
5447: </dd>
5448:
5449: </dl><h5 id="parsing-main-intable"><span class="secno">9.2.5.12 </span>The "<dfn title="insertion mode: in table">in table</dfn>" insertion mode</h5>
5450:
5451: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intable" title="insertion
5452: mode: in table">in table</a>", tokens must be handled as follows:</p>
5453:
5454: <dl class="switch"><dt>A character token</dt>
5455: <dd>
5456:
5457: <p>Let the <dfn id="pending-table-character-tokens"><var>pending table character tokens</var></dfn>
5458: be an empty list of tokens.</p>
5459:
5460: <p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the current
5461: <a href="#insertion-mode">insertion mode</a>.</p>
5462:
5463: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intabletext" title="insertion mode: in table text">in table text</a>" and
5464: reprocess the token.</p>
5465:
5466: </dd>
5467:
5468: <dt>A comment token</dt>
5469: <dd>
5470: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
5471: node</a> with the <code title="">data</code> attribute set to
5472: the data given in the comment token.</p>
5473: </dd>
5474:
5475: <dt>A DOCTYPE token</dt>
5476: <dd>
5477: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5478: </dd>
5479:
5480: <dt>A start tag whose tag name is "caption"</dt>
5481: <dd>
5482:
5483: <p><a href="#clear-the-stack-back-to-a-table-context">Clear the stack back to a table context</a>. (See
5484: below.)</p>
5485:
5486: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
5487: formatting elements</a>.</p>
5488:
5489: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then
5490: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incaption" title="insertion mode: in caption">in caption</a>".</p>
5491:
5492: </dd>
5493:
5494: <dt>A start tag whose tag name is "colgroup"</dt>
5495: <dd>
5496:
5497: <p><a href="#clear-the-stack-back-to-a-table-context">Clear the stack back to a table context</a>. (See
5498: below.)</p>
5499:
5500: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then
5501: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incolgroup" title="insertion mode: in column group">in column
5502: group</a>".</p>
5503:
5504: </dd>
5505:
5506: <dt>A start tag whose tag name is "col"</dt>
5507: <dd>
5508: <p>Act as if a start tag token with the tag name "colgroup"
5509: had been seen, then reprocess the current token.</p>
5510: </dd>
5511:
5512: <dt>A start tag whose tag name is one of: "tbody", "tfoot", "thead"</dt>
5513: <dd>
5514:
5515: <p><a href="#clear-the-stack-back-to-a-table-context">Clear the stack back to a table context</a>. (See
5516: below.)</p>
5517:
5518: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then
5519: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
5520: body</a>".</p>
5521:
5522: </dd>
5523:
5524: <dt>A start tag whose tag name is one of: "td", "th", "tr"</dt>
5525: <dd>
5526: <p>Act as if a start tag token with the tag name "tbody" had
5527: been seen, then reprocess the current token.</p>
5528: </dd>
5529:
5530: <dt>A start tag whose tag name is "table"</dt>
5531: <dd>
5532:
5533: <p><a href="#parse-error">Parse error</a>. Act as if an end tag token with
5534: the tag name "table" had been seen, then, if that token wasn't
5535: ignored, reprocess the current token.</p>
5536:
5537: <p class="note">The fake end tag token here can only be
5538: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5539:
5540: </dd>
5541:
5542: <dt>An end tag whose tag name is "table"</dt>
5543: <dd>
5544:
5545: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
5546: scope</a> with the same tag name as the token, this is a
5547: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
5548: case</a>)</p>
5549:
5550: <p>Otherwise:</p>
5551:
5552: <p>Pop elements from this stack until a <code><a href="tabular-data.html#the-table-element">table</a></code>
5553: element has been popped from the stack.</p>
5554:
5555: <p><a href="#reset-the-insertion-mode-appropriately">Reset the insertion mode appropriately</a>.</p>
5556:
5557: </dd>
5558:
5559: <dt>An end tag whose tag name is one of: "body", "caption",
5560: "col", "colgroup", "html", "tbody", "td", "tfoot", "th",
5561: "thead", "tr"</dt>
5562: <dd>
5563: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5564: </dd>
5565:
5566: <dt>A start tag whose tag name is one of: "style", "script"</dt>
5567: <dd>
5568:
5569: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
5570: mode</a>.</p>
5571:
5572: </dd>
5573:
5574: <dt>A start tag whose tag name is "input"</dt>
5575: <dd>
5576:
5577: <p>If the token does not have an attribute with the name "type",
5578: or if it does, but that attribute's value is not an <a href="infrastructure.html#ascii-case-insensitive">ASCII
5579: case-insensitive</a> match for the string "<code title="">hidden</code>", then: act as described in the "anything
5580: else" entry below.</p>
5581:
5582: <p>Otherwise:</p>
5583:
5584: <p><a href="#parse-error">Parse error</a>.</p>
5585:
5586: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5587:
5588: <p>Pop that <code><a href="forms.html#the-input-element">input</a></code> element off the <a href="#stack-of-open-elements">stack of
5589: open elements</a>.</p>
5590:
5591: </dd>
5592:
5593: <dt>An end-of-file token</dt>
5594: <dd>
5595:
5596: <p>If the <a href="#current-node">current node</a> is not the root
1.159 mike 5597: <code><a href="semantics.html#the-html-element-0">html</a></code> element, then this is a <a href="#parse-error">parse
1.1 mike 5598: error</a>.</p>
5599:
5600: <p class="note">It can only be the <a href="#current-node">current node</a> in
5601: the <a href="#fragment-case">fragment case</a>.</p>
5602:
5603: <p><a href="#stop-parsing">Stop parsing</a>.</p>
5604:
5605: </dd>
5606:
5607: <dt>Anything else</dt>
5608: <dd>
5609:
5610: <p><a href="#parse-error">Parse error</a>. Process the token <a href="#using-the-rules-for">using the
5611: rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in
5612: body</a>" <a href="#insertion-mode">insertion mode</a>, except that if the
5613: <a href="#current-node">current node</a> is a <code><a href="tabular-data.html#the-table-element">table</a></code>,
5614: <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>, <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code>, <code><a href="tabular-data.html#the-thead-element">thead</a></code>, or
5615: <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, then, whenever a node would be inserted
5616: into the <a href="#current-node">current node</a>, it must instead be <a href="#foster-parent" title="foster parent">foster parented</a>.</p>
5617:
5618: </dd>
5619:
5620: </dl><p>When the steps above require the UA to <dfn id="clear-the-stack-back-to-a-table-context">clear the stack
5621: back to a table context</dfn>, it means that the UA must, while
5622: the <a href="#current-node">current node</a> is not a <code><a href="tabular-data.html#the-table-element">table</a></code>
1.159 mike 5623: element or an <code><a href="semantics.html#the-html-element-0">html</a></code> element, pop elements from the
1.1 mike 5624: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
5625:
5626: <p class="note">The <a href="#current-node">current node</a> being an
1.159 mike 5627: <code><a href="semantics.html#the-html-element-0">html</a></code> element after this process is a <a href="#fragment-case">fragment
1.1 mike 5628: case</a>.</p>
5629:
5630:
5631:
5632: <h5 id="parsing-main-intabletext"><span class="secno">9.2.5.13 </span>The "<dfn title="insertion mode: in table text">in table text</dfn>" insertion mode</h5>
5633:
5634: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intabletext" title="insertion
5635: mode: in table text">in table text</a>", tokens must be handled
5636: as follows:</p>
5637:
5638: <dl class="switch"><dt>A character token</dt>
5639: <dd>
5640:
5641: <p>Append the character token to the <var><a href="#pending-table-character-tokens">pending table character
5642: tokens</a></var> list.</p>
5643:
5644: </dd>
5645:
5646:
5647: <dt>Anything else</dt>
5648: <dd>
5649:
5650: <p>If any of the tokens in the <var><a href="#pending-table-character-tokens">pending table character
5651: tokens</a></var> list are character tokens that are not one of U+0009
5652: CHARACTER TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED
5653: (FF), <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE, then
5654: reprocess those character tokens using the rules given in the
5655: "anything else" entry in the <a href="#parsing-main-intable" title="insertion mode: in
5656: table">in table</a>" insertion mode.</p>
5657:
5658: <p>Otherwise, <a href="#insert-a-character" title="insert a character">insert the
5659: characters</a> given by the <var><a href="#pending-table-character-tokens">pending table character
5660: tokens</a></var> list into the <a href="#current-node">current node</a>.</p>
5661:
5662: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5663: insertion mode</a> and reprocess the token.</p>
5664:
5665: </dd>
5666:
5667: </dl><h5 id="parsing-main-incaption"><span class="secno">9.2.5.14 </span>The "<dfn title="insertion mode: in caption">in caption</dfn>" insertion mode</h5>
5668:
5669: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-incaption" title="insertion
5670: mode: in caption">in caption</a>", tokens must be handled as follows:</p>
5671:
5672: <dl class="switch"><dt>An end tag whose tag name is "caption"</dt>
5673: <dd>
5674:
5675: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
5676: scope</a> with the same tag name as the token, this is a
5677: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
5678: case</a>)</p>
5679:
5680: <p>Otherwise:</p>
5681:
5682: <p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p>
5683:
5684: <p>Now, if the <a href="#current-node">current node</a> is not a
5685: <code><a href="tabular-data.html#the-caption-element">caption</a></code> element, then this is a <a href="#parse-error">parse
5686: error</a>.</p>
5687:
5688: <p>Pop elements from this stack until a <code><a href="tabular-data.html#the-caption-element">caption</a></code>
5689: element has been popped from the stack.</p>
5690:
5691: <p><a href="#clear-the-list-of-active-formatting-elements-up-to-the-last-marker">Clear the list of active formatting elements up to
5692: the last marker</a>.</p>
5693:
5694: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>".</p>
5695:
5696: </dd>
5697:
5698: <dt>A start tag whose tag name is one of: "caption", "col",
5699: "colgroup", "tbody", "td", "tfoot", "th", "thead", "tr"</dt>
5700: <dt>An end tag whose tag name is "table"</dt>
5701: <dd>
5702:
5703: <p><a href="#parse-error">Parse error</a>. Act as if an end tag with the tag
5704: name "caption" had been seen, then, if that token wasn't
5705: ignored, reprocess the current token.</p>
5706:
5707: <p class="note">The fake end tag token here can only be
5708: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5709:
5710: </dd>
5711:
5712: <dt>An end tag whose tag name is one of: "body", "col",
5713: "colgroup", "html", "tbody", "td", "tfoot", "th", "thead",
5714: "tr"</dt>
5715: <dd>
5716: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5717: </dd>
5718:
5719: <dt>Anything else</dt>
5720: <dd>
5721: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
5722: mode</a>.</p>
5723: </dd>
5724:
5725: </dl><h5 id="parsing-main-incolgroup"><span class="secno">9.2.5.15 </span>The "<dfn title="insertion mode: in column group">in column group</dfn>" insertion mode</h5>
5726:
5727: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-incolgroup" title="insertion
5728: mode: in column group">in column group</a>", tokens must be handled as follows:</p>
5729:
5730: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
5731: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
5732: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
5733: <dd>
5734: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
5735: the <a href="#current-node">current node</a>.</p>
5736: </dd>
5737:
5738: <dt>A comment token</dt>
5739: <dd>
5740: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
5741: node</a> with the <code title="">data</code> attribute set to
5742: the data given in the comment token.</p>
5743: </dd>
5744:
5745: <dt>A DOCTYPE token</dt>
5746: <dd>
5747: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5748: </dd>
5749:
5750: <dt>A start tag whose tag name is "html"</dt>
5751: <dd>
5752: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
5753: mode</a>.</p>
5754: </dd>
5755:
5756: <dt>A start tag whose tag name is "col"</dt>
5757: <dd>
5758:
5759: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
5760: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5761: elements</a>.</p>
5762:
5763: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
5764: token's <i>self-closing flag</i></a>, if it is set.</p>
5765:
5766: </dd>
5767:
5768: <dt>An end tag whose tag name is "colgroup"</dt>
5769: <dd>
5770:
5771: <p>If the <a href="#current-node">current node</a> is the root
1.159 mike 5772: <code><a href="semantics.html#the-html-element-0">html</a></code> element, then this is a <a href="#parse-error">parse
1.1 mike 5773: error</a>; ignore the token. (<a href="#fragment-case">fragment
5774: case</a>)</p>
5775:
5776: <p>Otherwise, pop the <a href="#current-node">current node</a> (which will be
5777: a <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element) from the <a href="#stack-of-open-elements">stack of open
5778: elements</a>. Switch the <a href="#insertion-mode">insertion mode</a> to
5779: "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>".</p>
5780:
5781: </dd>
5782:
5783: <dt>An end tag whose tag name is "col"</dt>
5784: <dd>
5785: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5786: </dd>
5787:
5788: <dt>An end-of-file token</dt>
5789: <dd>
5790:
1.159 mike 5791: <p>If the <a href="#current-node">current node</a> is the root <code><a href="semantics.html#the-html-element-0">html</a></code>
1.1 mike 5792: element, then <a href="#stop-parsing">stop parsing</a>. (<a href="#fragment-case">fragment
5793: case</a>)</p>
5794:
5795: <p>Otherwise, act as described in the "anything else" entry
5796: below.</p>
5797:
5798: </dd>
5799:
5800: <dt>Anything else</dt>
5801: <dd>
5802:
5803: <p>Act as if an end tag with the tag name "colgroup" had been
5804: seen, and then, if that token wasn't ignored, reprocess the
5805: current token.</p>
5806:
5807: <p class="note">The fake end tag token here can only be
5808: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5809:
5810: </dd>
5811:
5812: </dl><h5 id="parsing-main-intbody"><span class="secno">9.2.5.16 </span>The "<dfn title="insertion mode: in table body">in table body</dfn>" insertion mode</h5>
5813:
5814: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intbody" title="insertion
5815: mode: in table body">in table body</a>", tokens must be handled as follows:</p>
5816:
5817: <dl class="switch"><dt>A start tag whose tag name is "tr"</dt>
5818: <dd>
5819:
5820: <p><a href="#clear-the-stack-back-to-a-table-body-context">Clear the stack back to a table body
5821: context</a>. (See below.)</p>
5822:
5823: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then switch
5824: the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intr" title="insertion mode:
5825: in row">in row</a>".</p>
5826:
5827: </dd>
5828:
5829: <dt>A start tag whose tag name is one of: "th", "td"</dt>
5830: <dd>
5831: <p><a href="#parse-error">Parse error</a>. Act as if a start tag with
5832: the tag name "tr" had been seen, then reprocess the current
5833: token.</p>
5834: </dd>
5835:
5836: <dt>An end tag whose tag name is one of: "tbody", "tfoot",
5837: "thead"</dt>
5838: <dd>
5839:
5840: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
5841: scope</a> with the same tag name as the token, this is a
5842: <a href="#parse-error">parse error</a>. Ignore the token.</p>
5843:
5844: <p>Otherwise:</p>
5845:
5846: <p><a href="#clear-the-stack-back-to-a-table-body-context">Clear the stack back to a table body
5847: context</a>. (See below.)</p>
5848:
5849: <p>Pop the <a href="#current-node">current node</a> from the <a href="#stack-of-open-elements">stack of
5850: open elements</a>. Switch the <a href="#insertion-mode">insertion mode</a>
5851: to "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>".</p>
5852:
5853: </dd>
5854:
5855: <dt>A start tag whose tag name is one of: "caption", "col",
5856: "colgroup", "tbody", "tfoot", "thead"</dt>
5857: <dt>An end tag whose tag name is "table"</dt>
5858: <dd>
5859:
5860: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have a
5861: <code>tbody</code>, <code>thead</code>, or <code>tfoot</code>
5862: element in table scope</a>, this is a <a href="#parse-error">parse
5863: error</a>. Ignore the token. (<a href="#fragment-case">fragment
5864: case</a>)</p>
5865:
5866: <p>Otherwise:</p>
5867:
5868: <p><a href="#clear-the-stack-back-to-a-table-body-context">Clear the stack back to a table body
5869: context</a>. (See below.)</p>
5870:
5871: <p>Act as if an end tag with the same tag name as the
5872: <a href="#current-node">current node</a> ("tbody", "tfoot", or "thead") had
5873: been seen, then reprocess the current token.</p>
5874:
5875: </dd>
5876:
5877: <dt>An end tag whose tag name is one of: "body", "caption",
5878: "col", "colgroup", "html", "td", "th", "tr"</dt>
5879: <dd>
5880: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5881: </dd>
5882:
5883: <dt>Anything else</dt>
5884: <dd>
5885: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>" <a href="#insertion-mode">insertion
5886: mode</a>.</p>
5887: </dd>
5888:
5889: </dl><p>When the steps above require the UA to <dfn id="clear-the-stack-back-to-a-table-body-context">clear the stack
5890: back to a table body context</dfn>, it means that the UA must,
5891: while the <a href="#current-node">current node</a> is not a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>,
1.159 mike 5892: <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code>, <code><a href="tabular-data.html#the-thead-element">thead</a></code>, or <code><a href="semantics.html#the-html-element-0">html</a></code>
1.1 mike 5893: element, pop elements from the <a href="#stack-of-open-elements">stack of open
5894: elements</a>.</p>
5895:
5896: <p class="note">The <a href="#current-node">current node</a> being an
1.159 mike 5897: <code><a href="semantics.html#the-html-element-0">html</a></code> element after this process is a <a href="#fragment-case">fragment
1.1 mike 5898: case</a>.</p>
5899:
5900:
5901: <h5 id="parsing-main-intr"><span class="secno">9.2.5.17 </span>The "<dfn title="insertion mode: in row">in row</dfn>" insertion mode</h5>
5902:
5903: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intr" title="insertion
5904: mode: in row">in row</a>", tokens must be handled as follows:</p>
5905:
5906: <dl class="switch"><dt>A start tag whose tag name is one of: "th", "td"</dt>
5907: <dd>
5908:
5909: <p><a href="#clear-the-stack-back-to-a-table-row-context">Clear the stack back to a table row
5910: context</a>. (See below.)</p>
5911:
5912: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then switch
5913: the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intd" title="insertion mode:
5914: in cell">in cell</a>".</p>
5915:
5916: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
5917: formatting elements</a>.</p>
5918:
5919: </dd>
5920:
5921: <dt>An end tag whose tag name is "tr"</dt>
5922: <dd>
5923:
5924: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
5925: scope</a> with the same tag name as the token, this is a
5926: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
5927: case</a>)</p>
5928:
5929: <p>Otherwise:</p>
5930:
5931: <p><a href="#clear-the-stack-back-to-a-table-row-context">Clear the stack back to a table row
5932: context</a>. (See below.)</p>
5933:
5934: <p>Pop the <a href="#current-node">current node</a> (which will be a
5935: <code><a href="tabular-data.html#the-tr-element">tr</a></code> element) from the <a href="#stack-of-open-elements">stack of open
5936: elements</a>. Switch the <a href="#insertion-mode">insertion mode</a> to
5937: "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
5938: body</a>".</p>
5939:
5940: </dd>
5941:
5942: <dt>A start tag whose tag name is one of: "caption", "col",
5943: "colgroup", "tbody", "tfoot", "thead", "tr"</dt>
5944: <dt>An end tag whose tag name is "table"</dt>
5945: <dd>
5946:
5947: <p>Act as if an end tag with the tag name "tr" had been seen,
5948: then, if that token wasn't ignored, reprocess the current
5949: token.</p>
5950:
5951: <p class="note">The fake end tag token here can only be
5952: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5953:
5954: </dd>
5955:
5956: <dt>An end tag whose tag name is one of: "tbody", "tfoot",
5957: "thead"</dt>
5958: <dd>
5959:
5960: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
5961: scope</a> with the same tag name as the token, this is a
5962: <a href="#parse-error">parse error</a>. Ignore the token.</p>
5963:
5964: <p>Otherwise, act as if an end tag with the tag name "tr" had
5965: been seen, then reprocess the current token.</p>
5966:
5967: </dd>
5968:
5969: <dt>An end tag whose tag name is one of: "body", "caption",
5970: "col", "colgroup", "html", "td", "th"</dt>
5971: <dd>
5972: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5973: </dd>
5974:
5975: <dt>Anything else</dt>
5976: <dd>
5977: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>" <a href="#insertion-mode">insertion
5978: mode</a>.</p>
5979: </dd>
5980:
5981: </dl><p>When the steps above require the UA to <dfn id="clear-the-stack-back-to-a-table-row-context">clear the stack
5982: back to a table row context</dfn>, it means that the UA must,
5983: while the <a href="#current-node">current node</a> is not a <code><a href="tabular-data.html#the-tr-element">tr</a></code>
1.159 mike 5984: element or an <code><a href="semantics.html#the-html-element-0">html</a></code> element, pop elements from the
1.1 mike 5985: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
5986:
5987: <p class="note">The <a href="#current-node">current node</a> being an
1.159 mike 5988: <code><a href="semantics.html#the-html-element-0">html</a></code> element after this process is a <a href="#fragment-case">fragment
1.1 mike 5989: case</a>.</p>
5990:
5991:
5992: <h5 id="parsing-main-intd"><span class="secno">9.2.5.18 </span>The "<dfn title="insertion mode: in cell">in cell</dfn>" insertion mode</h5>
5993:
5994: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intd" title="insertion
5995: mode: in cell">in cell</a>", tokens must be handled as follows:</p>
5996:
5997: <dl class="switch"><dt>An end tag whose tag name is one of: "td", "th"</dt>
5998: <dd>
5999:
6000: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
6001: scope</a> with the same tag name as that of the token, then
6002: this is a <a href="#parse-error">parse error</a> and the token must be
6003: ignored.</p>
6004:
6005: <p>Otherwise:</p>
6006:
6007: <p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p>
6008:
6009: <p>Now, if the <a href="#current-node">current node</a> is not an element
6010: with the same tag name as the token, then this is a
6011: <a href="#parse-error">parse error</a>.</p>
6012:
6013: <p>Pop elements from this stack until an element with the same
6014: tag name as the token has been popped from the stack.</p>
6015:
6016: <p><a href="#clear-the-list-of-active-formatting-elements-up-to-the-last-marker">Clear the list of active formatting elements up to
6017: the last marker</a>.</p>
6018:
6019: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intr" title="insertion mode: in row">in row</a>". (The
6020: <a href="#current-node">current node</a> will be a <code><a href="tabular-data.html#the-tr-element">tr</a></code> element at
6021: this point.)</p>
6022:
6023: </dd>
6024:
6025: <dt>A start tag whose tag name is one of: "caption", "col",
6026: "colgroup", "tbody", "td", "tfoot", "th", "thead", "tr"</dt>
6027: <dd>
6028:
6029: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does
6030: <em>not</em> <a href="#has-an-element-in-table-scope" title="has an element in table scope">have
6031: a <code>td</code> or <code>th</code> element in table
6032: scope</a>, then this is a <a href="#parse-error">parse error</a>; ignore
6033: the token. (<a href="#fragment-case">fragment case</a>)</p>
6034:
6035: <p>Otherwise, <a href="#close-the-cell">close the cell</a> (see below) and
6036: reprocess the current token.</p>
6037:
6038: </dd>
6039:
6040: <dt>An end tag whose tag name is one of: "body", "caption",
6041: "col", "colgroup", "html"</dt>
6042: <dd>
6043: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6044: </dd>
6045:
6046: <dt>An end tag whose tag name is one of: "table", "tbody",
6047: "tfoot", "thead", "tr"</dt>
6048: <dd>
6049:
6050: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
6051: scope</a> with the same tag name as that of the token
6052: (which can only happen for "tbody", "tfoot" and "thead", or,
6053: in the <a href="#fragment-case">fragment case</a>), then this is a <a href="#parse-error">parse
6054: error</a> and the token must be ignored.</p>
6055:
6056: <p>Otherwise, <a href="#close-the-cell">close the cell</a> (see below) and
6057: reprocess the current token.</p>
6058:
6059: </dd>
6060:
6061: <dt>Anything else</dt>
6062: <dd>
6063: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6064: mode</a>.</p>
6065: </dd>
6066:
6067: </dl><p>Where the steps above say to <dfn id="close-the-cell">close the cell</dfn>, they
6068: mean to run the following algorithm:</p>
6069:
6070: <ol><li><p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-table-scope" title="has an element in table scope">has a <code>td</code>
6071: element in table scope</a>, then act as if an end tag token
6072: with the tag name "td" had been seen.</p></li>
6073:
6074: <li><p>Otherwise, the <a href="#stack-of-open-elements">stack of open elements</a> will
6075: <a href="#has-an-element-in-table-scope" title="has an element in table scope">have a
6076: <code>th</code> element in table scope</a>; act as if an end
6077: tag token with the tag name "th" had been seen.</p></li>
6078:
6079: </ol><p class="note">The <a href="#stack-of-open-elements">stack of open elements</a> cannot
6080: have both a <code><a href="tabular-data.html#the-td-element">td</a></code> and a <code><a href="tabular-data.html#the-th-element">th</a></code> element <a href="#has-an-element-in-table-scope" title="has an element in table scope">in table scope</a> at
6081: the same time, nor can it have neither when the <a href="#insertion-mode">insertion
6082: mode</a> is "<a href="#parsing-main-intd" title="insertion mode: in cell">in
6083: cell</a>".</p>
6084:
6085:
6086: <h5 id="parsing-main-inselect"><span class="secno">9.2.5.19 </span>The "<dfn title="insertion mode: in select">in select</dfn>" insertion mode</h5>
6087:
6088: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inselect" title="insertion
6089: mode: in select">in select</a>", tokens must be handled as follows:</p>
6090:
6091: <dl class="switch"><dt>A character token</dt>
6092: <dd>
6093: <p><a href="#insert-a-character" title="insert a character">Insert the token's
6094: character</a> into the <a href="#current-node">current node</a>.</p>
6095: </dd>
6096:
6097: <dt>A comment token</dt>
6098: <dd>
6099: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6100: node</a> with the <code title="">data</code> attribute set to
6101: the data given in the comment token.</p>
6102: </dd>
6103:
6104: <dt>A DOCTYPE token</dt>
6105: <dd>
6106: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6107: </dd>
6108:
6109: <dt>A start tag whose tag name is "html"</dt>
6110: <dd>
6111: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6112: mode</a>.</p>
6113: </dd>
6114:
6115: <dt>A start tag whose tag name is "option"</dt>
6116: <dd>
6117:
6118: <p>If the <a href="#current-node">current node</a> is an <code><a href="forms.html#the-option-element">option</a></code>
6119: element, act as if an end tag with the tag name "option" had
6120: been seen.</p>
6121:
6122: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
6123:
6124: </dd>
6125:
6126: <dt>A start tag whose tag name is "optgroup"</dt>
6127: <dd>
6128:
6129: <p>If the <a href="#current-node">current node</a> is an <code><a href="forms.html#the-option-element">option</a></code>
6130: element, act as if an end tag with the tag name "option" had
6131: been seen.</p>
6132:
6133: <p>If the <a href="#current-node">current node</a> is an
6134: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, act as if an end tag with the
6135: tag name "optgroup" had been seen.</p>
6136:
6137: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
6138:
6139: </dd>
6140:
6141: <dt>An end tag whose tag name is "optgroup"</dt>
6142: <dd>
6143:
6144: <p>First, if the <a href="#current-node">current node</a> is an
6145: <code><a href="forms.html#the-option-element">option</a></code> element, and the node immediately before
6146: it in the <a href="#stack-of-open-elements">stack of open elements</a> is an
6147: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, then act as if an end tag with
6148: the tag name "option" had been seen.</p>
6149:
6150: <p>If the <a href="#current-node">current node</a> is an
6151: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, then pop that node from the
6152: <a href="#stack-of-open-elements">stack of open elements</a>. Otherwise, this is a
6153: <a href="#parse-error">parse error</a>; ignore the token.</p>
6154:
6155: </dd>
6156:
6157: <dt>An end tag whose tag name is "option"</dt>
6158: <dd>
6159:
6160: <p>If the <a href="#current-node">current node</a> is an <code><a href="forms.html#the-option-element">option</a></code>
6161: element, then pop that node from the <a href="#stack-of-open-elements">stack of open
6162: elements</a>. Otherwise, this is a <a href="#parse-error">parse
6163: error</a>; ignore the token.</p>
6164:
6165: </dd>
6166:
6167: <dt>An end tag whose tag name is "select"</dt>
6168: <dd>
6169:
6170: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have an element in table
6171: scope</a> with the same tag name as the token, this is a
6172: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
6173: case</a>)</p>
6174:
6175: <p>Otherwise:</p>
6176:
6177: <p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
6178: until a <code><a href="forms.html#the-select-element">select</a></code> element has been popped from the
6179: stack.</p>
6180:
6181: <p><a href="#reset-the-insertion-mode-appropriately">Reset the insertion mode appropriately</a>.</p>
6182:
6183: </dd>
6184:
6185: <dt>A start tag whose tag name is "select"</dt>
6186: <dd>
6187:
6188: <p><a href="#parse-error">Parse error</a>. Act as if the token had been
6189: an end tag with the tag name "select" instead.</p>
6190:
6191: </dd>
6192:
6193: <dt>A start tag whose tag name is one of: "input", "keygen", "textarea"</dt>
6194: <dd>
1.73 mike 6195:
6196: <p><a href="#parse-error">Parse error</a>.</p>
6197:
1.124 mike 6198: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does not <a href="#has-an-element-in-table-scope" title="has an element in table scope">have a <code>select</code>
6199: element in table scope</a>, ignore the token. (<a href="#fragment-case">fragment
6200: case</a>)</p>
1.73 mike 6201:
6202: <p>Otherwise, act as if an end tag with the tag name "select" had
6203: been seen, and reprocess the token.</p>
6204:
1.1 mike 6205: </dd>
6206:
6207: <dt>A start tag token whose tag name is "script"</dt>
6208: <dd>
6209: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
6210: mode</a>.</p>
6211: </dd>
6212:
6213: <dt>An end-of-file token</dt>
6214: <dd>
6215:
6216: <p>If the <a href="#current-node">current node</a> is not the root
1.159 mike 6217: <code><a href="semantics.html#the-html-element-0">html</a></code> element, then this is a <a href="#parse-error">parse
1.1 mike 6218: error</a>.</p>
6219:
6220: <p class="note">It can only be the <a href="#current-node">current node</a> in
6221: the <a href="#fragment-case">fragment case</a>.</p>
6222:
6223: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6224:
6225: </dd>
6226:
6227: <dt>Anything else</dt>
6228: <dd>
6229: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6230: </dd>
6231:
6232: </dl><h5 id="parsing-main-inselectintable"><span class="secno">9.2.5.20 </span>The "<dfn title="insertion mode: in select in table">in select in table</dfn>" insertion mode</h5>
6233:
6234: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inselectintable" title="insertion
6235: mode: in select in table">in select in table</a>", tokens must be handled as follows:</p>
6236:
6237: <dl class="switch"><dt>A start tag whose tag name is one of: "caption", "table",
6238: "tbody", "tfoot", "thead", "tr", "td", "th"</dt>
6239: <dd>
6240: <p><a href="#parse-error">Parse error</a>. Act as if an end tag with the tag
6241: name "select" had been seen, and reprocess the token.</p>
6242: </dd>
6243:
6244: <dt>An end tag whose tag name is one of: "caption", "table",
6245: "tbody", "tfoot", "thead", "tr", "td", "th"</dt>
6246: <dd>
6247:
6248: <p><a href="#parse-error">Parse error</a>.</p>
6249:
6250: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-table-scope">has an
6251: element in table scope</a> with the same tag name as that
6252: of the token, then act as if an end tag with the tag name
6253: "select" had been seen, and reprocess the token. Otherwise,
6254: ignore the token.</p>
6255:
6256: </dd>
6257:
6258: <dt>Anything else</dt>
6259: <dd>
6260: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inselect" title="insertion mode: in select">in select</a>" <a href="#insertion-mode">insertion
6261: mode</a>.</p>
6262: </dd>
6263:
1.168 mike 6264: </dl><h5 id="parsing-main-inforeign"><span class="secno">9.2.5.21 </span>The "<dfn title="insertion mode: in foreign content">in foreign content</dfn>" insertion mode</h5>
1.1 mike 6265:
6266: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inforeign" title="insertion
6267: mode: in foreign content">in foreign content</a>", tokens must be
6268: handled as follows:</p>
6269:
6270: <dl class="switch"><dt>A character token</dt>
6271: <dd>
6272:
6273: <p><a href="#insert-a-character" title="insert a character">Insert the token's
6274: character</a> into the <a href="#current-node">current node</a>.</p>
6275:
6276: <p>If the token is not one of U+0009 CHARACTER TABULATION, U+000A
6277: LINE FEED (LF), U+000C FORM FEED (FF), <!--U+000D CARRIAGE RETURN
6278: (CR),--> or U+0020 SPACE, then set the <a href="#frameset-ok-flag">frameset-ok
6279: flag</a> to "not ok".</p>
6280:
6281: </dd>
6282:
6283: <dt>A comment token</dt>
6284: <dd>
6285: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6286: node</a> with the <code title="">data</code> attribute set to
6287: the data given in the comment token.</p>
6288: </dd>
6289:
6290: <dt>A DOCTYPE token</dt>
6291: <dd>
6292: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6293: </dd>
6294:
6295: <dt>An end tag whose tag name is "script", if the <a href="#current-node">current node</a> is a <code title="">script</code> element in the <a href="#svg-namespace">SVG namespace</a>.</dt>
6296: <dd>
6297:
6298: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
6299: elements</a>.</p>
6300:
6301: <p>Let the <var title="">old insertion point</var> have the
6302: same value as the current <a href="#insertion-point">insertion point</a>. Let
6303: the <a href="#insertion-point">insertion point</a> be just before the <a href="#next-input-character">next
6304: input character</a>.</p>
6305:
6306: <p>Increment the parser's <a href="#script-nesting-level">script nesting level</a> by
6307: one. Set the <a href="#parser-pause-flag">parser pause flag</a> to true.</p>
6308:
6309: <p><a href="http://www.w3.org/TR/SVGMobile12/script.html#ScriptContentProcessing">Process
6310: the <code title="">script</code> element</a> according to the SVG
1.187 mike 6311: rules, if the user agent supports SVG. <a href="references.html#refsSVG">[SVG]</a></p>
1.1 mike 6312:
1.159 mike 6313: <p class="note">Even if this causes <a href="embedded-content-0.html#dom-document-write" title="dom-document-write">new characters to be inserted into the
1.1 mike 6314: tokenizer</a>, the parser will not be executed reentrantly,
6315: since the <a href="#parser-pause-flag">parser pause flag</a> is true.</p>
6316:
6317: <p>Decrement the parser's <a href="#script-nesting-level">script nesting level</a> by
6318: one. If the parser's <a href="#script-nesting-level">script nesting level</a> is zero,
6319: then set the <a href="#parser-pause-flag">parser pause flag</a> to false.</p>
6320:
6321: <p>Let the <a href="#insertion-point">insertion point</a> have the value of the <var title="">old insertion point</var>. (In other words, restore the
6322: <a href="#insertion-point">insertion point</a> to its previous value. This value
6323: might be the "undefined" value.)</p>
6324:
6325: </dd>
6326:
6327: <dt>A start tag whose tag name is neither "mglyph" nor "malignmark", if the <a href="#current-node">current node</a> is an <code title="">mi</code> element in the <a href="#mathml-namespace">MathML namespace</a>.</dt>
6328: <dt>A start tag whose tag name is neither "mglyph" nor "malignmark", if the <a href="#current-node">current node</a> is an <code title="">mo</code> element in the <a href="#mathml-namespace">MathML namespace</a>.</dt>
6329: <dt>A start tag whose tag name is neither "mglyph" nor "malignmark", if the <a href="#current-node">current node</a> is an <code title="">mn</code> element in the <a href="#mathml-namespace">MathML namespace</a>.</dt>
6330: <dt>A start tag whose tag name is neither "mglyph" nor "malignmark", if the <a href="#current-node">current node</a> is an <code title="">ms</code> element in the <a href="#mathml-namespace">MathML namespace</a>.</dt>
6331: <dt>A start tag whose tag name is neither "mglyph" nor "malignmark", if the <a href="#current-node">current node</a> is an <code title="">mtext</code> element in the <a href="#mathml-namespace">MathML namespace</a>.</dt>
6332: <dt>A start tag whose tag name is "svg", if the <a href="#current-node">current node</a> is an <code title="">annotation-xml</code> element in the <a href="#mathml-namespace">MathML namespace</a>.</dt>
6333: <dt>A start tag, if the <a href="#current-node">current node</a> is a <code title="">foreignObject</code> element in the <a href="#svg-namespace">SVG namespace</a>.</dt>
6334: <dt>A start tag, if the <a href="#current-node">current node</a> is a <code title="">desc</code> element in the <a href="#svg-namespace">SVG namespace</a>.</dt>
6335: <dt>A start tag, if the <a href="#current-node">current node</a> is a <code title="">title</code> element in the <a href="#svg-namespace">SVG namespace</a>.</dt>
6336: <dt>A start tag, if the <a href="#current-node">current node</a> is an element in the <a href="#html-namespace-0">HTML namespace</a>.</dt>
6337: <dt>An end tag</dt>
6338: <dd>
6339:
6340: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the
6341: <a href="#secondary-insertion-mode">secondary insertion mode</a>.</p>
6342:
6343: <p>If, after doing so, the <a href="#insertion-mode">insertion mode</a> is still
6344: "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in foreign
6345: content</a>", but there is no element in scope that has a
6346: namespace other than the <a href="#html-namespace-0">HTML namespace</a><!-- XXX this
6347: isn't well-defined; it means check to see if the bottom-most HTML
6348: element on the stack is in scope -->, switch the <a href="#insertion-mode">insertion
6349: mode</a> to the <a href="#secondary-insertion-mode">secondary insertion mode</a>.</p>
6350:
6351: </dd>
6352:
6353: <dt>A start tag whose tag name is one of: <!--"a",--> "b", "big",
6354: "blockquote", "body"<!--by inspection-->, "br", "center", "code",
6355: "dd", "div", "dl", "dt"<!-- so that dd and dt can be handled
6356: uniformly throughout the parser -->, "em", "embed", "h1", "h2",
6357: "h3", "h4"<!--for completeness-->, "h5", "h6"<!--for
6358: completeness-->, "head"<!--by inspection-->, "hr", "i", "img",
6359: "li", "listing"<!-- so that pre and listing can be handled
6360: uniformly throughout the parser -->, "menu", "meta", "nobr",
6361: "ol"<!-- so that dl, ul, and ol can be handled uniformly throughout
6362: the parser -->, "p", "pre", "ruby", "s", <!--"script",--> "small",
6363: "span", "strong", "strike"<!-- so that s and strike can be handled
6364: uniformly throughout the parser -->, <!--"style",--> "sub", "sup",
6365: "table"<!--by inspection-->, "tt", "u", "ul", "var"</dt>
6366: <!-- this list was determined empirically by studying over
6367: 6,000,000,000 pages that were specifically not XML pages -->
6368: <dt>A start tag whose tag name is "font", if the token has
6369: any attributes named "color", "face", or "size"</dt>
6370: <!-- the attributes here are required so that SVG <font> will go
6371: through as SVG but legacy <font>s won't -->
6372: <dt>An end-of-file token</dt>
6373: <dd>
6374:
6375: <p><a href="#parse-error">Parse error</a>.</p>
6376:
6377: <p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a> until
6378: the <a href="#current-node">current node</a> is in the <a href="#html-namespace-0">HTML
6379: namespace</a>.</p>
6380:
6381: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#secondary-insertion-mode">secondary
6382: insertion mode</a>, and reprocess the token.</p>
6383:
6384: </dd>
6385:
6386: <dt>Any other start tag</dt>
6387: <dd>
6388:
6389: <p>If the <a href="#current-node">current node</a> is an element in the
6390: <a href="#mathml-namespace">MathML namespace</a>, <a href="#adjust-mathml-attributes">adjust MathML
6391: attributes</a> for the token. (This fixes the case of MathML
6392: attributes that are not all lowercase.)</p>
6393:
6394: <p>If the <a href="#current-node">current node</a> is an element in the <a href="#svg-namespace">SVG
6395: namespace</a>, and the token's tag name is one of the ones in
6396: the first column of the following table, change the tag name to
6397: the name given in the corresponding cell in the second
6398: column. (This fixes the case of SVG elements that are not all
6399: lowercase.)</p>
6400:
6401: <table><thead><tr><th> Tag name </th><th> Element name
6402: </th></tr></thead><tbody><tr><td> <code title="">altglyph</code> </td><td> <code title="">altGlyph</code>
6403: </td></tr><tr><td> <code title="">altglyphdef</code> </td><td> <code title="">altGlyphDef</code>
6404: </td></tr><tr><td> <code title="">altglyphitem</code> </td><td> <code title="">altGlyphItem</code>
6405: </td></tr><tr><td> <code title="">animatecolor</code> </td><td> <code title="">animateColor</code>
6406: </td></tr><tr><td> <code title="">animatemotion</code> </td><td> <code title="">animateMotion</code>
6407: </td></tr><tr><td> <code title="">animatetransform</code> </td><td> <code title="">animateTransform</code>
6408: </td></tr><tr><td> <code title="">clippath</code> </td><td> <code title="">clipPath</code>
6409: </td></tr><tr><td> <code title="">feblend</code> </td><td> <code title="">feBlend</code>
6410: </td></tr><tr><td> <code title="">fecolormatrix</code> </td><td> <code title="">feColorMatrix</code>
6411: </td></tr><tr><td> <code title="">fecomponenttransfer</code> </td><td> <code title="">feComponentTransfer</code>
6412: </td></tr><tr><td> <code title="">fecomposite</code> </td><td> <code title="">feComposite</code>
6413: </td></tr><tr><td> <code title="">feconvolvematrix</code> </td><td> <code title="">feConvolveMatrix</code>
6414: </td></tr><tr><td> <code title="">fediffuselighting</code> </td><td> <code title="">feDiffuseLighting</code>
6415: </td></tr><tr><td> <code title="">fedisplacementmap</code> </td><td> <code title="">feDisplacementMap</code>
6416: </td></tr><tr><td> <code title="">fedistantlight</code> </td><td> <code title="">feDistantLight</code>
6417: </td></tr><tr><td> <code title="">feflood</code> </td><td> <code title="">feFlood</code>
6418: </td></tr><tr><td> <code title="">fefunca</code> </td><td> <code title="">feFuncA</code>
6419: </td></tr><tr><td> <code title="">fefuncb</code> </td><td> <code title="">feFuncB</code>
6420: </td></tr><tr><td> <code title="">fefuncg</code> </td><td> <code title="">feFuncG</code>
6421: </td></tr><tr><td> <code title="">fefuncr</code> </td><td> <code title="">feFuncR</code>
6422: </td></tr><tr><td> <code title="">fegaussianblur</code> </td><td> <code title="">feGaussianBlur</code>
6423: </td></tr><tr><td> <code title="">feimage</code> </td><td> <code title="">feImage</code>
6424: </td></tr><tr><td> <code title="">femerge</code> </td><td> <code title="">feMerge</code>
6425: </td></tr><tr><td> <code title="">femergenode</code> </td><td> <code title="">feMergeNode</code>
6426: </td></tr><tr><td> <code title="">femorphology</code> </td><td> <code title="">feMorphology</code>
6427: </td></tr><tr><td> <code title="">feoffset</code> </td><td> <code title="">feOffset</code>
6428: </td></tr><tr><td> <code title="">fepointlight</code> </td><td> <code title="">fePointLight</code>
6429: </td></tr><tr><td> <code title="">fespecularlighting</code> </td><td> <code title="">feSpecularLighting</code>
6430: </td></tr><tr><td> <code title="">fespotlight</code> </td><td> <code title="">feSpotLight</code>
6431: </td></tr><tr><td> <code title="">fetile</code> </td><td> <code title="">feTile</code>
6432: </td></tr><tr><td> <code title="">feturbulence</code> </td><td> <code title="">feTurbulence</code>
6433: </td></tr><tr><td> <code title="">foreignobject</code> </td><td> <code title="">foreignObject</code>
6434: </td></tr><tr><td> <code title="">glyphref</code> </td><td> <code title="">glyphRef</code>
6435: </td></tr><tr><td> <code title="">lineargradient</code> </td><td> <code title="">linearGradient</code>
6436: </td></tr><tr><td> <code title="">radialgradient</code> </td><td> <code title="">radialGradient</code>
6437: <!--<tr> <td> <code title="">solidcolor</code> <td> <code title="">solidColor</code> (SVG 1.2)-->
6438: </td></tr><tr><td> <code title="">textpath</code> </td><td> <code title="">textPath</code>
6439: </td></tr></tbody></table><p>If the <a href="#current-node">current node</a> is an element in the <a href="#svg-namespace">SVG
6440: namespace</a>, <a href="#adjust-svg-attributes">adjust SVG attributes</a> for the
6441: token. (This fixes the case of SVG attributes that are not all
6442: lowercase.)</p>
6443:
6444: <p><a href="#adjust-foreign-attributes">Adjust foreign attributes</a> for the token. (This
6445: fixes the use of namespaced attributes, in particular XLink in
6446: SVG.)</p>
6447:
6448: <p><a href="#insert-a-foreign-element">Insert a foreign element</a> for the token, in the
6449: same namespace as the <a href="#current-node">current node</a>.</p>
6450:
6451: <p>If the token has its <i>self-closing flag</i> set, pop the
6452: <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
6453: elements</a> and <a href="#acknowledge-self-closing-flag" title="acknowledge self-closing
6454: flag">acknowledge the token's <i>self-closing flag</i></a>.</p>
6455:
6456: </dd>
6457:
6458: </dl><h5 id="parsing-main-afterbody"><span class="secno">9.2.5.22 </span>The "<dfn title="insertion mode: after body">after body</dfn>" insertion mode</h5>
6459:
6460: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-afterbody" title="insertion
6461: mode: after body">after body</a>", tokens must be handled as follows:</p>
6462:
6463: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
6464: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6465: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6466: <dd>
6467: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6468: mode</a>.</p>
6469: </dd>
6470:
6471: <dt>A comment token</dt>
6472: <dd>
6473: <p>Append a <code>Comment</code> node to the first element in
1.159 mike 6474: the <a href="#stack-of-open-elements">stack of open elements</a> (the <code><a href="semantics.html#the-html-element-0">html</a></code>
1.1 mike 6475: element), with the <code title="">data</code> attribute set to
6476: the data given in the comment token.</p>
6477: </dd>
6478:
6479: <dt>A DOCTYPE token</dt>
6480: <dd>
6481: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6482: </dd>
6483:
6484: <dt>A start tag whose tag name is "html"</dt>
6485: <dd>
6486: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6487: mode</a>.</p>
6488: </dd>
6489:
6490: <dt>An end tag whose tag name is "html"</dt>
6491: <dd>
6492:
6493: <p>If the parser was originally created as part of the <a href="#html-fragment-parsing-algorithm">HTML
6494: fragment parsing algorithm</a>, this is a <a href="#parse-error">parse
6495: error</a>; ignore the token. (<a href="#fragment-case">fragment case</a>)</p>
6496:
6497: <p>Otherwise, switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-after-after-body-insertion-mode" title="insertion mode: after after body">after after
6498: body</a>".</p>
6499:
6500: </dd>
6501:
6502: <dt>An end-of-file token</dt>
6503: <dd>
6504: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6505: </dd>
6506:
6507: <dt>Anything else</dt>
6508: <dd>
6509:
6510: <p><a href="#parse-error">Parse error</a>. Switch the <a href="#insertion-mode">insertion
6511: mode</a> to "<a href="#parsing-main-inbody" title="insertion mode: in body">in
6512: body</a>" and reprocess the token.</p>
6513:
6514: </dd>
6515:
6516: </dl><h5 id="parsing-main-inframeset"><span class="secno">9.2.5.23 </span>The "<dfn title="insertion mode: in frameset">in frameset</dfn>" insertion mode</h5>
6517:
6518: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inframeset" title="insertion
6519: mode: in frameset">in frameset</a>", tokens must be handled as follows:</p>
6520:
6521: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
6522: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6523: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6524: <dd>
6525: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
6526: the <a href="#current-node">current node</a>.</p>
6527: </dd>
6528:
6529: <dt>A comment token</dt>
6530: <dd>
6531: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6532: node</a> with the <code title="">data</code> attribute set to
6533: the data given in the comment token.</p>
6534: </dd>
6535:
6536: <dt>A DOCTYPE token</dt>
6537: <dd>
6538: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6539: </dd>
6540:
6541: <dt>A start tag whose tag name is "html"</dt>
6542: <dd>
6543: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6544: mode</a>.</p>
6545: </dd>
6546:
6547: <dt>A start tag whose tag name is "frameset"</dt>
6548: <dd>
6549: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
6550: </dd>
6551:
6552: <dt>An end tag whose tag name is "frameset"</dt>
6553: <dd>
6554:
6555: <p>If the <a href="#current-node">current node</a> is the root
1.159 mike 6556: <code><a href="semantics.html#the-html-element-0">html</a></code> element, then this is a <a href="#parse-error">parse
1.1 mike 6557: error</a>; ignore the token. (<a href="#fragment-case">fragment
6558: case</a>)</p>
6559:
6560: <p>Otherwise, pop the <a href="#current-node">current node</a> from the
6561: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
6562:
6563: <p>If the parser was <em>not</em> originally created as part
6564: of the <a href="#html-fragment-parsing-algorithm">HTML fragment parsing algorithm</a>
6565: (<a href="#fragment-case">fragment case</a>), and the <a href="#current-node">current
1.5 mike 6566: node</a> is no longer a <code><a href="obsolete.html#frameset">frameset</a></code> element, then
1.1 mike 6567: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-afterframeset" title="insertion mode: after frameset">after
6568: frameset</a>".</p>
6569:
6570: </dd>
6571:
6572: <dt>A start tag whose tag name is "frame"</dt>
6573: <dd>
6574:
6575: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.
6576: Immediately pop the <a href="#current-node">current node</a> off the
6577: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
6578:
6579: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
6580: token's <i>self-closing flag</i></a>, if it is set.</p>
6581:
6582: </dd>
6583:
6584: <dt>A start tag whose tag name is "noframes"</dt>
6585: <dd>
6586: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
6587: mode</a>.</p>
6588: </dd>
6589:
6590: <dt>An end-of-file token</dt>
6591: <dd>
6592:
6593: <p>If the <a href="#current-node">current node</a> is not the root
1.159 mike 6594: <code><a href="semantics.html#the-html-element-0">html</a></code> element, then this is a <a href="#parse-error">parse
1.1 mike 6595: error</a>.</p>
6596:
6597: <p class="note">It can only be the <a href="#current-node">current node</a> in
6598: the <a href="#fragment-case">fragment case</a>.</p>
6599:
6600: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6601:
6602: </dd>
6603:
6604: <dt>Anything else</dt>
6605: <dd>
6606: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6607: </dd>
6608:
6609: </dl><h5 id="parsing-main-afterframeset"><span class="secno">9.2.5.24 </span>The "<dfn title="insertion mode: after frameset">after frameset</dfn>" insertion mode</h5>
6610:
6611: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-afterframeset" title="insertion
6612: mode: after frameset">after frameset</a>", tokens must be handled as follows:</p>
6613:
6614: <!-- due to rules in the "in frameset" mode, this can't be entered in the fragment case -->
6615: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
6616: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6617: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6618: <dd>
6619: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
6620: the <a href="#current-node">current node</a>.</p>
6621: </dd>
6622:
6623: <dt>A comment token</dt>
6624: <dd>
6625: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6626: node</a> with the <code title="">data</code> attribute set to
6627: the data given in the comment token.</p>
6628: </dd>
6629:
6630: <dt>A DOCTYPE token</dt>
6631: <dd>
6632: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6633: </dd>
6634:
6635: <dt>A start tag whose tag name is "html"</dt>
6636: <dd>
6637: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6638: mode</a>.</p>
6639: </dd>
6640:
6641: <dt>An end tag whose tag name is "html"</dt>
6642: <dd>
6643: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#the-after-after-frameset-insertion-mode" title="insertion mode: after after frameset">after after
6644: frameset</a>".</p>
6645: </dd>
6646:
6647: <dt>A start tag whose tag name is "noframes"</dt>
6648: <dd>
6649: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
6650: mode</a>.</p>
6651: </dd>
6652:
6653: <dt>An end-of-file token</dt>
6654: <dd>
6655: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6656: </dd>
6657:
6658: <dt>Anything else</dt>
6659: <dd>
6660: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6661: </dd>
6662:
6663: </dl><p class="XXX">This doesn't handle UAs that don't support
6664: frames, or that do support frames but want to show the NOFRAMES
6665: content. Supporting the former is easy; supporting the latter is
6666: harder.</p>
6667:
6668:
6669: <h5 id="the-after-after-body-insertion-mode"><span class="secno">9.2.5.25 </span>The "<dfn title="insertion mode: after after body">after after body</dfn>" insertion mode</h5>
6670:
6671: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-after-after-body-insertion-mode" title="insertion
6672: mode: after after body">after after body</a>", tokens must be handled as follows:</p>
6673:
6674: <dl class="switch"><dt>A comment token</dt>
6675: <dd>
6676: <p>Append a <code>Comment</code> node to the <code>Document</code>
6677: object with the <code title="">data</code> attribute set to the
6678: data given in the comment token.</p>
6679: </dd>
6680:
6681: <dt>A DOCTYPE token</dt>
6682: <dt>A character token that is one of U+0009 CHARACTER
6683: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6684: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6685: <dt>A start tag whose tag name is "html"</dt>
6686: <dd>
6687: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6688: mode</a>.</p>
6689: </dd>
6690:
6691: <dt>An end-of-file token</dt>
6692: <dd>
6693: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6694: </dd>
6695:
6696: <dt>Anything else</dt>
6697: <dd>
6698: <p><a href="#parse-error">Parse error</a>. Switch the <a href="#insertion-mode">insertion mode</a>
6699: to "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" and
6700: reprocess the token.</p>
6701: </dd>
6702:
6703: </dl><h5 id="the-after-after-frameset-insertion-mode"><span class="secno">9.2.5.26 </span>The "<dfn title="insertion mode: after after frameset">after after frameset</dfn>" insertion mode</h5>
6704:
6705: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-after-after-frameset-insertion-mode" title="insertion
6706: mode: after after frameset">after after frameset</a>", tokens must be handled as follows:</p>
6707:
6708: <dl class="switch"><dt>A comment token</dt>
6709: <dd>
6710: <p>Append a <code>Comment</code> node to the <code>Document</code>
6711: object with the <code title="">data</code> attribute set to the
6712: data given in the comment token.</p>
6713: </dd>
6714:
6715: <dt>A DOCTYPE token</dt>
6716: <dt>A character token that is one of U+0009 CHARACTER
6717: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6718: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6719: <dt>A start tag whose tag name is "html"</dt>
6720: <dd>
6721: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" <a href="#insertion-mode">insertion
6722: mode</a>.</p>
6723: </dd>
6724:
6725: <dt>An end-of-file token</dt>
6726: <dd>
6727: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6728: </dd>
6729:
6730: <dt>A start tag whose tag name is "noframes"</dt>
6731: <dd>
6732: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the "<a href="#parsing-main-inhead" title="insertion mode: in head">in head</a>" <a href="#insertion-mode">insertion
6733: mode</a>.</p>
6734: </dd>
6735:
6736: <dt>Anything else</dt>
6737: <dd>
6738: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6739: </dd>
6740:
6741: </dl><h4 id="the-end"><span class="secno">9.2.6 </span>The end</h4>
6742:
6743: <p>Once the user agent <dfn id="stop-parsing" title="stop parsing">stops parsing</dfn>
6744: the document, the user agent must follow the steps in this
6745: section.</p>
6746:
1.10 mike 6747: <!-- this happens as part of one of the tasks that runs the parser -->
1.1 mike 6748:
1.10 mike 6749: <p>First, the user agent must set the <a href="dom.html#current-document-readiness">current document
6750: readiness</a> to "interactive" and the <a href="#insertion-point">insertion
6751: point</a> to undefined.</p>
6752:
6753: <p>Then, the user agent must then make a list of all the scripts
6754: that are in the <a href="semantics.html#list-of-scripts-that-will-execute-when-the-document-has-finished-parsing">list of scripts that will execute when the
6755: document has finished parsing</a>, the <a href="semantics.html#list-of-scripts-that-will-execute-asynchronously">list of scripts that
6756: will execute asynchronously</a>, and the <a href="semantics.html#list-of-scripts-that-will-execute-as-soon-as-possible">list of scripts
6757: that will execute as soon as possible</a>. This is the <dfn id="list-of-scripts-pending-after-the-parser-stopped">list
6758: of scripts pending after the parser stopped</dfn>.</p>
6759:
6760: <p>The rules for <a href="semantics.html#when-a-script-completes-loading">when a script completes loading</a> start
6761: applying (script execution is no longer managed by the parser).</p>
1.1 mike 6762:
6763: <p>If any of the scripts in the <a href="semantics.html#list-of-scripts-that-will-execute-as-soon-as-possible">list of scripts that will
6764: execute as soon as possible</a> have <a href="semantics.html#completed-loading">completed
6765: loading</a>, or if the <a href="semantics.html#list-of-scripts-that-will-execute-asynchronously">list of scripts that will execute
6766: asynchronously</a> is not empty and the first script in that list
6767: has <a href="semantics.html#completed-loading">completed loading</a>, then the user agent must act as
6768: if those scripts just completed loading, following the rules given
6769: for that in the <code><a href="semantics.html#script">script</a></code> element definition.</p>
6770:
1.10 mike 6771: <p>If the <a href="semantics.html#list-of-scripts-that-will-execute-when-the-document-has-finished-parsing">list of scripts that will execute when the document
6772: has finished parsing</a> is not empty, and the first item in this
6773: list has already <a href="semantics.html#completed-loading">completed loading</a>, then the user agent
6774: must act as if that script just finished loading.</p>
6775:
6776: <p class="note">By this point, there will be no scripts that have
6777: loaded but have not yet been executed.</p>
6778:
6779: <hr><!-- async --><p>Once all the scripts on the <a href="#list-of-scripts-pending-after-the-parser-stopped">list of scripts pending after
6780: the parser stopped</a> have <a href="semantics.html#completed-loading">completed loading</a> and
6781: been <a href="semantics.html#executing-a-script-block" title="executing a script block">executed</a>, the
6782: user agent must <a href="browsers.html#queue-a-task">queue a task</a> to <a href="browsers.html#fire-a-simple-event">fire a simple
6783: event</a> called <code title="event-DOMContentLoaded">DOMContentLoaded</code> at the
6784: <code>Document</code>. (If the list is empty, this happens
6785: immediately.)</p>
1.1 mike 6786:
1.10 mike 6787: <hr><!-- async --><p>Once everything that <dfn id="delay-the-load-event" title="delay the load event">delays the
1.1 mike 6788: load event</dfn> of the document has completed, the user agent must
6789: run the following steps:</p>
6790:
6791: <ol><li><a href="browsers.html#queue-a-task">Queue a task</a> to set the <a href="dom.html#current-document-readiness">current document
6792: readiness</a> to "complete".</li>
6793:
6794: <li>If the <code>Document</code> is in a <a href="browsers.html#browsing-context">browsing
6795: context</a>, then <a href="browsers.html#queue-a-task">queue a task</a> to <a href="browsers.html#fire-a-simple-event">fire a
6796: simple event</a> called <code title="event-load"><a href="video.html#event-load">load</a></code> at
6797: the <code>Document</code>'s <code><a href="browsers.html#window">Window</a></code> object, but with
6798: its <code title="dom-event-target">target</code> set to the
6799: <code>Document</code> object (and the <code title="dom-event-currentTarget">currentTarget</code> set to the
6800: <code><a href="browsers.html#window">Window</a></code> object).</li>
6801:
6802: <li>If the <code>Document</code> has a <a href="history.html#pending-state-object">pending state
6803: object</a>, then <a href="browsers.html#queue-a-task">queue a task</a> to fire a <code title="event-popstate"><a href="history.html#event-popstate">popstate</a></code> event in no namespace on the
6804: <code>Document</code>'s <code><a href="browsers.html#window">Window</a></code> object using the
6805: <code><a href="history.html#popstateevent">PopStateEvent</a></code> interface, with the <code title="dom-PopStateEvent-state"><a href="history.html#dom-popstateevent-state">state</a></code> attribute set to the
6806: current value of the <a href="history.html#pending-state-object">pending state object</a>. This event
6807: must bubble but not be cancelable and has no default action.</li>
6808:
6809: </ol><p>The <a href="browsers.html#task-source">task source</a> for these tasks is the <a href="browsers.html#dom-manipulation-task-source">DOM
6810: manipulation task source</a>.</p>
6811:
6812: <!-- XXX make sure things "delay the load event", e.g. applet and
6813: object element's frame contents -->
6814:
6815: <p class="XXX">delaying the load event for things like image
6816: loads allows for intranet port scans (even without
6817: javascript!). Should we really encode that into the spec?</p>
6818:
6819:
6820: <!--XXX need to handle
6821: http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#2354
6822: 2354 // Don't open transient styles if it makes the stack deep, bug 58917.
6823: -->
6824:
6825: <!--XXX
6826: http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/nsHTMLTokenizer.cpp#749
6827: -->
6828:
6829: <!--
6830: see also CTextToken::ConsumeCharacterData() for CDATA parsing?
6831:
6832: 1212 1 Here's a tricky case from bug 22596: <h5><li><h5>
6833: 1213 How do we know that the 2nd <h5> should close the <LI> rather than nest inside the <LI>?
6834: 1214 (Afterall, the <h5> is a legal child of the <LI>).
6835: 1215
6836: 1216 The way you know is that there is no root between the two, so the <h5> binds more
6837: 1217 tightly to the 1st <h5> than to the <LI>.
6838: 1218 2. Also, bug 6148 shows this case: <SPAN><DIV><SPAN>
6839: 1219 From this case we learned not to execute this logic if the parent is a block.
6840: 1220
6841: 1221 3. Fix for 26583
6842: 1222 Ex. <A href=foo.html><B>foo<A href-bar.html>bar</A></B></A> <- A legal HTML
6843: 1223 In the above example clicking on "foo" or "bar" should link to
6844: 1224 foo.html or bar.html respectively. That is, the inner <A> should be informed
6845: 1225 about the presence of an open <A> above <B>..so that the inner <A> can close out
6846: 1226 the outer <A>. The following code does it for us.
6847: 1227
6848: 1228 4. Fix for 27865 [ similer to 22596 ]. Ex: <DL><DD><LI>one<DD><LI>two
6849: - http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#1211
6850:
6851: 815 // Here's a problem. If theTag is legal in here, we don't move it
6852: 816 // out. So if we're moving stuff out of here, the parent of theTag
6853: 817 // gets closed at this point. But some things are legal
6854: 818 // _everywhere_ and hence would effectively close out misplaced
6855: 819 // content in tables. This is undesirable, so treat them as
6856: 820 // illegal here so they'll be shipped out with their parents and
6857: 821 // siblings. See bug 40855 for an explanation (that bug was for
6858: 822 // comments, but the same issues arise with whitespace, newlines,
6859: 823 // noscript, etc). Script is special, though. Shipping it out
6860: 824 // breaks document.write stuff. See bug 243064.
6861: - http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#825
6862:
6863:
6864: 1326 /**************************************************************************************
6865: 1327 *
6866: 1328 * Now a little code to deal with bug #49687 (crash when layout stack gets too deep)
6867: 1329 * I've also opened this up to any container (not just inlines): re bug 55095
6868: 1330 * Improved to handle bug 55980 (infinite loop caused when DEPTH is exceeded and
6869: 1331 * </P> is encountered by itself (<P>) is continuously produced.
6870: 1332 *
6871: 1333 **************************************************************************************/
6872:
6873: 1912 // Oh boy!! we found a "stray" tag. Nav4.x and IE introduce line break in
6874: 1913 // such cases. So, let's simulate that effect for compatibility.
6875: 1914 // Ex. <html><body>Hello</P>There</body></html>
6876: http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#1912
6877:
6878: http://lxr.mozilla.org/seamonkey/search?string=nested
6879: /parser/htmlparser/src/CNavDTD.cpp, line 791 - * 2. <CENTER><DL><DT><A><CENTER> allow nested <CENTER>
6880: /parser/htmlparser/src/CNavDTD.cpp, line 792 - * 3. <TABLE><TR><TD><TABLE>... allow nested <TABLE>
6881: /parser/htmlparser/src/CNavDTD.cpp, line 2562 - // Discard nested forms - bug 72639
6882: /parser/htmlparser/src/nsElementTable.cpp, line 1453 - * 2. <CENTER><DL><DT><A><CENTER> allow nested <CENTER>
6883: /parser/htmlparser/src/nsElementTable.cpp, line 1454 - * 3. <TABLE><TR><TD><TABLE>... allow nested <TABLE>
6884: /parser/htmlparser/src/nsElementTable.cpp, line 1901 - // Ex: <H1><LI><H1><LI>. Inner LI has the potential of getting nested
6885: -->
6886:
6887:
6888: <h4 id="coercing-an-html-dom-into-an-infoset"><span class="secno">9.2.7 </span>Coercing an HTML DOM into an infoset</h4>
6889:
6890: <p>When an application uses an <a href="#html-parser">HTML parser</a> in
6891: conjunction with an XML pipeline, it is possible that the
6892: constructed DOM is not compatible with the XML tool chain in certain
6893: subtle ways. For example, an XML toolchain might not be able to
6894: represent attributes with the name <code title="">xmlns</code>,
6895: since they conflict with the Namespaces in XML syntax. There is also
6896: some data that the <a href="#html-parser">HTML parser</a> generates that isn't
6897: included in the DOM itself. This section specifies some rules for
6898: handling these issues.</p>
6899:
6900: <p>If the XML API being used doesn't support DOCTYPEs, the tool may
6901: drop DOCTYPEs altogether.</p>
6902:
6903: <p>If the XML API doesn't support attributes in no namespace that
6904: are named "<code title="">xmlns</code>", attributes whose names
6905: start with "<code title="">xmlns:</code>", or attributes in the
6906: <a href="#xmlns-namespace">XMLNS namespace</a>, then the tool may drop such
6907: attributes.</p>
6908:
6909: <p>The tool may annotate the output with any namespace declarations
6910: required for proper operation.</p>
6911:
6912: <p>If the XML API being used restricts the allowable characters in
6913: the local names of elements and attributes, then the tool may map
6914: all element and attribute local names that the API wouldn't support
6915: to a set of names that <em>are</em> allowed, by replacing any
6916: character that isn't supported with the uppercase letter U and the
6917: six digits of the character's Unicode code point when expressed in
6918: hexadecimal, using digits 0-9 and capital letters A-F as the
6919: symbols, in increasing numeric order.</p>
6920:
6921: <p class="example">For example, the element name <code title="">foo<bar</code>, which can be output by the <a href="#html-parser">HTML
6922: parser</a>, though it is neither a legal HTML element name nor a
6923: well-formed XML element name, would be converted into <code title="">fooU00003Cbar</code>, which <em>is</em> a well-formed XML
6924: element name (though it's still not legal in HTML by any means).</p>
6925:
6926: <p class="example">As another example, consider the attribute
6927: <code>xlink:href</code>. Used on a MathML element, it becomes, after
6928: being <a href="#adjust-foreign-attributes" title="adjust foreign attributes">adjusted</a>, an
6929: attribute with a prefix "<code title="">xlink</code>" and a local
6930: name "<code title="">href</code>". However, used on an HTML element,
6931: it becomes an attribute with no prefix and the local name "<code title="">xlink:href</code>", which is not a valid NCName, and thus
6932: might not be accepted by an XML API. It could thus get converted,
6933: becoming "<code title="">xlinkU00003Ahref</code>".</p>
6934:
6935: <p class="note">The resulting names from this conversion
6936: conveniently can't clash with any attribute generated by the
6937: <a href="#html-parser">HTML parser</a>, since those are all either lowercase or
6938: those listed in the <a href="#adjust-foreign-attributes">adjust foreign attributes</a>
6939: algorithm's table.</p>
6940:
6941: <p>If the XML API restricts comments from having two consecutive
6942: U+002D HYPHEN-MINUS characters (--), the tool may insert a single
6943: U+0020 SPACE character between any such offending characters.</p>
6944:
6945: <p>If the XML API restricts comments from ending in a
6946: U+002D HYPHEN-MINUS character (-), the tool may insert a single
6947: U+0020 SPACE character at the end of such comments.</p>
6948:
6949: <p>If the XML API restricts allowed characters in character data,
6950: the tool may replace any U+000C FORM FEED (FF) character with a
6951: U+0020 SPACE character, and any other literal non-XML character with
6952: a U+FFFD REPLACEMENT CHARACTER.</p>
6953:
6954: <p>If the tool has no way to convey out-of-band information, then
6955: the tool may drop the following information:</p>
6956:
6957: <ul><li>Whether the document is set to <i><a href="dom.html#no-quirks-mode">no quirks mode</a></i>,
6958: <i><a href="dom.html#limited-quirks-mode">limited quirks mode</a></i>, or <i><a href="dom.html#quirks-mode">quirks mode</a></i></li>
6959:
6960: <li>The association between form controls and forms that aren't
6961: their nearest <code><a href="forms.html#the-form-element">form</a></code> element ancestor (use of the
6962: <a href="#form-element-pointer"><code>form</code> element pointer</a> in the parser)</li>
6963:
6964: </ul><p class="note">The mutations allowed by this section apply
6965: <em>after</em> the <a href="#html-parser">HTML parser</a>'s rules have been
6966: applied. For example, a <code title=""><a::></code> start tag
6967: will be closed by a <code title=""></a::></code> end tag, and
6968: never by a <code title=""></aU00003AU00003A></code> end tag, even
6969: if the user agent is using the rules above to then generate an
6970: actual element in the DOM with the name <code title="">aU00003AU00003A</code> for that start tag.</p>
6971:
6972:
6973:
1.35 mike 6974: <h4 id="an-introduction-to-error-handling-and-strange-cases-in-the-parser"><span class="secno">9.2.8 </span>An introduction to error handling and strange cases in the parser</h4>
1.1 mike 6975:
6976: <p><i>This section is non-normative.</i></p>
6977:
6978: <p>This section examines some erroneous markup and discusses how
6979: the <a href="#html-parser">HTML parser</a> handles these cases.</p>
6980:
6981:
6982: <h5 id="misnested-tags:-b-i-b-i"><span class="secno">9.2.8.1 </span>Misnested tags: <b><i></b></i></h5>
6983:
6984: <p><i>This section is non-normative.</i></p>
6985:
6986: <p>The most-often discussed example of erroneous markup is as
6987: follows:</p>
6988:
6989: <pre><p>1<b>2<i>3</b>4</i>5</p></pre>
6990:
6991: <p>The parsing of this markup is straightforward up to the "3". At
6992: this point, the DOM looks like this:</p>
6993:
1.159 mike 6994: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="semantics.html#the-p-element">p</a></code><ul><li class="t3"><code>#text</code>: <span title="">1</span></li><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">2</span></li><li class="t1"><code><a href="text-level-semantics.html#the-i-element">i</a></code><ul><li class="t3"><code>#text</code>: <span title="">3</span></li></ul></li></ul></li></ul></li></ul></li></ul></li></ul><p>Here, the <a href="#stack-of-open-elements">stack of open elements</a> has five elements
6995: on it: <code><a href="semantics.html#the-html-element-0">html</a></code>, <code><a href="semantics.html#the-body-element-0">body</a></code>, <code><a href="semantics.html#the-p-element">p</a></code>,
1.1 mike 6996: <code><a href="text-level-semantics.html#the-b-element">b</a></code>, and <code><a href="text-level-semantics.html#the-i-element">i</a></code>. The <a href="#list-of-active-formatting-elements">list of active
6997: formatting elements</a> just has two: <code><a href="text-level-semantics.html#the-b-element">b</a></code> and
6998: <code><a href="text-level-semantics.html#the-i-element">i</a></code>. The <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>".</p>
6999:
7000: <p>Upon receiving the end tag token with the tag name "b", the "<a href="#adoptionAgency">adoption agency algorithm</a>" is
7001: invoked. This is a simple case, in that the <var title="">formatting
7002: element</var> is the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element, and there is no
7003: <var title="">furthest block</var>. Thus, the <a href="#stack-of-open-elements">stack of open
1.159 mike 7004: elements</a> ends up with just three elements: <code><a href="semantics.html#the-html-element-0">html</a></code>,
7005: <code><a href="semantics.html#the-body-element-0">body</a></code>, and <code><a href="semantics.html#the-p-element">p</a></code>, while the <a href="#list-of-active-formatting-elements">list of
1.1 mike 7006: active formatting elements</a> has just one: <code><a href="text-level-semantics.html#the-i-element">i</a></code>. The
7007: DOM tree is unmodified at this point.</p>
7008:
7009: <p>The next token is a character ("4"), triggers the <a href="#reconstruct-the-active-formatting-elements" title="reconstruct the active formatting elements">reconstruction of
7010: the active formatting elements</a>, in this case just the
7011: <code><a href="text-level-semantics.html#the-i-element">i</a></code> element. A new <code><a href="text-level-semantics.html#the-i-element">i</a></code> element is thus created
7012: for the "4" text node. After the end tag token for the "i" is also
7013: received, and the "5" text node is inserted, the DOM looks as
7014: follows:</p>
7015:
1.159 mike 7016: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="semantics.html#the-p-element">p</a></code><ul><li class="t3"><code>#text</code>: <span title="">1</span></li><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">2</span></li><li class="t1"><code><a href="text-level-semantics.html#the-i-element">i</a></code><ul><li class="t3"><code>#text</code>: <span title="">3</span></li></ul></li></ul></li><li class="t1"><code><a href="text-level-semantics.html#the-i-element">i</a></code><ul><li class="t3"><code>#text</code>: <span title="">4</span></li></ul></li><li class="t3"><code>#text</code>: <span title="">5</span></li></ul></li></ul></li></ul></li></ul><h5 id="misnested-tags:-b-p-b-p"><span class="secno">9.2.8.2 </span>Misnested tags: <b><p></b></p></h5>
1.1 mike 7017:
7018: <p><i>This section is non-normative.</i></p>
7019:
7020: <p>A case similar to the previous one is the following:</p>
7021:
7022: <pre><b>1<p>2</b>3</p></pre>
7023:
7024: <p>Up to the "2" the parsing here is straightforward:</p>
7025:
1.159 mike 7026: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">1</span></li><li class="t1"><code><a href="semantics.html#the-p-element">p</a></code><ul><li class="t3"><code>#text</code>: <span title="">2</span></li></ul></li></ul></li></ul></li></ul></li></ul><p>The interesting part is when the end tag token with the tag name
1.1 mike 7027: "b" is parsed.</p>
7028:
7029: <p>Before that token is seen, the <a href="#stack-of-open-elements">stack of open
1.159 mike 7030: elements</a> has four elements on it: <code><a href="semantics.html#the-html-element-0">html</a></code>,
7031: <code><a href="semantics.html#the-body-element-0">body</a></code>, <code><a href="text-level-semantics.html#the-b-element">b</a></code>, and <code><a href="semantics.html#the-p-element">p</a></code>. The
1.1 mike 7032: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> just has the one:
7033: <code><a href="text-level-semantics.html#the-b-element">b</a></code>. The <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>".</p>
7034:
7035: <p>Upon receiving the end tag token with the tag name "b", the "<a href="#adoptionAgency">adoption agency algorithm</a>" is invoked, as
7036: in the previous example. However, in this case, there <em>is</em> a
7037: <var title="">furthest block</var>, namely the <code><a href="semantics.html#the-p-element">p</a></code> element. Thus,
7038: this time the adoption agency algorithm isn't skipped over.</p>
7039:
1.159 mike 7040: <p>The <var title="">common ancestor</var> is the <code><a href="semantics.html#the-body-element-0">body</a></code>
1.1 mike 7041: element. A conceptual "bookmark" marks the position of the
7042: <code><a href="text-level-semantics.html#the-b-element">b</a></code> in the <a href="#list-of-active-formatting-elements">list of active formatting
7043: elements</a>, but since that list has only one element in it,
7044: it won't have much effect.</p>
7045:
7046: <p>As the algorithm progresses, <var title="">node</var> ends up set
7047: to the formatting element (<code><a href="text-level-semantics.html#the-b-element">b</a></code>), and <var title="">last
7048: node</var> ends up set to the <var title="">furthest block</var>
7049: (<code><a href="semantics.html#the-p-element">p</a></code>).</p>
7050:
7051: <p>The <var title="">last node</var> gets appended (moved) to the
7052: <var title="">common ancestor</var>, so that the DOM looks like:</p>
7053:
1.159 mike 7054: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">1</span></li></ul></li><li class="t1"><code><a href="semantics.html#the-p-element">p</a></code><ul><li class="t3"><code>#text</code>: <span title="">2</span></li></ul></li></ul></li></ul></li></ul><p>A new <code><a href="text-level-semantics.html#the-b-element">b</a></code> element is created, and the children of the
1.1 mike 7055: <code><a href="semantics.html#the-p-element">p</a></code> element are moved to it:</p>
7056:
1.159 mike 7057: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">1</span></li></ul></li><li class="t1"><code><a href="semantics.html#the-p-element">p</a></code></li></ul></li></ul></li></ul><ul class="domTree"><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">2</span></li></ul></li></ul><p>Finally, the new <code><a href="text-level-semantics.html#the-b-element">b</a></code> element is appended to the
1.1 mike 7058: <code><a href="semantics.html#the-p-element">p</a></code> element, so that the DOM looks like:</p>
7059:
1.159 mike 7060: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">1</span></li></ul></li><li class="t1"><code><a href="semantics.html#the-p-element">p</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">2</span></li></ul></li></ul></li></ul></li></ul></li></ul><p>The <code><a href="text-level-semantics.html#the-b-element">b</a></code> element is removed from the <a href="#list-of-active-formatting-elements">list of
1.1 mike 7061: active formatting elements</a> and the <a href="#stack-of-open-elements">stack of open
7062: elements</a>, so that when the "3" is parsed, it is appended to
7063: the <code><a href="semantics.html#the-p-element">p</a></code> element:</p>
7064:
1.159 mike 7065: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">1</span></li></ul></li><li class="t1"><code><a href="semantics.html#the-p-element">p</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">2</span></li></ul></li><li class="t3"><code>#text</code>: <span title="">3</span></li></ul></li></ul></li></ul></li></ul><h5 id="unexpected-markup-in-tables"><span class="secno">9.2.8.3 </span>Unexpected markup in tables</h5>
1.1 mike 7066:
7067: <p><i>This section is non-normative.</i></p>
7068:
7069: <p>Error handling in tables is, for historical reasons, especially
7070: strange. For example, consider the following markup:</p>
7071:
7072: <pre><table><strong><b></strong><tr><td>aaa</td></tr><strong>bbb</strong></table>ccc</pre>
7073:
7074: <p>The highlighted <code><a href="text-level-semantics.html#the-b-element">b</a></code> element start tag is not allowed
7075: directly inside a table like that, and the parser handles this case
7076: by placing the element <em>before</em> the table. (This is called <i title="foster parent"><a href="#foster-parent">foster parenting</a></i>.) This can be seen by
7077: examining the DOM tree as it stands just after the
7078: <code><a href="tabular-data.html#the-table-element">table</a></code> element's start tag has been seen:</p>
7079:
1.159 mike 7080: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-table-element">table</a></code></li></ul></li></ul></li></ul><p>...and then immediately after the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element start
1.1 mike 7081: tag has been seen:</p>
7082:
1.159 mike 7083: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code></li><li class="t1"><code><a href="tabular-data.html#the-table-element">table</a></code></li></ul></li></ul></li></ul><p>At this point, the <a href="#stack-of-open-elements">stack of open elements</a> has on it
7084: the elements <code><a href="semantics.html#the-html-element-0">html</a></code>, <code><a href="semantics.html#the-body-element-0">body</a></code>,
1.1 mike 7085: <code><a href="tabular-data.html#the-table-element">table</a></code>, and <code><a href="text-level-semantics.html#the-b-element">b</a></code> (in that order, despite the
7086: resulting DOM tree); the <a href="#list-of-active-formatting-elements">list of active formatting
7087: elements</a> just has the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in it; and the
7088: <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intable" title="insertion mode: in
7089: table">in table</a>".</p>
7090:
7091: <p>The <code><a href="tabular-data.html#the-tr-element">tr</a></code> start tag causes the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element
7092: to be popped off the stack and a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> start tag to be
7093: implied; the <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> and <code><a href="tabular-data.html#the-tr-element">tr</a></code> elements are
7094: then handled in a rather straight-forward manner, taking the parser
7095: through the "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
7096: body</a>" and "<a href="#parsing-main-intr" title="insertion mode: in row">in
7097: row</a>" insertion modes, after which the DOM looks as
7098: follows:</p>
7099:
1.159 mike 7100: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code></li><li class="t1"><code><a href="tabular-data.html#the-table-element">table</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tbody-element">tbody</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tr-element">tr</a></code></li></ul></li></ul></li></ul></li></ul></li></ul><p>Here, the <a href="#stack-of-open-elements">stack of open elements</a> has on it the
7101: elements <code><a href="semantics.html#the-html-element-0">html</a></code>, <code><a href="semantics.html#the-body-element-0">body</a></code>, <code><a href="tabular-data.html#the-table-element">table</a></code>,
1.1 mike 7102: <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>, and <code><a href="tabular-data.html#the-tr-element">tr</a></code>; the <a href="#list-of-active-formatting-elements">list of active
7103: formatting elements</a> still has the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in
7104: it; and the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intr" title="insertion
7105: mode: in row">in row</a>".</p>
7106:
7107: <p>The <code><a href="tabular-data.html#the-td-element">td</a></code> element start tag token, after putting a
7108: <code><a href="tabular-data.html#the-td-element">td</a></code> element on the tree, puts a marker on the <a href="#list-of-active-formatting-elements">list
7109: of active formatting elements</a> (it also switches to the "<a href="#parsing-main-intd" title="insertion mode: in cell">in cell</a>" <a href="#insertion-mode">insertion
7110: mode</a>).</p>
7111:
1.159 mike 7112: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code></li><li class="t1"><code><a href="tabular-data.html#the-table-element">table</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tbody-element">tbody</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tr-element">tr</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-td-element">td</a></code></li></ul></li></ul></li></ul></li></ul></li></ul></li></ul><p>The marker means that when the "aaa" character tokens are seen,
1.1 mike 7113: no <code><a href="text-level-semantics.html#the-b-element">b</a></code> element is created to hold the resulting text
7114: node:</p>
7115:
1.159 mike 7116: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code></li><li class="t1"><code><a href="tabular-data.html#the-table-element">table</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tbody-element">tbody</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tr-element">tr</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-td-element">td</a></code><ul><li class="t3"><code>#text</code>: <span title="">aaa</span></li></ul></li></ul></li></ul></li></ul></li></ul></li></ul></li></ul><p>The end tags are handled in a straight-forward manner; after
1.1 mike 7117: handling them, the <a href="#stack-of-open-elements">stack of open elements</a> has on it the
1.159 mike 7118: elements <code><a href="semantics.html#the-html-element-0">html</a></code>, <code><a href="semantics.html#the-body-element-0">body</a></code>, <code><a href="tabular-data.html#the-table-element">table</a></code>,
1.1 mike 7119: and <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>; the <a href="#list-of-active-formatting-elements">list of active formatting
7120: elements</a> still has the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in it (the
7121: marker having been removed by the "td" end tag token); and the
7122: <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intbody" title="insertion mode: in
7123: table body">in table body</a>".</p>
7124:
7125: <p>Thus it is that the "bbb" character tokens are found. These
7126: trigger the "<a href="#parsing-main-intabletext" title="insertion mode: in table text">in table
7127: text</a>" insertion mode to be used (with the <a href="#original-insertion-mode">original
7128: insertion mode</a> set to "<a href="#parsing-main-intbody" title="insertion mode: in table
7129: body">in table body</a>"). The character tokens are collected,
7130: and when the next token (the <code><a href="tabular-data.html#the-table-element">table</a></code> element end tag) is
7131: seen, they are processed as a group. Since they are not all spaces,
7132: they are handled as per the "anything else" rules in the "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>" insertion mode,
7133: which defer to the "<a href="#parsing-main-inbody" title="insertion mode: in body">in
7134: body</a>" insertion mode but with <a href="#foster-parent" title="foster
7135: parent">foster parenting</a>.</p>
7136:
7137: <p>When <a href="#reconstruct-the-active-formatting-elements" title="reconstruct the active formatting elements">the
7138: active formatting elements are reconstructed</a>, a
7139: <code><a href="text-level-semantics.html#the-b-element">b</a></code> element is created and <a href="#foster-parent" title="foster
7140: parent">foster parented</a>, and then the "bbb" text node is
7141: appended to it:</p>
7142:
1.159 mike 7143: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code></li><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">bbb</span></li></ul></li><li class="t1"><code><a href="tabular-data.html#the-table-element">table</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tbody-element">tbody</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tr-element">tr</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-td-element">td</a></code><ul><li class="t3"><code>#text</code>: <span title="">aaa</span></li></ul></li></ul></li></ul></li></ul></li></ul></li></ul></li></ul><p>The <a href="#stack-of-open-elements">stack of open elements</a> has on it the elements
7144: <code><a href="semantics.html#the-html-element-0">html</a></code>, <code><a href="semantics.html#the-body-element-0">body</a></code>, <code><a href="tabular-data.html#the-table-element">table</a></code>,
1.1 mike 7145: <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>, and the new <code><a href="text-level-semantics.html#the-b-element">b</a></code> (again, note that
7146: this doesn't match the resulting tree!); the <a href="#list-of-active-formatting-elements">list of active
7147: formatting elements</a> has the new <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in it;
7148: and the <a href="#insertion-mode">insertion mode</a> is still "<a href="#parsing-main-intbody" title="insertion
7149: mode: in table body">in table body</a>".</p>
7150:
7151: <p>Had the character tokens been only <a href="infrastructure.html#space-character" title="space
7152: character">space characters</a> instead of "bbb", then those
7153: <a href="infrastructure.html#space-character" title="space character">space characters</a> would just be
7154: appended to the <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element.</p>
7155:
7156: <p>Finally, the <code><a href="tabular-data.html#the-table-element">table</a></code> is closed by a "table" end
7157: tag. This pops all the nodes from the <a href="#stack-of-open-elements">stack of open
7158: elements</a> up to and including the <code><a href="tabular-data.html#the-table-element">table</a></code> element,
7159: but it doesn't affect the <a href="#list-of-active-formatting-elements">list of active formatting
7160: elements</a>, so the "ccc" character tokens after the table
7161: result in yet another <code><a href="text-level-semantics.html#the-b-element">b</a></code> element being created, this
7162: time after the table:</p>
7163:
1.159 mike 7164: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code></li><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">bbb</span></li></ul></li><li class="t1"><code><a href="tabular-data.html#the-table-element">table</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tbody-element">tbody</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-tr-element">tr</a></code><ul><li class="t1"><code><a href="tabular-data.html#the-td-element">td</a></code><ul><li class="t3"><code>#text</code>: <span title="">aaa</span></li></ul></li></ul></li></ul></li></ul></li><li class="t1"><code><a href="text-level-semantics.html#the-b-element">b</a></code><ul><li class="t3"><code>#text</code>: <span title="">ccc</span></li></ul></li></ul></li></ul></li></ul><h5 id="scripts-that-modify-the-page-as-it-is-being-parsed"><span class="secno">9.2.8.4 </span>Scripts that modify the page as it is being parsed</h5>
1.1 mike 7165:
7166: <p><i>This section is non-normative.</i></p>
7167:
7168: <p>Consider the following markup, which for this example we will
7169: assume is the document with <a href="infrastructure.html#url">URL</a> <code title="">http://example.com/inner</code>, being rendered as the
1.159 mike 7170: content of an <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code> in another document with the
1.1 mike 7171: <a href="infrastructure.html#url">URL</a> <code title="">http://example.com/outer</code>:</p>
7172:
7173: <pre><div id=a>
7174: <script>
7175: var div = document.getElementById('a');
7176: parent.document.body.appendChild(div);
7177: </script>
7178: <script>
7179: alert(document.URL);
7180: </script>
7181: </div>
7182: <script>
7183: alert(document.URL);
7184: </script></pre>
7185:
7186: <p>Up to the first "script" end tag, before the script is parsed,
7187: the result is relatively straightforward:</p>
7188:
1.159 mike 7189: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="interactive-elements.html#the-div-element">div</a></code> <span class="t2" title=""><code class="attribute name">id</code>="<code class="attribute value"><a href="text-level-semantics.html#the-a-element">a</a></code>"</span><ul><li class="t3"><code>#text</code>: <span title="">
1.1 mike 7190: </span></li><li class="t1"><code><a href="semantics.html#script">script</a></code><ul><li class="t3"><code>#text</code>: <span title="">var div = document.getElementById('a'); ⏎ parent.document.body.appendChild(div);</span></li></ul></li></ul></li></ul></li></ul></li></ul><p>After the script is parsed, though, the <code><a href="interactive-elements.html#the-div-element">div</a></code> element
7191: and its child <code><a href="semantics.html#script">script</a></code> element are gone:</p>
7192:
1.159 mike 7193: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code></li></ul></li></ul><p>They are, at this point, in the <code>Document</code> of the
1.1 mike 7194: aforementioned outer <a href="browsers.html#browsing-context">browsing context</a>. However, the
7195: <a href="#stack-of-open-elements">stack of open elements</a> <em>still contains the
7196: <code><a href="interactive-elements.html#the-div-element">div</a></code> element</em>.</p>
7197:
7198: <p>Thus, when the second <code><a href="semantics.html#script">script</a></code> element is parsed, it
7199: is inserted <em>into the outer <code>Document</code>
7200: object</em>.</p>
7201:
7202: <p>This also means that the <a href="browsers.html#script-s-global-object">script's global object</a> is
7203: the outer <a href="browsers.html#browsing-context">browsing context</a>'s <code><a href="browsers.html#window">Window</a></code>
7204: object, <em>not</em> the <code><a href="browsers.html#window">Window</a></code> object inside the
1.159 mike 7205: <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code>.</p>
1.1 mike 7206:
7207: <p class="note">This isn't a security problem since the script that
7208: moves the <code><a href="interactive-elements.html#the-div-element">div</a></code> into the outer <code>Document</code> can
7209: only do so because they have the two <code>Document</code> object
1.159 mike 7210: have the same <a href="browsers.html#origin">origin</a>.</p>
1.1 mike 7211:
7212: <p>Thus, the first alert says "http://example.com/outer".</p>
7213:
7214: <p>Once the <code><a href="interactive-elements.html#the-div-element">div</a></code> element's end tag is parsed, the
7215: <code><a href="interactive-elements.html#the-div-element">div</a></code> element is popped off the stack, and so the next
7216: <code><a href="semantics.html#script">script</a></code> element is in the inner <code>Document</code>:</p>
7217:
1.159 mike 7218: <ul class="domTree"><li class="t1"><code><a href="semantics.html#the-html-element-0">html</a></code><ul><li class="t1"><code><a href="semantics.html#the-head-element-0">head</a></code></li><li class="t1"><code><a href="semantics.html#the-body-element-0">body</a></code><ul><li class="t1"><code><a href="semantics.html#script">script</a></code><ul><li class="t3"><code>#text</code>: <span title="">alert(document.URL);</span></li></ul></li></ul></li></ul></li></ul><p>This second alert will say "http://example.com/inner".</p>
1.1 mike 7219:
7220:
7221:
1.215 mike 7222: <h3 id="namespaces"><span class="secno">9.3 </span>Namespaces</h3>
1.1 mike 7223:
7224: <p>The <dfn id="html-namespace-0">HTML namespace</dfn> is: <code>http://www.w3.org/1999/xhtml</code></p>
7225:
7226: <p>The <dfn id="mathml-namespace">MathML namespace</dfn> is: <code>http://www.w3.org/1998/Math/MathML</code></p>
7227:
7228: <p>The <dfn id="svg-namespace">SVG namespace</dfn> is: <code>http://www.w3.org/2000/svg</code></p>
7229:
7230: <p>The <dfn id="xlink-namespace">XLink namespace</dfn> is: <code>http://www.w3.org/1999/xlink</code></p>
7231:
7232: <p>The <dfn id="xml-namespace">XML namespace</dfn> is: <code>http://www.w3.org/XML/1998/namespace</code></p>
7233:
7234: <p>The <dfn id="xmlns-namespace">XMLNS namespace</dfn> is: <code>http://www.w3.org/2000/xmlns/</code></p>
7235:
7236: <hr><p>Data mining tools and other user agents that perform operations
1.83 mike 7237: on <code><a href="iana-considerations.html#text-html">text/html</a></code> content without running scripts,
1.1 mike 7238: evaluating CSS or XPath expressions, or otherwise exposing the
7239: resulting DOM to arbitrary content, may "support namespaces" by just
7240: asserting that their DOM node analogues are in certain namespaces,
7241: without actually exposing the above strings.</p>
7242:
7243:
7244:
7245:
7246: <h3 id="serializing-html-fragments"><span class="secno">9.4 </span>Serializing HTML fragments</h3>
7247:
7248: <p>The following steps form the <dfn id="html-fragment-serialization-algorithm">HTML fragment serialization
7249: algorithm</dfn>. The algorithm takes as input a DOM
7250: <code>Element</code> or <code>Document</code>, referred to as <var title="">the node</var>, and either returns a string or raises an
7251: exception.</p>
7252:
7253: <p class="note">This algorithm serializes the <em>children</em> of
7254: the node being serialized, not the node itself.</p>
7255:
7256: <ol><li><p>Let <var title="">s</var> be a string, and initialize it to
7257: the empty string.</p></li>
7258:
7259: <li>
7260:
7261: <p>For each child node of <var title="">the node</var>, in
7262: <a href="infrastructure.html#tree-order">tree order</a>, run the following steps:
7263:
7264: </p><ol><li><p>Let <var title="">current node</var> be the child node
7265: being processed.</p></li>
7266:
7267: <li>
7268:
7269: <p>Append the appropriate string from the following list to
7270: <var title="">s</var>:</p>
7271:
7272: <dl class="switch"><dt>If <var title="">current node</var> is an <code title="">Element</code></dt>
7273:
7274: <dd>
7275:
7276: <p>Append a U+003C LESS-THAN SIGN (<code title=""><</code>)
7277: character, followed by the element's tag name. (For nodes
7278: created by the <a href="#html-parser">HTML parser</a> or <code title="">Document.createElement()</code>, the tag name will be
7279: lowercase.)</p>
7280:
7281: <p>For each attribute that the element has, append a U+0020
7282: SPACE character, the attribute's name (which, for attributes
7283: set by the <a href="#html-parser">HTML parser</a> or by <code title="">Element.setAttributeNode()</code> or <code title="">Element.setAttribute()</code>, will be lowercase), a
7284: U+003D EQUALS SIGN (<code title="">=</code>) character, a
7285: U+0022 QUOTATION MARK (<code title="">"</code>)
7286: character, the attribute's value, <a href="#escapingString" title="escaping a
7287: string">escaped as described below</a> in <i>attribute
7288: mode</i>, and a second U+0022 QUOTATION MARK (<code title="">"</code>) character.</p>
7289:
7290: <p>While the exact order of attributes is UA-defined, and may
7291: depend on factors such as the order that the attributes were
7292: given in the original markup, the sort order must be stable,
7293: such that consecutive invocations of this algorithm serialize an
7294: element's attributes in the same order.</p>
7295:
7296: <p>Append a U+003E GREATER-THAN SIGN (<code title="">></code>)
7297: character.</p>
7298:
7299: <p>If <var title="">current node</var> is an
1.5 mike 7300: <code><a href="the-canvas-element.html#the-area-element">area</a></code>, <code><a href="semantics.html#the-base-element">base</a></code>, <code><a href="obsolete.html#basefont">basefont</a></code>,
1.1 mike 7301: <code>bgsound</code>, <code><a href="semantics.html#the-br-element">br</a></code>, <code><a href="tabular-data.html#the-col-element">col</a></code>,
1.159 mike 7302: <code><a href="text-level-semantics.html#the-embed-element">embed</a></code>, <code><a href="obsolete.html#frame">frame</a></code>, <code><a href="semantics.html#the-hr-element">hr</a></code>,
7303: <code><a href="text-level-semantics.html#the-img-element">img</a></code>, <code><a href="forms.html#the-input-element">input</a></code>, <code><a href="forms.html#the-keygen-element">keygen</a></code>,
7304: <code><a href="semantics.html#the-link-element">link</a></code>, <code><a href="semantics.html#meta">meta</a></code>, <code><a href="text-level-semantics.html#the-param-element">param</a></code>,
1.5 mike 7305: <code><a href="obsolete.html#spacer">spacer</a></code>, or <code>wbr</code> element, then
1.1 mike 7306: continue on to the next child node at this point.</p> <!--
7307: also, i guess: image and isindex, but we don't list those
7308: because we don't consider those "elements", more "macros", and
7309: thus we should never serialize them -->
7310:
7311: <p>If <var title="">current node</var> is a <code><a href="semantics.html#the-pre-element">pre</a></code>,
1.42 mike 7312: <code><a href="forms.html#the-textarea-element">textarea</a></code>, or <code><a href="obsolete.html#listing">listing</a></code> element, append
1.1 mike 7313: a U+000A LINE FEED (LF) character.</p>
7314:
7315: <p>Append the value of running the <a href="#html-fragment-serialization-algorithm">HTML fragment
7316: serialization algorithm</a> on the <var title="">current
7317: node</var> element (thus recursing into this algorithm for
7318: that element), followed by a U+003C LESS-THAN SIGN (<code title=""><</code>) character, a U+002F SOLIDUS (<code title="">/</code>) character, the element's tag name again,
7319: and finally a U+003E GREATER-THAN SIGN (<code title="">></code>) character.</p>
7320:
7321: </dd>
7322:
7323:
7324: <dt>If <var title="">current node</var> is a <code title="">Text</code> or <code title="">CDATASection</code>
7325: node</dt>
7326:
7327: <dd>
7328:
1.19 mike 7329: <p>If the parent of <var title="">current node</var> is a
1.42 mike 7330: <code><a href="semantics.html#the-style-element">style</a></code>, <code><a href="semantics.html#script">script</a></code>, <code><a href="obsolete.html#xmp">xmp</a></code>,
1.159 mike 7331: <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code>, <code><a href="obsolete.html#noembed">noembed</a></code>,
1.222 mike 7332: <code><a href="obsolete.html#noframes">noframes</a></code>, or <code><a href="obsolete.html#plaintext">plaintext</a></code> element, or
7333: if the parent of <var title="">current node</var> is
7334: <code><a href="semantics.html#the-noscript-element">noscript</a></code> element and <a href="browsers.html#concept-n-script" title="concept-n-script">scripting is enabled</a> for the
7335: node, then append the value of <var title="">current
7336: node</var>'s <code title="">data</code> IDL attribute
7337: literally.</p>
1.1 mike 7338:
7339: <p>Otherwise, append the value of <var title="">current
1.192 mike 7340: node</var>'s <code title="">data</code> IDL attribute, <a href="#escapingString" title="escaping a string">escaped as described
1.1 mike 7341: below</a>.</p>
7342:
7343: </dd>
7344:
7345:
7346: <dt>If <var title="">current node</var> is a <code title="">Comment</code></dt>
7347:
7348: <dd>
7349:
7350: <p>Append the literal string <code><!--</code> (U+003C
7351: LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+002D HYPHEN-MINUS,
1.192 mike 7352: U+002D HYPHEN-MINUS), followed by the value of <var title="">current node</var>'s <code title="">data</code> IDL
1.1 mike 7353: attribute, followed by the literal string <code>--></code>
7354: (U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS, U+003E GREATER-THAN
7355: SIGN).</p>
7356:
7357: </dd>
7358:
7359:
7360: <dt>If <var title="">current node</var> is a <code title="">ProcessingInstruction</code></dt>
7361:
7362: <dd>
7363:
7364: <p>Append the literal string <code><?</code> (U+003C
7365: LESS-THAN SIGN, U+003F QUESTION MARK), followed by the value
1.192 mike 7366: of <var title="">current node</var>'s <code title="">target</code> IDL attribute, followed by a single
7367: U+0020 SPACE character, followed by the value of <var title="">current node</var>'s <code title="">data</code> IDL
1.1 mike 7368: attribute, followed by a single U+003E GREATER-THAN SIGN
7369: character ('>').</p>
7370:
7371: </dd>
7372:
7373:
7374: <dt>If <var title="">current node</var> is a <code title="">DocumentType</code></dt>
7375:
7376: <dd>
7377:
7378: <p>Append the literal string <code><!DOCTYPE</code> (U+003C
7379: LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+0044 LATIN CAPITAL
7380: LETTER D, U+004F LATIN CAPITAL LETTER O, U+0043 LATIN CAPITAL
7381: LETTER C, U+0054 LATIN CAPITAL LETTER T, U+0059 LATIN CAPITAL
7382: LETTER Y, U+0050 LATIN CAPITAL LETTER P, U+0045 LATIN CAPITAL
7383: LETTER E), followed by a space (U+0020 SPACE), followed by the
1.192 mike 7384: value of <var title="">current node</var>'s <code title="">name</code> IDL attribute, followed by the literal
1.1 mike 7385: string <code>></code> (U+003E GREATER-THAN SIGN).</p>
7386:
7387: </dd>
7388:
7389:
7390: </dl><p>Other node types (e.g. <code title="">Attr</code>) cannot
7391: occur as children of elements. If, despite this, they somehow do
7392: occur, this algorithm must raise an
7393: <code><a href="infrastructure.html#invalid_state_err">INVALID_STATE_ERR</a></code> exception.</p>
7394:
7395: </li>
7396:
7397: </ol></li>
7398:
7399: <li><p>The result of the algorithm is the string <var title="">s</var>.</p></li>
7400:
7401: </ol><p><dfn id="escapingString">Escaping a string</dfn> (for the
7402: purposes of the algorithm above) consists of replacing any
7403: occurrences of the "<code title="">&</code>" character by the
7404: string "<code title="">&amp;</code>", any occurrences of the
7405: U+00A0 NO-BREAK SPACE character by the string "<code title="">&nbsp;</code>", and, if the algorithm was invoked in
7406: the <i>attribute mode</i>, any occurrences of the "<code title="">"</code>" character by the string "<code title="">&quot;</code>", or if it was not, any occurrences of
7407: the "<code title=""><</code>" character by the string "<code title="">&lt;</code>", any occurrences of the "<code title="">></code>" character by the string "<code title="">&gt;</code>".</p>
7408:
7409: <p class="note">Entity reference nodes are <a href="infrastructure.html#entity-references">assumed to be expanded</a> by the user
7410: agent, and are therefore not covered in the algorithm above.</p>
7411:
7412: <p class="note">It is possible that the output of this algorithm, if
7413: parsed with an <a href="#html-parser">HTML parser</a>, will not return the
7414: original tree structure. For instance, if a <code><a href="forms.html#the-textarea-element">textarea</a></code>
7415: element to which a <code title="">Comment</code> node has been
7416: appended is serialized and the output is then reparsed, the comment
7417: will end up being displayed in the text field. Similarly, if, as a
7418: result of DOM manipulation, an element contains a comment that
7419: contains the literal string "<code title="">--></code>", then
7420: when the result of serializing the element is parsed, the comment
7421: will be truncated at that point and the rest of the comment will be
7422: interpreted as markup. More examples would be making a
7423: <code><a href="semantics.html#script">script</a></code> element contain a text node with the text string
7424: "<code></script></code>", or having a <code><a href="semantics.html#the-p-element">p</a></code> element that
7425: contains a <code><a href="semantics.html#the-ul-element">ul</a></code> element (as the <code><a href="semantics.html#the-ul-element">ul</a></code> element's
7426: <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> would imply the end
7427: tag for the <code><a href="semantics.html#the-p-element">p</a></code>).</p>
7428:
7429:
7430: <h3 id="parsing-html-fragments"><span class="secno">9.5 </span>Parsing HTML fragments</h3>
7431:
7432: <p>The following steps form the <dfn id="html-fragment-parsing-algorithm">HTML fragment parsing
7433: algorithm</dfn>. The algorithm optionally takes as input an
7434: <code>Element</code> node, referred to as the <var title="">context</var> element, which gives the context for the
7435: parser, as well as <var title="">input</var>, a string to parse, and
7436: returns a list of zero or more nodes.</p>
7437:
7438: <p class="note">Parts marked <dfn id="fragment-case">fragment case</dfn> in algorithms
7439: in the parser section are parts that only occur if the parser was
7440: created for the purposes of this algorithm (and with a <var title="">context</var> element). The algorithms have been annotated
7441: with such markings for informational purposes only; such markings
7442: have no normative weight. If it is possible for a condition
7443: described as a <a href="#fragment-case">fragment case</a> to occur even when the
7444: parser wasn't created for the purposes of handling this algorithm,
7445: then that is an error in the specification.</p>
7446:
7447: <ol><li>
7448:
7449: <p>Create a new <code>Document</code> node, and mark it as being
7450: an <a href="dom.html#html-documents" title="HTML documents">HTML document</a>.</p>
7451:
7452: </li>
7453:
7454: <li>
7455:
7456: <p>If there is a <var title="">context</var> element, and the
7457: <code>Document</code> of the <var title="">context</var> element
7458: is in <a href="dom.html#quirks-mode">quirks mode</a>, then let the <code>Document</code>
7459: be in <a href="dom.html#quirks-mode">quirks mode</a>. Otherwise, if there is a <var title="">context</var> element, and the <code>Document</code> of
7460: the <var title="">context</var> element is in <a href="dom.html#limited-quirks-mode">limited quirks
7461: mode</a>, then let the <code>Document</code> be in
7462: <a href="dom.html#limited-quirks-mode">limited quirks mode</a>. Otherwise, leave the
7463: <code>Document</code> in <a href="dom.html#no-quirks-mode">no quirks mode</a>.</p>
7464:
7465: </li>
7466:
7467: <li>
7468:
7469: <p>Create a new <a href="#html-parser">HTML parser</a>, and associate it with
7470: the just created <code>Document</code> node.</p>
7471:
7472: </li>
7473:
7474: <li>
7475:
7476: <p>If there is a <var title="">context</var> element, run these
7477: substeps:</p>
7478:
7479: <ol><li>
7480:
7481: <p>Set the <a href="#html-parser">HTML parser</a>'s <a href="#tokenization">tokenization</a>
7482: stage's <a href="#content-model-flag">content model flag</a> according to the <var title="">context</var> element, as follows:</p>
7483:
1.159 mike 7484: <dl class="switch"><dt>If it is a <code><a href="semantics.html#the-title-element-0">title</a></code> or <code><a href="forms.html#the-textarea-element">textarea</a></code>
1.1 mike 7485: element</dt>
7486:
7487: <dd>Set the <a href="#content-model-flag">content model flag</a> to
7488: the RCDATA state.</dd>
7489:
7490:
7491: <dt>If it is a <code><a href="semantics.html#the-style-element">style</a></code>, <code><a href="semantics.html#script">script</a></code>,
1.159 mike 7492: <code><a href="obsolete.html#xmp">xmp</a></code>, <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code>, <code><a href="obsolete.html#noembed">noembed</a></code>, or
1.5 mike 7493: <code><a href="obsolete.html#noframes">noframes</a></code> element</dt>
1.1 mike 7494:
7495: <dd>Set the <a href="#content-model-flag">content model flag</a> to
1.91 mike 7496: the RAWTEXT state.</dd>
1.1 mike 7497:
7498:
7499: <dt>If it is a <code><a href="semantics.html#the-noscript-element">noscript</a></code> element</dt>
7500:
7501: <dd>If the <a href="#scripting-flag">scripting flag</a> is enabled, set the
1.91 mike 7502: <a href="#content-model-flag">content model flag</a> to the RAWTEXT
1.1 mike 7503: state. Otherwise, set the <a href="#content-model-flag">content model flag</a> to the
7504: PCDATA state.</dd>
7505:
7506:
1.42 mike 7507: <dt>If it is a <code><a href="obsolete.html#plaintext">plaintext</a></code> element</dt>
1.1 mike 7508:
7509: <dd>Set the <a href="#content-model-flag">content model flag</a> to
7510: PLAINTEXT.</dd>
7511:
7512:
7513: <dt>Otherwise</dt>
7514:
7515: <dd>Leave the <a href="#content-model-flag">content model flag</a> in the PCDATA
7516: state.</dd>
7517:
7518: </dl></li>
7519:
7520: <li>
7521:
1.159 mike 7522: <p>Let <var title="">root</var> be a new <code><a href="semantics.html#the-html-element-0">html</a></code> element
1.1 mike 7523: with no attributes.</p>
7524:
7525: </li>
7526:
7527: <li>
7528:
7529: <p>Append the element <var title="">root</var> to the
7530: <code>Document</code> node created above.</p>
7531:
7532: </li>
7533:
7534: <li>
7535:
7536: <p>Set up the parser's <a href="#stack-of-open-elements">stack of open elements</a> so that
7537: it contains just the single element <var title="">root</var>.</p>
7538:
7539: </li>
7540:
7541: <li>
7542:
7543: <p><a href="#reset-the-insertion-mode-appropriately" title="reset the insertion mode appropriately">Reset the
7544: parser's insertion mode appropriately</a>.</p>
7545:
7546: <p class="note">The parser will reference the <var title="">context</var> element as part of that algorithm.</p>
7547:
7548: </li>
7549:
7550: <li>
7551:
7552: <p>Set the parser's <a href="#form-element-pointer"><code>form</code> element pointer</a>
7553: to the nearest node to the <var title="">context</var> element
7554: that is a <code><a href="forms.html#the-form-element">form</a></code> element (going straight up the
7555: ancestor chain, and including the element itself, if it is a
7556: <code><a href="forms.html#the-form-element">form</a></code> element), or, if there is no such
7557: <code><a href="forms.html#the-form-element">form</a></code> element, to null.</p>
7558:
7559: </li>
7560:
7561: </ol></li>
7562:
7563: <li>
7564:
7565: <p>Place into the <a href="#the-input-stream">input stream</a> for the <a href="#html-parser">HTML
7566: parser</a> just created the <var title="">input</var>. The
7567: encoding <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
7568: <i>irrelevant</i>.</p>
7569:
7570: </li>
7571:
7572: <li>
7573:
7574: <p>Start the parser and let it run until it has consumed all the
7575: characters just inserted into the input stream.</p>
7576:
7577: </li>
7578:
7579: <li>
7580:
7581: <p>If there is a <var title="">context</var> element, return the
7582: child nodes of <var title="">root</var>, in <a href="infrastructure.html#tree-order">tree
7583: order</a>.</p>
7584:
7585: <p>Otherwise, return the children of the <code>Document</code>
7586: object, in <a href="infrastructure.html#tree-order">tree order</a>.</p>
7587:
7588: </li>
7589:
1.123 mike 7590: </ol></div></body></html>
Webmaster
![[BACK]](/https/dev.w3.org/cvsweb/icons/back.gif){kind=icon}
Return to syntax.html CVS log ![[TXT]](/https/dev.w3.org/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/https/dev.w3.org/cvsweb/icons/dir.gif){kind=icon}
Up to [Public] / html5 / spec