Annotation of html5/spec/syntax.html, revision 1.172
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.4 mike 179: <h1>HTML 5</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.172 ! mike 185: </nav><p>This is revision 1.2866.</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,
342: U+0061 LATIN SMALL LETTER A .. U+007A LATIN SMALL LETTER Z, U+0041
343: LATIN CAPITAL LETTER A .. U+005A LATIN CAPITAL LETTER Z, and U+002D
344: HYPHEN-MINUS (<code>-</code>). In the HTML syntax, tag names may be
345: written with any mix of lower- and uppercase letters that, when
346: converted to all-lowercase, matches the element's tag name; tag
1.123 mike 347: 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
348: following format:</p><ol><li>The first character of a start tag must be a U+003C LESS-THAN
1.1 mike 349: SIGN (<code><</code>).</li>
350:
351: <li>The next few characters of a start tag must be the element's
352: <a href="#syntax-tag-name" title="syntax-tag-name">tag name</a>.</li>
353:
354: <li>If there are to be any attributes in the next step, there must
355: first be one or more <a href="infrastructure.html#space-character" title="space character">space
356: characters</a>.</li>
357:
358: <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
359: below. Attributes may be separated from each other by one or more
360: <a href="infrastructure.html#space-character" title="space character">space characters</a>.</li>
361:
362: <li>After the attributes, there may be one or more <a href="infrastructure.html#space-character" title="space character">space characters</a>. (Some attributes
363: are required to be followed by a space. See the <a href="#syntax-attributes" title="syntax-attributes">attributes section</a> below.)</li>
364:
365: <li>Then, if the element is one of the <a href="#void-elements">void elements</a>,
366: or if the element is a foreign element, then there may be a single
367: U+002F SOLIDUS (<code>/</code>) character. This character has no
368: effect on void elements, but on foreign elements it marks the start
369: tag as self-closing.</li>
370:
371: <li>Finally, start tags must be closed by a U+003E GREATER-THAN
372: SIGN (<code>></code>) character.</li>
373:
1.123 mike 374: </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
375: following format:</p><ol><li>The first character of an end tag must be a U+003C LESS-THAN
1.1 mike 376: SIGN (<code><</code>).</li>
377:
378: <li>The second character of an end tag must be a U+002F SOLIDUS
379: (<code>/</code>).</li>
380:
381: <li>The next few characters of an end tag must be the element's
382: <a href="#syntax-tag-name" title="syntax-tag-name">tag name</a>.</li>
383:
384: <li>After the tag name, there may be one or more <a href="infrastructure.html#space-character" title="space
385: character">space characters</a>.</li>
386:
387: <li>Finally, end tags must be closed by a U+003E GREATER-THAN
388: SIGN (<code>></code>) character.</li>
389:
1.123 mike 390: </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
391: 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 392: one or more characters other than the <a href="infrastructure.html#space-character" title="space
393: character">space characters</a>, U+0000 NULL, U+0022 QUOTATION
394: MARK ("), U+0027 APOSTROPHE ('), U+003E GREATER-THAN SIGN
395: (>), U+002F SOLIDUS (/), and U+003D EQUALS SIGN (=) characters,
396: the control characters, and any characters that are not defined by
397: Unicode. In the HTML syntax, attribute names may be written with any
398: mix of lower- and uppercase letters that are an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.123 mike 399: 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 400: 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 401: 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 402:
403: <dd>
404:
405: <p>Just the <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute
406: name</a>.</p>
407:
408: <div class="example">
409:
410: <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
411: the empty attribute syntax:</p>
412:
413: <pre><input <em>disabled</em>></pre>
414:
415: </div>
416:
417: <p>If an attribute using the empty attribute syntax is to be
418: followed by another attribute, then there must be a <a href="infrastructure.html#space-character">space
419: character</a> separating the two.</p>
420:
421: </dd>
422:
1.2 mike 423: <dt id="unquoted">Unquoted attribute value syntax</dt>
1.1 mike 424:
425: <dd>
426:
427: <p>The <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute name</a>,
428: followed by zero or more <a href="infrastructure.html#space-character" title="space character">space
429: characters</a>, followed by a single U+003D EQUALS SIGN
430: character, followed by zero or more <a href="infrastructure.html#space-character" title="space
431: character">space characters</a>, followed by the <a href="#syntax-attribute-value" title="syntax-attribute-value">attribute value</a>, which, in
432: addition to the requirements given above for attribute values,
433: must not contain any literal <a href="infrastructure.html#space-character" title="space character">space
434: characters</a>, any U+0022 QUOTATION MARK (<code>"</code>)
435: characters, U+0027 APOSTROPHE (<code>'</code>) characters,
436: U+003D EQUALS SIGN (<code>=</code>) characters, U+003C LESS-THAN
437: SIGN (<code><</code>) characters, or U+003E GREATER-THAN SIGN
438: (<code>></code>) characters, and must not be the empty
439: string.</p>
440:
441: <div class="example">
442:
443: <p>In the following example, the <code title="attr-input-value"><a href="forms.html#attr-input-value">value</a></code> attribute is given
444: with the unquoted attribute value syntax:</p>
445:
446: <pre><input <em>value=yes</em>></pre>
447:
448: </div>
449:
450: <p>If an attribute using the unquoted attribute syntax is to be
1.101 mike 451: followed by another attribute or by the optional U+002F SOLIDUS
452: (<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 453: must be a <a href="infrastructure.html#space-character">space character</a> separating the two.</p>
454:
455: </dd>
456:
457: <dt>Single-quoted attribute value syntax</dt>
458:
459: <dd>
460:
461: <p>The <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute name</a>,
462: followed by zero or more <a href="infrastructure.html#space-character" title="space character">space
463: characters</a>, followed by a single U+003D EQUALS SIGN
464: character, followed by zero or more <a href="infrastructure.html#space-character" title="space
465: character">space characters</a>, followed by a single U+0027
466: APOSTROPHE (<code>'</code>) character, followed by the <a href="#syntax-attribute-value" title="syntax-attribute-value">attribute value</a>, which, in
467: addition to the requirements given above for attribute values,
468: must not contain any literal U+0027 APOSTROPHE (<code>'</code>)
469: characters, and finally followed by a second single U+0027
470: APOSTROPHE (<code>'</code>) character.</p>
471:
472: <div class="example">
473:
474: <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
475: single-quoted attribute value syntax:</p>
476:
477: <pre><input <em>type='checkbox'</em>></pre>
478:
479: </div>
480:
481: <p>If an attribute using the single-quoted attribute syntax is to
482: be followed by another attribute, then there must be a <a href="infrastructure.html#space-character">space
483: character</a> separating the two.</p>
484:
485: </dd>
486:
487: <dt>Double-quoted attribute value syntax</dt>
488:
489: <dd>
490:
491: <p>The <a href="#syntax-attribute-name" title="syntax-attribute-name">attribute name</a>,
492: followed by zero or more <a href="infrastructure.html#space-character" title="space character">space
493: characters</a>, followed by a single U+003D EQUALS SIGN
494: character, followed by zero or more <a href="infrastructure.html#space-character" title="space
495: character">space characters</a>, followed by a single U+0022
496: QUOTATION MARK (<code>"</code>) character, followed by the <a href="#syntax-attribute-value" title="syntax-attribute-value">attribute value</a>, which, in
497: addition to the requirements given above for attribute values,
498: must not contain any literal U+0022 QUOTATION MARK
499: (<code>"</code>) characters, and finally followed by a second
500: single U+0022 QUOTATION MARK (<code>"</code>) character.</p>
501:
502: <div class="example">
503:
504: <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
505: double-quoted attribute value syntax:</p>
506:
507: <pre><input <em>name="be evil"</em>></pre>
508:
509: </div>
510:
511: <p>If an attribute using the double-quoted attribute syntax is to
512: be followed by another attribute, then there must be a <a href="infrastructure.html#space-character">space
513: character</a> separating the two.</p>
514:
515: </dd>
516:
517: </dl><p>There must never be two or more attributes on the same start tag
518: whose names are an <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> match for
1.123 mike 519: 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 520: is not present; it is implied, but it is still there. An HTML
1.159 mike 521: document always has a root <code><a href="semantics.html#the-html-element-0">html</a></code> element, even if the
1.1 mike 522: string <code title=""><html></code> doesn't appear anywhere in
1.159 mike 523: 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
524: 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
525: tag</a> may be omitted if the <code><a href="semantics.html#the-html-element-0">html</a></code> element is not
526: 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 527: element is empty, or--> if the first thing inside the
1.159 mike 528: <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
529: tag</a> may be omitted if the <code><a href="semantics.html#the-head-element-0">head</a></code> element is not
530: 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
531: 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 532: 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 533: 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 534: <code><a href="semantics.html#the-style-element">style</a></code> element. <!-- Note that even if the </head> end
535: tag is present, the parser makes <style> and <script> elements
536: between </head> and <body> end up in the <head> instead of implying
1.159 mike 537: 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
538: 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 539: 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 540: tag</a> may be omitted if the <code><a href="semantics.html#the-li-element">li</a></code> element is
541: immediately followed by another <code><a href="semantics.html#the-li-element">li</a></code> element or if there
1.123 mike 542: 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 543: tag</a> may be omitted if the <code><a href="semantics.html#the-dt-element">dt</a></code> element is
544: immediately followed by another <code><a href="semantics.html#the-dt-element">dt</a></code> element or a
1.123 mike 545: <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 546: tag</a> may be omitted if the <code><a href="semantics.html#the-dd-element">dd</a></code> element is
547: immediately followed by another <code><a href="semantics.html#the-dd-element">dd</a></code> element or a
548: <code><a href="semantics.html#the-dt-element">dt</a></code> element, or if there is no more content in the
1.123 mike 549: 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 550: tag</a> may be omitted if the <code><a href="semantics.html#the-p-element">p</a></code> element is
551: immediately followed by an <code><a href="semantics.html#the-address-element">address</a></code>,
552: <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 553: <!--v2DATAGRID <code>datagrid</code>,--> <code><a href="semantics.html#the-dialog-element">dialog</a></code>,
554: <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>,
555: <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>,
556: <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>,
557: <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>,
558: <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>,
559: <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 560: <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>,
561: element, or if there is no more content in the parent element and
1.123 mike 562: 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 563: tag</a> may be omitted if the <code><a href="text-level-semantics.html#the-rt-element">rt</a></code> element is
564: 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 565: 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 566: tag</a> may be omitted if the <code><a href="text-level-semantics.html#the-rp-element">rp</a></code> element is
567: 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 568: 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 569: <select>; commented out text below can handle the non-<select> case
1.123 mike 570: 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 571: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element <!--has an ancestor
572: <code>select</code> element and--> is immediately followed by
573: another <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, or if <!--all of the elements
574: that are ancestors of the <code>optgroup</code> element, up to and
575: including the first ancestor element that is not an
576: <code>optgroup</code> element, have no more content--> there is no
1.123 mike 577: more content in the parent element.</p><!-- so e.g. the max number of </optgroup>s are omitted here:
1.1 mike 578: <select><optgroup></select>
579: <p id=x><optgroup></optgroup>x</p>
580: <p id=x><optgroup><optgroup></optgroup></optgroup>x</p>
581: <p><optgroup id=x><optgroup></optgroup>x</p>
582: <p><optgroup><optgroup id=x>x</p>
1.123 mike 583: --><!-- </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 584: tag</a> may be omitted if the <code><a href="forms.html#the-option-element">option</a></code> element is
585: immediately followed by another <code><a href="forms.html#the-option-element">option</a></code> element, or if
586: it is immediately followed by an <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, or
1.123 mike 587: 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 588: first thing inside the <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element is a
589: <code><a href="tabular-data.html#the-col-element">col</a></code> element, and if the element is not immediately
590: 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 591: 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 592: <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element is not immediately followed by a
1.123 mike 593: <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 594: tag</a> may be omitted if the <code><a href="tabular-data.html#the-thead-element">thead</a></code> element is
595: 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 596: 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 597: first thing inside the <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element is a
598: <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, and if the element is not immediately
599: 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
600: <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element whose <a href="#syntax-end-tag" title="syntax-end-tag">end
601: tag</a> has been omitted. (It can't be omitted if the element is
1.123 mike 602: 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 603: tag</a> may be omitted if the <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element is
604: 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 605: 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 606: tag</a> may be omitted if the <code><a href="tabular-data.html#the-tfoot-element">tfoot</a></code> element is
607: immediately followed by a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element, or if there is
1.123 mike 608: 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 609: tag</a> may be omitted if the <code><a href="tabular-data.html#the-tr-element">tr</a></code> element is
610: immediately followed by another <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, or if there
1.123 mike 611: 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 612: tag</a> may be omitted if the <code><a href="tabular-data.html#the-td-element">td</a></code> element is
613: 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 614: 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 615: tag</a> may be omitted if the <code><a href="tabular-data.html#the-th-element">th</a></code> element is
616: 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 617: 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
618: 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
619: 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 620: elements, even though these elements are technically allowed inside
621: <code><a href="tabular-data.html#the-table-element">table</a></code> elements according to the content models
622: described in this specification. (If a <code><a href="tabular-data.html#the-tr-element">tr</a></code> element is
623: 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 624: 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 625: immediately after the <a href="#syntax-start-tag" title="syntax-start-tag">start
626: 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>
627: elements. This does not affect the processing of the element. The
628: otherwise optional U+000A LINE FEED (LF) character <em>must</em> be
629: included if the element's contents start with that character
630: (because otherwise the leading newline in the contents would be
1.123 mike 631: treated like the optional newline, and ignored).</p><div class="example">
1.1 mike 632: <p>The following two <code><a href="semantics.html#the-pre-element">pre</a></code> blocks are equivalent:</p>
633: <pre><pre>Hello</pre></pre>
634: <pre><pre><br>Hello</pre></pre>
1.123 mike 635: </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 636: occurrences of the string "<code title=""></</code>" (U+003C
637: LESS-THAN SIGN, U+002F SOLIDUS) followed by characters that
638: case-insensitively match the tag name of the element followed by one
639: of U+0009 CHARACTER TABULATION, U+000A LINE FEED (LF), U+000C FORM
640: FEED (FF), U+0020 SPACE, U+003E GREATER-THAN SIGN (>), or U+002F
1.123 mike 641: 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 642: 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
643: not itself in an <a href="#syntax-escape" title="syntax-escape">escaping text
644: span</a>, and ends at the next <a href="#syntax-escape-end" title="syntax-escape-end">escaping text span end</a>. There
645: cannot be any <a href="#syntax-charref" title="syntax-charref">character
646: references</a> inside an <a href="#syntax-escape" title="syntax-escape">escaping
647: text span</a> — sequences of characters that would look
648: like <a href="#syntax-charref" title="syntax-charref">character references</a> do not
1.123 mike 649: have special meaning.</p><p>An <dfn id="syntax-escape-start" title="syntax-escape-start">escaping text span
1.1 mike 650: start</dfn> is a part of <a href="#syntax-text" title="syntax-text">text</a> that
651: consists of the four character sequence "<code title=""><!--</code>" (U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
1.123 mike 652: 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 653: a part of <a href="#syntax-text" title="syntax-text">text</a> that consists of the
654: three character sequence "<code title="">--></code>" (U+002D
1.134 mike 655: 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 656: start</a> may share its U+002D HYPHEN-MINUS characters with its
657: corresponding <a href="#syntax-escape-end" title="syntax-escape-end">escaping text span
1.123 mike 658: end</a>.</p><p>The text in raw text elements and RCDATA elements must not have
1.91 mike 659: an <a href="#syntax-escape-start" title="syntax-escape-start">escaping text span start</a>
660: that is not followed by an <a href="#syntax-escape-end" title="syntax-escape-end">escaping
1.123 mike 661: 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 662: attributes, and comments. Text must consist of Unicode characters.
663: Text must not contain U+0000 characters. Text must not contain
664: permanently undefined Unicode characters. Text must not contain
665: control characters other than <a href="infrastructure.html#space-character" title="space character">space
666: characters</a>. Extra constraints are placed on what is and what
667: is not allowed in text based on where the text is to be put, as
1.123 mike 668: 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 669: represented either as U+000D CARRIAGE RETURN (CR) characters, U+000A
670: LINE FEED (LF) characters, or pairs of U+000D CARRIAGE RETURN (CR),
1.123 mike 671: 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 672: to escape characters that couldn't otherwise legally be included in
1.123 mike 673: <a href="#syntax-text" title="syntax-text">text</a>.</p><p>Character references must start with a U+0026 AMPERSAND
1.1 mike 674: (<code>&</code>). Following this, there are three possible kinds
1.123 mike 675: of character references:</p><dl><dt>Named character references</dt>
1.1 mike 676:
677: <dd>The ampersand must be followed by one of the names given in the
678: <a href="named-character-references.html#named-character-references">named character references</a> section, using the same
679: case. The name must be one that is terminated by a U+003B SEMICOLON
680: (<code title="">;</code>) character.</dd>
681:
682:
683: <dt>Decimal numeric character reference</dt>
684:
685: <dd>The ampersand must be followed by a U+0023 NUMBER SIGN
686: (<code>#</code>) character, followed by one or more digits in the
687: range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE, representing a
688: base-ten integer that itself is a Unicode code point that is
689: not U+0000, U+000D, in the range U+0080 .. U+009F, or in the range
690: 0xD800 .. 0xDFFF (surrogates). The digits must then be followed by
691: a U+003B SEMICOLON character (<code title="">;</code>).</dd>
692:
693:
694: <dt>Hexadecimal numeric character reference</dt>
695:
696: <dd>The ampersand must be followed by a U+0023 NUMBER SIGN
697: (<code>#</code>) character, which must be followed by either a
698: U+0078 LATIN SMALL LETTER X or a U+0058 LATIN CAPITAL LETTER X
699: character, which must then be followed by one or more digits in the
700: range U+0030 DIGIT ZERO .. U+0039 DIGIT NINE, U+0061 LATIN SMALL
701: LETTER A .. U+0066 LATIN SMALL LETTER F, and U+0041 LATIN CAPITAL
702: LETTER A .. U+0046 LATIN CAPITAL LETTER F, representing a
703: base-sixteen integer that itself is a Unicode code point that is
704: not U+0000, U+000D, in the range U+0080 .. U+009F, or in the range
705: 0xD800 .. 0xDFFF (surrogates). The digits must then be followed by
706: a U+003B SEMICOLON character (<code title="">;</code>).</dd>
707:
708: </dl><p>An <dfn id="syntax-ambiguous-ampersand" title="syntax-ambiguous-ampersand">ambiguous
709: ampersand</dfn> is a U+0026 AMPERSAND (<code>&</code>) character
710: that is followed by some <a href="#syntax-text" title="syntax-text">text</a> other
711: than a <a href="infrastructure.html#space-character">space character</a>, a U+003C LESS-THAN SIGN
712: character ('<'), or another U+0026 AMPERSAND (<code>&</code>)
1.123 mike 713: 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 714: the character sequence U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
715: MARK, U+005B LEFT SQUARE BRACKET, U+0043 LATIN CAPITAL LETTER C,
716: U+0044 LATIN CAPITAL LETTER D, U+0041 LATIN CAPITAL LETTER A, U+0054
717: LATIN CAPITAL LETTER T, U+0041 LATIN CAPITAL LETTER A, U+005B LEFT
718: SQUARE BRACKET (<code title=""><![CDATA[</code>). Following this
719: sequence, the CDATA section may have <a href="#syntax-text" title="syntax-text">text</a>, with the additional restriction
720: that the text must not contain the three character sequence U+005D
721: RIGHT SQUARE BRACKET, U+005D RIGHT SQUARE BRACKET, U+003E
722: GREATER-THAN SIGN (<code title="">]]></code>). Finally, the CDATA
723: section must be ended by the three character sequence U+005D RIGHT
724: SQUARE BRACKET, U+005D RIGHT SQUARE BRACKET, U+003E GREATER-THAN
1.159 mike 725: 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 726: four character sequence U+003C LESS-THAN SIGN, U+0021 EXCLAMATION
727: MARK, U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS (<code title=""><!--</code>). Following this sequence, the comment may
728: have <a href="#syntax-text" title="syntax-text">text</a>, with the additional
729: restriction that the text must not start with a single U+003E
730: GREATER-THAN SIGN ('>') character, nor start with a U+002D
731: HYPHEN-MINUS (<code title="">-</code>) character followed by a
732: U+003E GREATER-THAN SIGN ('>') character, nor contain two
733: consecutive U+002D HYPHEN-MINUS (<code title="">-</code>)
734: characters, nor end with a U+002D HYPHEN-MINUS (<code title="">-</code>) character. Finally, the comment must be ended by
735: the three character sequence U+002D HYPHEN-MINUS, U+002D
1.123 mike 736: HYPHEN-MINUS, U+003E GREATER-THAN SIGN (<code title="">--></code>).</p><div class="impl">
1.1 mike 737:
1.159 mike 738: <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 739:
740: <p><i>This section only applies to user agents, data mining tools,
741: and conformance checkers.</i></p>
742:
743: <p class="note">The rules for parsing XML documents into DOM trees
744: are covered by the next section, entitled "<a href="the-xhtml-syntax.html#the-xhtml-syntax">The XHTML
745: syntax</a>".</p>
746:
747: <p>For <a href="dom.html#html-documents">HTML documents</a>, user agents must use the parsing
748: rules described in this section to generate the DOM trees. Together,
749: these rules define what is referred to as the <dfn id="html-parser">HTML
750: parser</dfn>.</p>
751:
752: <div class="note">
753:
754: <p>While the HTML syntax described in this specification bears a
755: close resemblance to SGML and XML, it is a separate language with
756: its own parsing rules.</p>
757:
758: <p>Some earlier versions of HTML (in particular from HTML 2 to
759: HTML 4) were based on SGML and used SGML parsing rules. However, few
760: (if any) web browsers ever implemented true SGML parsing for HTML
761: documents; the only user agents to strictly handle HTML as an SGML
762: application have historically been validators. The resulting
763: confusion — with validators claiming documents to have one
764: representation while widely deployed Web browsers interoperably
765: implemented a different representation — has wasted decades
766: of productivity. This version of HTML thus returns to a non-SGML
767: basis.</p>
768:
769: <p>Authors interested in using SGML tools in their authoring
770: pipeline are encouraged to use XML tools and the XML serialization
771: of HTML.</p>
772:
773: </div>
774:
775: <p>This specification defines the parsing rules for HTML documents,
776: whether they are syntactically correct or not. Certain points in the
777: parsing algorithm are said to be <dfn id="parse-error" title="parse error">parse
778: errors</dfn>. The error handling for parse errors is well-defined:
779: user agents must either act as described below when encountering
780: such problems, or must abort processing at the first error that they
781: encounter for which they do not wish to apply the rules described
782: below.</p>
783:
784: <p>Conformance checkers must report at least one parse error
785: condition to the user if one or more parse error conditions exist in
786: the document and must not report parse error conditions if none
787: exist in the document. Conformance checkers may report more than one
788: parse error condition if more than one parse error conditions exist
789: in the document. Conformance checkers are not required to recover
790: from parse errors.</p>
791:
792: <p class="note">Parse errors are only errors with the
793: <em>syntax</em> of HTML. In addition to checking for parse errors,
794: conformance checkers will also verify that the document obeys all
795: the other conformance requirements described in this
796: specification.</p>
797:
798: <p>For the purposes of conformance checkers, if a resource is
799: determined to be in <a href="#syntax">the HTML syntax</a>, then it is an
800: <a href="dom.html#html-documents" title="HTML documents">HTML document</a>.</p>
801:
802:
803: <h4 id="overview-of-the-parsing-model"><span class="secno">9.2.1 </span>Overview of the parsing model</h4>
804:
805: <p>The input to the HTML parsing process consists of a stream of
806: Unicode characters, which is passed through a
807: <a href="#tokenization">tokenization</a> stage followed by a <a href="#tree-construction">tree
808: construction</a> stage. The output is a <code>Document</code>
809: object.</p>
810:
811: <p class="note">Implementations that <a href="infrastructure.html#non-scripted">do not
812: support scripting</a> do not have to actually create a DOM
813: <code>Document</code> object, but the DOM tree in such cases is
814: still used as the model for the rest of the specification.</p>
815:
816: <p>In the common case, the data handled by the tokenization stage
1.159 mike 817: comes from the network, but <a href="embedded-content-0.html#dynamic-markup-insertion" title="dynamic markup
818: 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 819:
820: <p><img alt="" src="images/parsing-model-overview.png"></p>
821:
822: <p id="nestedParsing">There is only one set of states for the
823: tokenizer stage and the tree construction stage, but the tree
824: construction stage is reentrant, meaning that while the tree
825: construction stage is handling one token, the tokenizer might be
826: resumed, causing further tokens to be emitted and processed before
827: the first token's processing is complete.</p>
828:
829: <div class="example">
830:
831: <p>In the following example, the tree construction stage will be
832: called upon to handle a "p" start tag token while handling the
833: "script" start tag token:</p>
834:
835: <pre>...
836: <script>
837: document.write('<p>');
838: </script>
839: ...</pre>
840:
841: </div>
842:
843: <p>To handle these cases, parsers have a <dfn id="script-nesting-level">script nesting
844: level</dfn>, which must be initially set to zero, and a <dfn id="parser-pause-flag">parser
845: pause flag</dfn>, which must be initially set to false.</p>
846:
847:
848:
849: <h4 id="the-input-stream"><span class="secno">9.2.2 </span>The <dfn>input stream</dfn></h4>
850:
851: <p>The stream of Unicode characters that comprises the input to the
852: tokenization stage will be initially seen by the user agent as a
853: stream of bytes (typically coming over the network or from the local
854: file system). The bytes encode the actual characters according to a
855: particular <em>character encoding</em>, which the user agent must
856: use to decode the bytes into characters.</p>
857:
858: <p class="note">For XML documents, the algorithm user agents must
859: use to determine the character encoding is given by the XML
1.104 mike 860: specification. This section does not apply to XML documents. <a href="references.html#refsXML">[XML]</a></p>
1.1 mike 861:
862:
1.168 mike 863: <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 864:
865: <p>In some cases, it might be impractical to unambiguously determine
866: the encoding before parsing the document. Because of this, this
867: specification provides for a two-pass mechanism with an optional
868: pre-scan. Implementations are allowed, as described below, to apply
869: a simplified parsing algorithm to whatever bytes they have available
870: before beginning to parse the document. Then, the real parser is
871: started, using a tentative encoding derived from this pre-parse and
872: other out-of-band metadata. If, while the document is being loaded,
873: the user agent discovers an encoding declaration that conflicts with
874: this information, then the parser can get reinvoked to perform a
875: parse of the document with the real encoding.</p>
876:
877: <p id="documentEncoding">User agents must use the following
878: algorithm (the <dfn id="encoding-sniffing-algorithm">encoding sniffing algorithm</dfn>) to determine
879: the character encoding to use when decoding a document in the first
880: pass. This algorithm takes as input any out-of-band metadata
881: available to the user agent (e.g. the <a href="infrastructure.html#content-type" title="Content-Type">Content-Type metadata</a> of the document)
882: and all the bytes available so far, and returns an encoding and a
883: <dfn id="concept-encoding-confidence" title="concept-encoding-confidence">confidence</dfn>. The
884: confidence is either <i>tentative</i>, <i>certain</i>, or
885: <i>irrelevant</i>. The encoding used, and whether the confidence in
886: that encoding is <i>tentative</i> or <i>certain</i>, is <a href="#meta-charset-during-parse">used during the parsing</a> to
887: determine whether to <a href="#change-the-encoding">change the encoding</a>. If no
888: encoding is necessary, e.g. because the parser is operating on a
889: stream of Unicode characters and doesn't have to use an encoding at
890: all, then the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
891: <i>irrelevant</i>.</p>
892:
893: <ol><li><p>If the transport layer specifies an encoding, and it is
894: supported, return that encoding with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
895: <i>certain</i>, and abort these steps.</p></li>
896:
897: <li><p>The user agent may wait for more bytes of the resource to be
898: available, either in this step or at any later step in this
899: algorithm. For instance, a user agent might wait 500ms or 512
900: bytes, whichever came first. In general preparsing the source to
901: find the encoding improves performance, as it reduces the need to
902: throw away the data structures used when parsing upon finding the
903: encoding information. However, if the user agent delays too long to
904: obtain data to determine the encoding, then the cost of the delay
905: could outweigh any performance improvements from the
906: preparse.</p></li>
907:
908: <li><p>For each of the rows in the following table, starting with
909: the first one and going down, if there are as many or more bytes
910: available than the number of bytes in the first column, and the
911: first bytes of the file match the bytes given in the first column,
912: then return the encoding given in the cell in the second column of
913: that row, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
914: <i>certain</i>, and abort these steps:</p>
915:
916: <!-- this table is present in several forms in this file; keep them in sync -->
917: <table><thead><tr><th>Bytes in Hexadecimal
918: </th><th>Encoding
919: </th></tr></thead><tbody><!-- nobody uses this
920: <tr>
921: <td>00 00 FE FF
922: <td>UTF-32BE
923: <tr>
924: <td>FF FE 00 00
925: <td>UTF-32LE
926: --><tr><td>FE FF
927: </td><td>UTF-16BE
928: </td></tr><tr><td>FF FE
929: </td><td>UTF-16LE
930: </td></tr><tr><td>EF BB BF
931: </td><td>UTF-8
932: <!-- nobody uses this
933: <tr>
934: <td>DD 73 66 73
935: <td>UTF-EBCDIC
936: -->
937: </td></tr></tbody></table><p class="note">This step looks for Unicode Byte Order Marks
938: (BOMs).</p></li>
939:
940: <li><p>Otherwise, the user agent will have to search for explicit
941: character encoding information in the file itself. This should
942: proceed as follows:
943:
944: </p><p>Let <var title="">position</var> be a pointer to a byte in the
945: input stream, initially pointing at the first byte. If at any
946: point during these substeps the user agent either runs out of
947: bytes or decides that scanning further bytes would not be
948: efficient, then skip to the next step of the overall character
949: encoding detection algorithm. User agents may decide that scanning
950: <em>any</em> bytes is not efficient, in which case these substeps
951: are entirely skipped.</p>
952:
953: <p>Now, repeat the following "two" steps until the algorithm
954: aborts (either because user agent aborts, as described above, or
955: because a character encoding is found):</p>
956:
957: <ol><li><p>If <var title="">position</var> points to:</p>
958:
959: <dl class="switch"><dt>A sequence of bytes starting with: 0x3C 0x21 0x2D 0x2D (ASCII '<!--')</dt>
960: <dd>
961:
962: <p>Advance the <var title="">position</var> pointer so that it
963: points at the first 0x3E byte which is preceded by two 0x2D
964: bytes (i.e. at the end of an ASCII '-->' sequence) and comes
965: after the 0x3C byte that was found. (The two 0x2D bytes can be
966: the same as the those in the '<!--' sequence.)</p>
967:
968: </dd>
969:
970: <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>
971: <dd>
972:
973: <ol><li><p>Advance the <var title="">position</var> pointer so
974: that it points at the next 0x09, 0x0A, 0x0C, 0x0D, 0x20, or
975: 0x2F byte (the one in sequence of characters matched
976: above).</p></li>
977:
978: <li><p><a href="#concept-get-attributes-when-sniffing" title="concept-get-attributes-when-sniffing">Get
979: an attribute</a> and its value. If no attribute was
980: sniffed, then skip this inner set of steps, and jump to the
981: second step in the overall "two step" algorithm.</p></li>
982:
983: <li><p>If the attribute's name is neither "<code title="">charset</code>" nor "<code title="">content</code>",
984: then return to step 2 in these inner steps.</p></li>
985:
986: <li><p>If the attribute's name is "<code title="">charset</code>", let <var title="">charset</var> be
987: the attribute's value, interpreted as a character
988: encoding.</p></li>
989:
990: <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
991: extracting an encoding from a Content-Type</a>, giving the
992: attribute's value as the string to parse. If an encoding is
993: returned, let <var title="">charset</var> be that
994: encoding. Otherwise, return to step 2 in these inner
995: steps.</p></li>
996:
997: <li><p>If <var title="">charset</var> is a UTF-16 encoding,
998: change the value of <var title="">charset</var> to
999: UTF-8.</p></li>
1000:
1001: <li><p>If <var title="">charset</var> is a supported
1002: character encoding, then return the given encoding, with
1003: <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1004: <i>tentative</i>, and abort all these steps.</p></li>
1005:
1006: <li><p>Otherwise, return to step 2 in these inner
1007: steps.</p></li>
1008:
1009: </ol></dd>
1010:
1011: <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>
1012: <dd>
1013:
1014: <ol><li><p>Advance the <var title="">position</var> pointer so
1015: that it points at the next 0x09 (ASCII TAB), 0x0A (ASCII LF),
1016: 0x0C (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E
1017: (ASCII '>') byte.</p></li>
1018:
1019: <li><p>Repeatedly <a href="#concept-get-attributes-when-sniffing" title="concept-get-attributes-when-sniffing">get an
1020: attribute</a> until no further attributes can be found,
1021: then jump to the second step in the overall "two step"
1022: algorithm.</p></li>
1023:
1024: </ol></dd>
1025:
1026: <dt>A sequence of bytes starting with: 0x3C 0x21 (ASCII '<!')</dt>
1027: <dt>A sequence of bytes starting with: 0x3C 0x2F (ASCII '</')</dt>
1028: <dt>A sequence of bytes starting with: 0x3C 0x3F (ASCII '<?')</dt>
1029: <dd>
1030:
1031: <p>Advance the <var title="">position</var> pointer so that it
1032: points at the first 0x3E byte (ASCII '>') that comes after the
1033: 0x3C byte that was found.</p>
1034:
1035: </dd>
1036:
1037: <dt>Any other byte</dt>
1038: <dd>
1039:
1040: <p>Do nothing with that byte.</p>
1041:
1042: </dd>
1043:
1044: </dl></li>
1045:
1046: <li>Move <var title="">position</var> so it points at the next
1047: byte in the input stream, and return to the first step of this
1048: "two step" algorithm.</li>
1049:
1050: </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
1051: attribute</dfn>, it means doing this:</p>
1052:
1053: <ol><li><p>If the byte at <var title="">position</var> is one of 0x09
1054: (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII FF), 0x0D (ASCII CR),
1055: 0x20 (ASCII space), or 0x2F (ASCII '/') then advance <var title="">position</var> to the next byte and redo this
1056: substep.</p></li>
1057:
1058: <li><p>If the byte at <var title="">position</var> is 0x3E (ASCII
1059: '>'), then abort the "get an attribute" algorithm. There isn't
1060: one.</p></li>
1061:
1062: <li><p>Otherwise, the byte at <var title="">position</var> is the
1063: start of the attribute name. Let <var title="">attribute
1064: name</var> and <var title="">attribute value</var> be the empty
1065: string.</p></li>
1066:
1067: <li><p><i>Attribute name</i>: Process the byte at <var title="">position</var> as follows:</p>
1068:
1069: <dl class="switch"><dt>If it is 0x3D (ASCII '='), and the <var title="">attribute
1070: name</var> is longer than the empty string</dt>
1071:
1072: <dd>Advance <var title="">position</var> to the next byte and
1073: jump to the step below labeled <i>value</i>.</dd>
1074:
1075: <dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII
1076: FF), 0x0D (ASCII CR), or 0x20 (ASCII space)</dt>
1077:
1078: <dd>Jump to the step below labeled <i>spaces</i>.</dd>
1079:
1080: <dt>If it is 0x2F (ASCII '/') or 0x3E (ASCII '>')</dt>
1081:
1082: <dd>Abort the "get an attribute" algorithm. The attribute's
1083: name is the value of <var title="">attribute name</var>, its
1084: value is the empty string.</dd>
1085:
1086: <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
1087: 'Z')</dt>
1088:
1089: <dd>Append the Unicode character with code point <span title=""><var title="">b</var>+0x20</span> to <var title="">attribute
1090: name</var> (where <var title="">b</var> is the value of the
1091: byte at <var title="">position</var>).</dd>
1092:
1093: <dt>Anything else</dt>
1094:
1095: <dd>Append the Unicode character with the same code point as the
1096: value of the byte at <var title="">position</var>) to <var title="">attribute name</var>. (It doesn't actually matter how
1097: bytes outside the ASCII range are handled here, since only
1098: ASCII characters can contribute to the detection of a character
1099: encoding.)</dd>
1100:
1101: </dl></li>
1102:
1103: <li><p>Advance <var title="">position</var> to the next byte and
1104: return to the previous step.</p></li>
1105:
1106: <li><p><i>Spaces</i>: If the byte at <var title="">position</var> is one of 0x09 (ASCII TAB), 0x0A (ASCII
1107: LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then
1108: advance <var title="">position</var> to the next byte, then,
1109: repeat this step.</p></li>
1110:
1111: <li><p>If the byte at <var title="">position</var> is
1112: <em>not</em> 0x3D (ASCII '='), abort the "get an attribute"
1113: algorithm. The attribute's name is the value of <var title="">attribute name</var>, its value is the empty
1114: string.</p></li>
1115:
1116: <li><p>Advance <var title="">position</var> past the 0x3D (ASCII
1117: '=') byte.</p></li>
1118:
1119: <li><p><i>Value:</i> If the byte at <var title="">position</var> is one of 0x09 (ASCII TAB), 0x0A (ASCII
1120: LF), 0x0C (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then
1121: advance <var title="">position</var> to the next byte, then,
1122: repeat this step.</p></li>
1123:
1124: <li><p>Process the byte at <var title="">position</var> as
1125: follows:</p>
1126:
1127: <dl class="switch"><dt>If it is 0x22 (ASCII '"') or 0x27 ("'")</dt>
1128:
1129: <dd>
1130:
1131: <ol><li>Let <var title="">b</var> be the value of the byte at
1132: <var title="">position</var>.</li>
1133:
1134: <li>Advance <var title="">position</var> to the next
1135: byte.</li>
1136:
1137: <li>If the value of the byte at <var title="">position</var>
1138: is the value of <var title="">b</var>, then advance <var title="">position</var> to the next byte and abort the "get
1139: an attribute" algorithm. The attribute's name is the value of
1140: <var title="">attribute name</var>, and its value is the
1141: value of <var title="">attribute value</var>.</li>
1142:
1143: <li>Otherwise, if the value of the byte at <var title="">position</var> is in the range 0x41 (ASCII 'A') to
1144: 0x5A (ASCII 'Z'), then append a Unicode character to <var title="">attribute value</var> whose code point is 0x20 more
1145: than the value of the byte at <var title="">position</var>.</li>
1146:
1147: <li>Otherwise, append a Unicode character to <var title="">attribute value</var> whose code point is the same as
1148: the value of the byte at <var title="">position</var>.</li>
1149:
1150: <li>Return to the second step in these substeps.</li>
1151:
1152: </ol></dd>
1153:
1154: <dt>If it is 0x3E (ASCII '>')</dt>
1155:
1156: <dd>Abort the "get an attribute" algorithm. The attribute's
1157: name is the value of <var title="">attribute name</var>, its
1158: value is the empty string.</dd>
1159:
1160:
1161: <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
1162: 'Z')</dt>
1163:
1164: <dd>Append the Unicode character with code point <span title=""><var title="">b</var>+0x20</span> to <var title="">attribute
1165: value</var> (where <var title="">b</var> is the value of the
1166: byte at <var title="">position</var>). Advance <var title="">position</var> to the next byte.</dd>
1167:
1168: <dt>Anything else</dt>
1169:
1170: <dd>Append the Unicode character with the same code point as the
1171: 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>
1172:
1173: </dl></li>
1174:
1175: <li><p>Process the byte at <var title="">position</var> as
1176: follows:</p>
1177:
1178: <dl class="switch"><dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0C (ASCII
1179: FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E (ASCII
1180: '>')</dt>
1181:
1182: <dd>Abort the "get an attribute" algorithm. The attribute's
1183: name is the value of <var title="">attribute name</var> and its
1184: value is the value of <var title="">attribute value</var>.</dd>
1185:
1186: <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII
1187: 'Z')</dt>
1188:
1189: <dd>Append the Unicode character with code point <span title=""><var title="">b</var>+0x20</span> to <var title="">attribute
1190: value</var> (where <var title="">b</var> is the value of the
1191: byte at <var title="">position</var>).</dd>
1192:
1193: <dt>Anything else</dt>
1194:
1195: <dd>Append the Unicode character with the same code point as the
1196: value of the byte at <var title="">position</var>) to <var title="">attribute value</var>.</dd>
1197:
1198: </dl></li>
1199:
1200: <li><p>Advance <var title="">position</var> to the next byte and
1201: return to the previous step.</p></li>
1202:
1203: </ol><p>For the sake of interoperability, user agents should not use a
1204: pre-scan algorithm that returns different results than the one
1205: described above. (But, if you do, please at least let us know, so
1206: that we can improve this algorithm and benefit everyone...)</p>
1207:
1208: </li>
1209:
1210: <li><p>If the user agent has information on the likely encoding for
1211: this page, e.g. based on the encoding of the page when it was last
1212: visited, then return that encoding, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1213: <i>tentative</i>, and abort these steps.</p></li>
1214:
1215: <li><p>The user agent may attempt to autodetect the character
1216: encoding from applying frequency analysis or other algorithms to
1217: the data stream. If autodetection succeeds in determining a
1218: character encoding, then return that encoding, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1.104 mike 1219: <i>tentative</i>, and abort these steps. <a href="references.html#refsUNIVCHARDET">[UNIVCHARDET]</a></p></li>
1.1 mike 1220:
1221: <li><p>Otherwise, return an implementation-defined or
1222: user-specified default character encoding, with the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a>
1223: <i>tentative</i>. In non-legacy environments, the more
1224: comprehensive <code title="">UTF-8</code> encoding is
1225: recommended. Due to its use in legacy content, <code title="">windows-1252</code> is recommended as a default in
1226: predominantly Western demographics instead. Since these encodings
1227: can in many cases be distinguished by inspection, a user agent may
1228: heuristically decide which to use as a default.</p></li>
1229:
1230: </ol><p>The <a href="dom.html#document-s-character-encoding">document's character encoding</a> must immediately
1231: be set to the value returned from this algorithm, at the same time
1232: as the user agent uses the returned value to select the decoder to
1233: use for the input stream.</p>
1234:
1235:
1236:
1237: <h5 id="preprocessing-the-input-stream"><span class="secno">9.2.2.2 </span>Preprocessing the input stream</h5>
1238:
1239: <p>Given an encoding, the bytes in the input stream must be
1240: converted to Unicode characters for the tokenizer, as described by
1241: the rules for that encoding, except that the leading U+FEFF BYTE
1242: ORDER MARK character, if any, must not be stripped by the encoding
1243: layer (it is stripped by the rule below).</p> <!-- this is to
1244: prevent two leading BOMs from being both stripped, once by the
1245: decoder, and once by the parser -->
1246:
1247: <p>Bytes or sequences of bytes in the original byte stream that
1248: could not be converted to Unicode characters must be converted to
1249: U+FFFD REPLACEMENT CHARACTER code points.</p>
1250:
1251: <p class="note">Bytes or sequences of bytes in the original byte
1252: stream that did not conform to the encoding specification
1253: (e.g. invalid UTF-8 byte sequences in a UTF-8 input stream) are
1254: errors that conformance checkers are expected to report.</p>
1255:
1256: <p>Any byte or sequences of bytes in the original byte stream that
1257: is <a href="infrastructure.html#misinterpreted-for-compatibility">misinterpreted for compatibility</a> is a <a href="#parse-error">parse
1258: error</a>.</p>
1259:
1260: <p>One leading U+FEFF BYTE ORDER MARK character must be ignored if
1261: any are present.</p>
1262:
1263: <p>All U+0000 NULL characters in the input must be replaced by
1264: U+FFFD REPLACEMENT CHARACTERs. Any occurrences of such characters is
1265: a <a href="#parse-error">parse error</a>.</p>
1266:
1267: <p>Any occurrences of any characters in the ranges U+0001 to U+0008,
1268: <!-- HT, LF allowed --> <!-- U+000B is in the next list --> <!-- FF,
1269: CR allowed --> U+000E to U+001F, <!-- ASCII allowed --> U+007F
1270: <!--to U+0084, (U+0085 NEL not allowed), U+0086--> to U+009F, U+D800
1271: to U+DFFF<!-- surrogates not allowed -->, U+FDD0 to U+FDEF, and
1272: characters U+000B, U+FFFE, U+FFFF, U+1FFFE, U+1FFFF, U+2FFFE,
1273: U+2FFFF, U+3FFFE, U+3FFFF, U+4FFFE, U+4FFFF, U+5FFFE, U+5FFFF,
1274: U+6FFFE, U+6FFFF, U+7FFFE, U+7FFFF, U+8FFFE, U+8FFFF, U+9FFFE,
1275: U+9FFFF, U+AFFFE, U+AFFFF, U+BFFFE, U+BFFFF, U+CFFFE, U+CFFFF,
1276: U+DFFFE, U+DFFFF, U+EFFFE, U+EFFFF, U+FFFFE, U+FFFFF, U+10FFFE, and
1277: U+10FFFF are <a href="#parse-error" title="parse error">parse errors</a>. (These
1278: are all control characters or permanently undefined Unicode
1279: characters.)</p>
1280:
1281: <p>U+000D CARRIAGE RETURN (CR) characters and U+000A LINE FEED (LF)
1282: characters are treated specially. Any CR characters that are
1283: followed by LF characters must be removed, and any CR characters not
1284: followed by LF characters must be converted to LF characters. Thus,
1285: newlines in HTML DOMs are represented by LF characters, and there
1286: are never any CR characters in the input to the
1287: <a href="#tokenization">tokenization</a> stage.</p>
1288:
1289: <p>The <dfn id="next-input-character">next input character</dfn> is the first character in the
1290: input stream that has not yet been <dfn id="consumed">consumed</dfn>. Initially,
1291: the <i><a href="#next-input-character">next input character</a></i> is the first character in the
1292: input. The <dfn id="current-input-character">current input character</dfn> is the last character
1293: to have been <i><a href="#consumed">consumed</a></i>.</p>
1294:
1295: <p>The <dfn id="insertion-point">insertion point</dfn> is the position (just before a
1296: character or just before the end of the input stream) where content
1.159 mike 1297: 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 1298: inserted. The insertion point is relative to the position of the
1299: character immediately after it, it is not an absolute offset into
1300: the input stream. Initially, the insertion point is
1.10 mike 1301: undefined.</p>
1.1 mike 1302:
1303: <p>The "EOF" character in the tables below is a conceptual character
1304: representing the end of the <a href="#the-input-stream">input stream</a>. If the parser
1.159 mike 1305: is a <a href="embedded-content-0.html#script-created-parser">script-created parser</a>, then the end of the
1.1 mike 1306: <a href="#the-input-stream">input stream</a> is reached when an <dfn id="explicit-eof-character">explicit "EOF"
1.159 mike 1307: 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 1308: consumed. Otherwise, the "EOF" character is not a real character in
1309: the stream, but rather the lack of any further characters.</p>
1310:
1311:
1312: <h5 id="changing-the-encoding-while-parsing"><span class="secno">9.2.2.3 </span>Changing the encoding while parsing</h5>
1313:
1314: <p>When the parser requires the user agent to <dfn id="change-the-encoding">change the
1315: encoding</dfn>, it must run the following steps. This might happen
1316: if the <a href="#encoding-sniffing-algorithm">encoding sniffing algorithm</a> described above
1317: failed to find an encoding, or if it found an encoding that was not
1318: the actual encoding of the file.</p>
1319:
1320: <ol><li>If the new encoding is identical or equivalent to the encoding
1321: that is already being used to interpret the input stream, then set
1322: the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1323: <i>certain</i> and abort these steps. This happens when the
1324: encoding information found in the file matches what the
1325: <a href="#encoding-sniffing-algorithm">encoding sniffing algorithm</a> determined to be the
1326: encoding, and in the second pass through the parser if the first
1327: pass found that the encoding sniffing algorithm described in the
1328: earlier section failed to find the right encoding.</li>
1329:
1330: <li>If the encoding that is already being used to interpret the
1331: input stream is a UTF-16 encoding, then set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1332: <i>certain</i> and abort these steps. The new encoding is ignored;
1333: if it was anything but the same encoding, then it would be clearly
1334: incorrect.</li>
1335:
1336: <li>If the new encoding is a UTF-16 encoding, change it to
1337: UTF-8.</li>
1338:
1339: <li>If all the bytes up to the last byte converted by the current
1340: decoder have the same Unicode interpretations in both the current
1341: encoding and the new encoding, and if the user agent supports
1342: changing the converter on the fly, then the user agent may change
1343: to the new converter for the encoding on the fly. Set the
1344: <a href="dom.html#document-s-character-encoding">document's character encoding</a> and the encoding used to
1345: convert the input stream to the new encoding, set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1346: <i>certain</i>, and abort these steps.</li>
1347:
1348: <li>Otherwise, <a href="history.html#navigate">navigate</a> to the document again, with
1349: <a href="history.html#replacement-enabled">replacement enabled</a>, and using the same <a href="history.html#source-browsing-context">source
1350: browsing context</a>, but this time skip the <a href="#encoding-sniffing-algorithm">encoding
1351: sniffing algorithm</a> and instead just set the encoding to the
1352: new encoding and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1353: <i>certain</i>. Whenever possible, this should be done without
1354: actually contacting the network layer (the bytes should be
1355: re-parsed from memory), even if, e.g., the document is marked as
1356: not being cacheable. If this is not possible and contacting the
1357: network layer would involve repeating a request that uses a method
1358: other than HTTP GET (<a href="infrastructure.html#concept-http-equivalent-get" title="concept-http-equivalent-get">or
1359: equivalent</a> for non-HTTP URLs), then instead set the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> to
1360: <i>certain</i> and ignore the new encoding. The resource will be
1361: misinterpreted. User agents may notify the user of the situation,
1362: to aid in application development.</li>
1363:
1364: </ol><h4 id="parse-state"><span class="secno">9.2.3 </span>Parse state</h4>
1365:
1366: <h5 id="the-insertion-mode"><span class="secno">9.2.3.1 </span>The insertion mode</h5>
1367:
1368: <p>The <dfn id="insertion-mode">insertion mode</dfn> is a state variable that controls
1369: the primary operation of the tree construction stage.</p>
1370:
1371: <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
1372: "<a href="#the-before-html-insertion-mode" title="insertion mode: before html">before html</a>",
1373: "<a href="#the-before-head-insertion-mode" title="insertion mode: before head">before head</a>",
1374: "<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 1375: "<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 1376: "<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>",
1377: "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table body</a>",
1378: "<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
1379: table</a>", "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in
1380: foreign content</a>", "<a href="#parsing-main-afterbody" title="insertion mode: after
1381: body">after body</a>", "<a href="#parsing-main-inframeset" title="insertion mode: in
1382: frameset">in frameset</a>", "<a href="#parsing-main-afterframeset" title="insertion mode: after
1383: frameset">after frameset</a>", "<a href="#the-after-after-body-insertion-mode" title="insertion mode:
1384: after after body">after after body</a>", and "<a href="#the-after-after-frameset-insertion-mode" title="insertion mode: after after frameset">after after
1385: frameset</a>" during the course of the parsing, as described in
1386: the <a href="#tree-construction">tree construction</a> stage. The insertion mode affects
1387: how tokens are processed and whether CDATA sections are
1388: supported.</p>
1389:
1390: <p>Seven of these modes, namely "<a href="#parsing-main-inhead" title="insertion mode: in
1391: head">in head</a>", "<a href="#parsing-main-inbody" title="insertion mode: in body">in
1392: body</a>", "<a href="#parsing-main-intable" title="insertion mode: in table">in
1393: table</a>", "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
1394: body</a>", "<a href="#parsing-main-intr" title="insertion mode: in row">in row</a>",
1395: "<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
1396: that the other modes defer to them at various times. When the
1397: algorithm below says that the user agent is to do something
1398: "<dfn id="using-the-rules-for">using the rules for</dfn> the <var title="">m</var> insertion
1399: mode", where <var title="">m</var> is one of these modes, the user
1400: agent must use the rules described under the <var title="">m</var>
1401: <a href="#insertion-mode">insertion mode</a>'s section, but must leave the
1402: <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>
1403: to a new value.</p>
1404:
1405: <p>When the insertion mode is switched to "<a href="#parsing-main-incdata" title="insertion
1.91 mike 1406: 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 1407: <dfn id="original-insertion-mode">original insertion mode</dfn> is also set. This is the
1408: insertion mode to which the tree construction stage will return.</p>
1409:
1410: <p>When the insertion mode is switched to "<a href="#parsing-main-inforeign" title="insertion
1411: mode: in foreign content">in foreign content</a>", the
1412: <dfn id="secondary-insertion-mode">secondary insertion mode</dfn> is also set. This secondary mode
1413: is used within the rules for the "<a href="#parsing-main-inforeign" title="insertion mode: in
1414: foreign content">in foreign content</a>" mode to handle HTML
1415: (i.e. not foreign) content.</p>
1416:
1417: <hr><p>When the steps below require the UA to <dfn id="reset-the-insertion-mode-appropriately">reset the insertion
1418: mode appropriately</dfn>, it means the UA must follow these
1419: steps:</p>
1420:
1421: <ol><li>Let <var title="">last</var> be false.</li>
1422:
1423: <li>Let <var title="">node</var> be the last node in the
1424: <a href="#stack-of-open-elements">stack of open elements</a>.</li>
1425:
1426: <li>If <var title="">node</var> is the first node in the stack of
1427: open elements, then set <var title="">last</var> to true and set
1428: <var title="">node</var> to the <var title="">context</var>
1429: element. (<a href="#fragment-case">fragment case</a>)</li>
1430:
1431: <li>If <var title="">node</var> is a <code><a href="forms.html#the-select-element">select</a></code> element,
1432: 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
1433: steps. (<a href="#fragment-case">fragment case</a>)</li>
1434:
1435: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-td-element">td</a></code> or
1436: <code><a href="tabular-data.html#the-th-element">th</a></code> element and <var title="">last</var> is false, then
1437: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intd" title="insertion
1438: mode: in cell">in cell</a>" and abort these steps.</li>
1439:
1440: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, then
1441: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intr" title="insertion
1442: mode: in row">in row</a>" and abort these steps.</li>
1443:
1444: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code>,
1445: <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
1446: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intbody" title="insertion mode: in
1447: table body">in table body</a>" and abort these steps.</li>
1448:
1449: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-caption-element">caption</a></code> element,
1450: 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
1451: these steps.</li>
1452:
1453: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-colgroup-element">colgroup</a></code> element,
1454: 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
1455: abort these steps. (<a href="#fragment-case">fragment case</a>)</li>
1456:
1457: <li>If <var title="">node</var> is a <code><a href="tabular-data.html#the-table-element">table</a></code> element,
1458: 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
1459: steps.</li>
1460:
1461: <li>If <var title="">node</var> is an element from the <a href="#mathml-namespace">MathML
1462: namespace</a> or the <a href="#svg-namespace">SVG namespace</a>, then switch the
1463: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inforeign" title="insertion mode: in
1464: foreign content">in foreign content</a>", let the
1465: <a href="#secondary-insertion-mode">secondary insertion mode</a> be "<a href="#parsing-main-inbody" title="insertion
1466: mode: in body">in body</a>", and abort these steps.</li>
1467:
1.159 mike 1468: <li>If <var title="">node</var> is a <code><a href="semantics.html#the-head-element-0">head</a></code> element,
1.1 mike 1469: 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
1470: these steps. (<a href="#fragment-case">fragment case</a>)</li> <!-- This is only
1471: here for now in case people think that the spec accidentally
1472: omitted it and try to "fix" it. Note that noscript-in-head is also
1473: handled this way. This is all intentional. The only thing it
1474: doesn't handle is the scripting-disabled fragment parsing case for
1475: a <head> element containing a <noscript> which itself contains
1476: something other than a <link> or a <style> element; you'd expect
1477: that to break out of the <noscript> but it doesn't. This is an edge
1478: case that doesn't affect the spec, since the algorithm for fragment
1479: parsing is only used for innerHTML/outerHTML/insertAdjacentHTML(),
1480: where we know scripting is enabled. (XXX except maybe if innerHTML
1481: is set from another browsing context on a document with designMode
1482: set?) -->
1483:
1.159 mike 1484: <li>If <var title="">node</var> is a <code><a href="semantics.html#the-body-element-0">body</a></code> element,
1.1 mike 1485: 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
1486: steps.</li>
1487:
1.5 mike 1488: <li>If <var title="">node</var> is a <code><a href="obsolete.html#frameset">frameset</a></code> element,
1.1 mike 1489: 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
1490: these steps. (<a href="#fragment-case">fragment case</a>)</li>
1491:
1.159 mike 1492: <li>If <var title="">node</var> is an <code><a href="semantics.html#the-html-element-0">html</a></code> element,
1.1 mike 1493: then: if the <a href="#head-element-pointer"><code title="">head</code> element
1494: pointer</a> is null, switch the <a href="#insertion-mode">insertion mode</a> to
1495: "<a href="#the-before-head-insertion-mode" title="insertion mode: before head">before head</a>",
1496: 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
1497: case, abort these steps. (<a href="#fragment-case">fragment case</a>)</li> <!-- XXX
1498: can the head element pointer ever be non-null when we're going
1499: through these steps? -->
1500:
1501: <li>If <var title="">last</var> is true, then switch the
1502: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inbody" title="insertion mode: in
1503: body">in body</a>" and abort these steps. (<a href="#fragment-case">fragment
1504: case</a>)</li>
1505:
1506: <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
1507: elements</a>.</li>
1508:
1509: <li>Return to step 3.</li>
1510:
1511: </ol><h5 id="the-stack-of-open-elements"><span class="secno">9.2.3.2 </span>The stack of open elements</h5>
1512:
1513: <p>Initially, the <dfn id="stack-of-open-elements">stack of open elements</dfn> is empty. The
1514: stack grows downwards; the topmost node on the stack is the first
1515: one added to the stack, and the bottommost node of the stack is the
1516: most recently added node in the stack (notwithstanding when the
1517: stack is manipulated in a random access fashion as part of <a href="#adoptionAgency">the handling for misnested tags</a>).</p>
1518:
1519: <p>The "<a href="#the-before-html-insertion-mode" title="insertion mode: before html">before
1520: html</a>" <a href="#insertion-mode">insertion mode</a> creates the
1.159 mike 1521: <code><a href="semantics.html#the-html-element-0">html</a></code> root element node, which is then added to the
1.1 mike 1522: stack.</p>
1523:
1524: <p>In the <a href="#fragment-case">fragment case</a>, the <a href="#stack-of-open-elements">stack of open
1.159 mike 1525: elements</a> is initialized to contain an <code><a href="semantics.html#the-html-element-0">html</a></code>
1.1 mike 1526: element that is created as part of <a href="#html-fragment-parsing-algorithm" title="html fragment
1527: parsing algorithm">that algorithm</a>. (The <a href="#fragment-case">fragment
1528: case</a> skips the "<a href="#the-before-html-insertion-mode" title="insertion mode: before
1529: html">before html</a>" <a href="#insertion-mode">insertion mode</a>.)</p>
1530:
1.159 mike 1531: <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 1532: node of the stack. It never gets popped off the stack.</p>
1533:
1534: <p>The <dfn id="current-node">current node</dfn> is the bottommost node in this
1535: stack.</p>
1536:
1537: <p>The <dfn id="current-table">current table</dfn> is the last <code><a href="tabular-data.html#the-table-element">table</a></code>
1538: element in the <a href="#stack-of-open-elements">stack of open elements</a>, if there is
1539: 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
1540: open elements</a> (<a href="#fragment-case">fragment case</a>), then the
1541: <a href="#current-table">current table</a> is the first element in the <a href="#stack-of-open-elements">stack
1.159 mike 1542: of open elements</a> (the <code><a href="semantics.html#the-html-element-0">html</a></code> element).</p>
1.1 mike 1543:
1544: <p>Elements in the stack fall into the following categories:</p>
1545:
1546: <dl><dt><dfn id="special">Special</dfn></dt>
1547:
1548: <dd><p>The following HTML elements have varying levels of special
1549: 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>,
1550: <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 1551: <code><a href="obsolete.html#basefont">basefont</a></code>, <code>bgsound</code>,
1.159 mike 1552: <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 1553: <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 1554: <code><a href="interactive-elements.html#the-command">command</a></code>, <!--v2DDATAGRID--><code>datagrid</code>,
1555: <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>,
1556: <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 1557: <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>,
1558: <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 1559: <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>,
1560: <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 1561: <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>,
1562: <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 1563: <code>image</code>, (commented out because this isn't an element
1564: that can end up on the stack, so it doesn't matter) -->
1.159 mike 1565: <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 1566: <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>,
1567: <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>,
1568: <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 1569: <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 1570: <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>,
1571: <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>,
1572: <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 1573: <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.86 mike 1574: <code><a href="tabular-data.html#the-tr-element">tr</a></code>, <code><a href="semantics.html#the-ul-element">ul</a></code>, and <code>wbr</code>.</p></dd>
1.1 mike 1575:
1576: <dt><dfn id="scoping">Scoping</dfn></dt>
1577: <dd><p>The following HTML elements introduce new <a href="#has-an-element-in-scope" title="has
1578: an element in scope">scopes</a> for various parts of the
1.5 mike 1579: 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 1580: <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>,
1581: <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 1582: <code><a href="tabular-data.html#the-th-element">th</a></code>, and SVG's <code>foreignObject</code>.</p></dd>
1583:
1584: <dt><dfn id="formatting">Formatting</dfn></dt>
1585: <dd><p>The following HTML elements are those that end up in the
1586: <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 1587: <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>,
1588: <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>,
1589: <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>,
1590: <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
1591: <code><a href="obsolete.html#u">u</a></code>.</p></dd>
1.1 mike 1592:
1593: <dt><dfn id="phrasing">Phrasing</dfn></dt>
1594: <dd><p>All other elements found while parsing an HTML
1595: document.</p></dd>
1596:
1597: </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
1598: the following algorithm terminates in a match state:</p>
1599:
1600: <ol><li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
1601: node</a> (the bottommost node of the stack).</p></li>
1602:
1603: <li><p>If <var title="">node</var> is the target node, terminate in
1604: a match state.</p></li>
1605:
1606: <li><p>Otherwise, if <var title="">node</var> is one of the
1607: following elements, terminate in a failure state:</p>
1.5 mike 1608: <ul class="brief"><li><code><a href="obsolete.html#the-applet-element">applet</a></code> in the HTML namespace</li>
1.1 mike 1609: <li><code><a href="tabular-data.html#the-caption-element">caption</a></code> in the HTML namespace</li>
1.159 mike 1610: <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 1611: <li><code><a href="tabular-data.html#the-table-element">table</a></code> in the HTML namespace</li>
1612: <li><code><a href="tabular-data.html#the-td-element">td</a></code> in the HTML namespace</li>
1613: <li><code><a href="tabular-data.html#the-th-element">th</a></code> in the HTML namespace</li>
1614: <li><code><a href="forms.html#the-button-element">button</a></code> in the HTML namespace</li>
1.159 mike 1615: <li><code><a href="obsolete.html#the-marquee-element">marquee</a></code> in the HTML namespace</li>
1616: <li><code><a href="text-level-semantics.html#the-object-element">object</a></code> in the HTML namespace</li>
1.1 mike 1617: <li><code title="">foreignObject</code> in the SVG namespace</li>
1618: </ul></li>
1619:
1620: <li><p>Otherwise, set <var title="">node</var> to the previous
1621: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to step
1622: 2. (This will never fail, since the loop will always terminate in
1623: the previous step if the top of the stack — an
1.159 mike 1624: <code><a href="semantics.html#the-html-element-0">html</a></code> element — is reached.)</p></li>
1.1 mike 1625:
1626: </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
1627: scope</em></dfn> when the following algorithm terminates in a match
1628: state:</p>
1629:
1630: <ol><li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
1631: node</a> (the bottommost node of the stack).</p></li>
1632:
1633: <li><p>If <var title="">node</var> is the target node, terminate in
1634: a match state.</p></li>
1635:
1636: <li><p>Otherwise, if <var title="">node</var> is one of the
1637: following elements, terminate in a failure state:</p>
1.159 mike 1638: <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 1639: <li><code><a href="tabular-data.html#the-table-element">table</a></code> in the HTML namespace</li>
1640: </ul></li>
1641:
1642: <li><p>Otherwise, set <var title="">node</var> to the previous
1643: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to step
1644: 2. (This will never fail, since the loop will always terminate in
1645: the previous step if the top of the stack — an
1.159 mike 1646: <code><a href="semantics.html#the-html-element-0">html</a></code> element — is reached.)</p></li>
1.1 mike 1647:
1648: </ol><p>Nothing happens if at any time any of the elements in the
1649: <a href="#stack-of-open-elements">stack of open elements</a> are moved to a new location in,
1650: or removed from, the <code>Document</code> tree. In particular, the
1651: stack is not changed in this situation. This can cause, amongst
1652: other strange effects, content to be appended to nodes that are no
1653: longer in the DOM.</p>
1654:
1655: <p class="note">In some cases (namely, when <a href="#adoptionAgency">closing misnested formatting elements</a>),
1656: the stack is manipulated in a random-access fashion.</p>
1657:
1658:
1659: <h5 id="the-list-of-active-formatting-elements"><span class="secno">9.2.3.3 </span>The list of active formatting elements</h5>
1660:
1661: <p>Initially, the <dfn id="list-of-active-formatting-elements">list of active formatting elements</dfn> is
1662: empty. It is used to handle mis-nested <a href="#formatting" title="formatting">formatting element tags</a>.</p>
1663:
1664: <p>The list contains elements in the <a href="#formatting">formatting</a>
1665: category, and scope markers. The scope markers are inserted when
1.159 mike 1666: 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 1667: elements, marquees, table cells, and table captions, and are used to
1.5 mike 1668: prevent formatting from "leaking" <em>into</em> <code><a href="obsolete.html#the-applet-element">applet</a></code>
1.159 mike 1669: elements, buttons, <code><a href="text-level-semantics.html#the-object-element">object</a></code> elements, marquees, and
1.1 mike 1670: tables.</p>
1671:
1672: <p class="note">The scope markers are unrelated to the concept of an
1673: element being <a href="#has-an-element-in-scope" title="has an element in scope">in
1674: scope</a>.</p>
1675:
1676: <p>In addition, each element in the <a href="#list-of-active-formatting-elements">list of active formatting
1677: elements</a> is associated with the token for which it was
1678: created, so that further elements can be created for that token if
1679: necessary.</p>
1680:
1681: <p>When the steps below require the UA to <dfn id="reconstruct-the-active-formatting-elements">reconstruct the
1682: active formatting elements</dfn>, the UA must perform the following
1683: steps:</p>
1684:
1685: <ol><li>If there are no entries in the <a href="#list-of-active-formatting-elements">list of active formatting
1686: elements</a>, then there is nothing to reconstruct; stop this
1687: algorithm.</li>
1688:
1689: <li>If the last (most recently added) entry in the <a href="#list-of-active-formatting-elements">list of
1690: active formatting elements</a> is a marker, or if it is an
1691: element that is in the <a href="#stack-of-open-elements">stack of open elements</a>, then
1692: there is nothing to reconstruct; stop this algorithm.</li>
1693:
1694: <li>Let <var title="">entry</var> be the last (most recently added)
1695: element in the <a href="#list-of-active-formatting-elements">list of active formatting
1696: elements</a>.</li>
1697:
1698: <li>If there are no entries before <var title="">entry</var> in the
1699: <a href="#list-of-active-formatting-elements">list of active formatting elements</a>, then jump to step
1700: 8.</li>
1701:
1702: <li>Let <var title="">entry</var> be the entry one earlier than
1703: <var title="">entry</var> in the <a href="#list-of-active-formatting-elements">list of active formatting
1704: elements</a>.</li>
1705:
1706: <li>If <var title="">entry</var> is neither a marker nor an element
1707: that is also in the <a href="#stack-of-open-elements">stack of open elements</a>, go to step
1708: 4.</li>
1709:
1710: <li>Let <var title="">entry</var> be the element one later than
1711: <var title="">entry</var> in the <a href="#list-of-active-formatting-elements">list of active formatting
1712: elements</a>.</li>
1713:
1714: <li><a href="#create-an-element-for-the-token">Create an element for the token</a> for which the
1715: element <var title="">entry</var> was created, to obtain <var title="">new element</var>.</li>
1716:
1717: <li>Append <var title="">new element</var> to the <a href="#current-node">current
1718: node</a> and push it onto the <a href="#stack-of-open-elements">stack of open
1719: elements</a> so that it is the new <a href="#current-node">current
1720: node</a>.</li>
1721:
1722: <li>Replace the entry for <var title="">entry</var> in the list
1723: with an entry for <var title="">new element</var>.</li>
1724:
1725: <li>If the entry for <var title="">new element</var> in the
1726: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> is not the last
1727: entry in the list, return to step 7.</li>
1728:
1729: </ol><p>This has the effect of reopening all the formatting elements that
1730: were opened in the current body, cell, or caption (whichever is
1731: youngest) that haven't been explicitly closed.</p>
1732:
1733: <p class="note">The way this specification is written, the
1734: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> always consists of
1735: elements in chronological order with the least recently added
1736: element first and the most recently added element last (except for
1737: while steps 8 to 11 of the above algorithm are being executed, of
1738: course).</p>
1739:
1740: <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
1741: active formatting elements up to the last marker</dfn>, the UA must
1742: perform the following steps:</p>
1743:
1744: <ol><li>Let <var title="">entry</var> be the last (most recently added)
1745: entry in the <a href="#list-of-active-formatting-elements">list of active formatting elements</a>.</li>
1746:
1747: <li>Remove <var title="">entry</var> from the <a href="#list-of-active-formatting-elements">list of active
1748: formatting elements</a>.</li>
1749:
1750: <li>If <var title="">entry</var> was a marker, then stop the
1751: algorithm at this point. The list has been cleared up to the last
1752: marker.</li>
1753:
1754: <li>Go to step 1.</li>
1755:
1756: </ol><h5 id="the-element-pointers"><span class="secno">9.2.3.4 </span>The element pointers</h5>
1757:
1758: <p>Initially, the <dfn id="head-element-pointer"><code title="">head</code> element
1759: pointer</dfn> and the <dfn id="form-element-pointer"><code title="">form</code> element
1760: pointer</dfn> are both null.</p>
1761:
1.159 mike 1762: <p>Once a <code><a href="semantics.html#the-head-element-0">head</a></code> element has been parsed (whether
1.1 mike 1763: implicitly or explicitly) the <a href="#head-element-pointer"><code title="">head</code>
1764: element pointer</a> gets set to point to this node.</p>
1765:
1766: <p>The <a href="#form-element-pointer"><code title="">form</code> element pointer</a>
1767: points to the last <code><a href="forms.html#the-form-element">form</a></code> element that was opened and
1768: whose end tag has not yet been seen. It is used to make form
1769: controls associate with forms in the face of dramatically bad
1770: markup, for historical reasons.</p>
1771:
1772:
1773: <h5 id="other-parsing-state-flags"><span class="secno">9.2.3.5 </span>Other parsing state flags</h5>
1774:
1775: <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
1776: <code>Document</code> with which the parser is associated when the
1777: parser was created, and "disabled" otherwise.</p>
1778:
1779: <p class="note">The <a href="#scripting-flag">scripting flag</a> can be enabled even
1780: when the parser was originally created for the <a href="#html-fragment-parsing-algorithm">HTML fragment
1781: parsing algorithm</a>, even though <code><a href="semantics.html#script">script</a></code> elements
1782: don't execute in that case.</p>
1783:
1784: <p>The <dfn id="frameset-ok-flag">frameset-ok flag</dfn> is set to "ok" when the parser is
1785: created. It is set to "not ok" after certain tokens are seen.</p>
1786:
1787:
1.159 mike 1788: <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 1789:
1790: <p>Implementations must act as if they used the following state
1791: machine to tokenize HTML. The state machine must start in the
1792: <a href="#data-state">data state</a>. Most states consume a single character,
1793: which may have various side-effects, and either switches the state
1794: machine to a new state to <em>reconsume</em> the same character, or
1795: switches it to a new state (to consume the next character), or
1796: repeats the same state (to consume the next character). Some states
1797: have more complicated behavior and can consume several characters
1798: before switching to another state.</p>
1799:
1800: <p>The exact behavior of certain states depends on a <dfn id="content-model-flag">content
1801: model flag</dfn> that is set after certain tokens are emitted. The
1.91 mike 1802: 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
1803: state. In the RCDATA and RAWTEXT states, a further <dfn id="escape-flag">escape
1.1 mike 1804: flag</dfn> is used to control the behavior of the tokenizer. It is
1805: either true or false, and initially must be set to the false
1806: state. The <a href="#insertion-mode">insertion mode</a> and the <a href="#stack-of-open-elements">stack of open
1807: elements</a> also affects tokenization.</p>
1808:
1809: <p>The output of the tokenization step is a series of zero or more
1810: of the following tokens: DOCTYPE, start tag, end tag, comment,
1811: character, end-of-file. DOCTYPE tokens have a name, a public
1812: identifier, a system identifier, and a <i>force-quirks
1813: flag</i>. When a DOCTYPE token is created, its name, public
1814: identifier, and system identifier must be marked as missing (which
1815: is a distinct state from the empty string), and the <i>force-quirks
1816: flag</i> must be set to <i>off</i> (its other state is
1817: <i>on</i>). Start and end tag tokens have a tag name, a
1818: <i>self-closing flag</i>, and a list of attributes, each of which
1819: has a name and a value. When a start or end tag token is created,
1820: its <i>self-closing flag</i> must be unset (its other state is that
1821: it be set), and its attributes list must be empty. Comment and
1822: character tokens have data.</p>
1823:
1824: <p>When a token is emitted, it must immediately be handled by the
1825: <a href="#tree-construction">tree construction</a> stage. The tree construction stage
1826: can affect the state of the <a href="#content-model-flag">content model flag</a>, and can
1827: insert additional characters into the stream. (For example, the
1828: <code><a href="semantics.html#script">script</a></code> element can result in scripts executing and
1.159 mike 1829: using the <a href="embedded-content-0.html#dynamic-markup-insertion">dynamic markup insertion</a> APIs to insert
1.1 mike 1830: characters into the stream being tokenized.)</p>
1831:
1832: <p>When a start tag token is emitted with its <i>self-closing
1833: flag</i> set, if the flag is not <dfn id="acknowledge-self-closing-flag" title="acknowledge
1834: self-closing flag">acknowledged</dfn> when it is processed by the
1835: tree construction stage, that is a <a href="#parse-error">parse error</a>.</p>
1836:
1837: <p>When an end tag token is emitted, the <a href="#content-model-flag">content model
1838: flag</a> must be switched to the PCDATA state.</p>
1839:
1840: <p>When an end tag token is emitted with attributes, that is a
1841: <a href="#parse-error">parse error</a>.</p>
1842:
1843: <p>When an end tag token is emitted with its <i>self-closing
1844: flag</i> set, that is a <a href="#parse-error">parse error</a>.</p>
1845:
1846: <p>Before each step of the tokenizer, the user agent must first
1847: check the <a href="#parser-pause-flag">parser pause flag</a>. If it is true, then the
1848: tokenizer must abort the processing of any nested invocations of the
1849: tokenizer, yielding control back to the caller. If it is false, then
1850: the user agent may then check to see if either one of the scripts in
1851: the <a href="semantics.html#list-of-scripts-that-will-execute-as-soon-as-possible">list of scripts that will execute as soon as
1852: possible</a> or the first script in the <a href="semantics.html#list-of-scripts-that-will-execute-asynchronously">list of scripts
1853: that will execute asynchronously</a>, has <a href="semantics.html#completed-loading">completed
1854: loading</a>. If one has, then it must be <a href="semantics.html#executing-a-script-block" title="executing a
1855: script block">executed</a> and removed from its list.</p>
1856:
1857: <p>The tokenizer state machine consists of the states defined in the
1858: following subsections.</p>
1859:
1860: <!-- XXX should go through these reordering the entries so that
1861: they're in some consistent order, like, by Unicode, errors last, or
1862: something -->
1863:
1864: <h5 id="data-state"><span class="secno">9.2.4.1 </span><dfn>Data state</dfn></h5>
1865:
1866: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
1867:
1868: <dl class="switch"><dt>U+0026 AMPERSAND (&)</dt>
1869: <dd>When the <a href="#content-model-flag">content model flag</a> is set to one of the
1870: PCDATA or RCDATA states and the <a href="#escape-flag">escape flag</a> is
1871: false: switch to the <a href="#character-reference-data-state">character reference data
1.56 mike 1872: state</a>.</dd>
1873: <dd>Otherwise: treat it as per the "anything else" entry
1874: below.</dd>
1.1 mike 1875:
1876: <dt>U+002D HYPHEN-MINUS (-)</dt>
1877: <dd>
1878:
1879: <p>If the <a href="#content-model-flag">content model flag</a> is set to either the
1.91 mike 1880: RCDATA state or the RAWTEXT state, and the <a href="#escape-flag">escape flag</a>
1.1 mike 1881: is false, and there are at least three characters before this
1882: one in the input stream, and the last four characters in the
1883: input stream, including this one, are U+003C LESS-THAN SIGN,
1884: U+0021 EXCLAMATION MARK, U+002D HYPHEN-MINUS, and U+002D
1885: HYPHEN-MINUS ("<!--"), then set the <a href="#escape-flag">escape flag</a>
1886: to true.</p>
1887:
1888: <p>In any case, emit the input character as a character
1889: token. Stay in the <a href="#data-state">data state</a>.</p>
1890:
1891: </dd>
1892:
1893: <dt>U+003C LESS-THAN SIGN (<)</dt>
1894: <dd>When the <a href="#content-model-flag">content model flag</a> is set to the PCDATA
1895: state: switch to the <a href="#tag-open-state">tag open state</a>.</dd>
1896: <dd>When the <a href="#content-model-flag">content model flag</a> is set to either the
1.91 mike 1897: RCDATA state or the RAWTEXT state, and the <a href="#escape-flag">escape flag</a>
1.1 mike 1898: is false: switch to the <a href="#tag-open-state">tag open state</a>.</dd>
1899: <dd>Otherwise: treat it as per the "anything else" entry
1900: below.</dd>
1901:
1902: <dt>U+003E GREATER-THAN SIGN (>)</dt>
1903: <dd>
1904:
1905: <p>If the <a href="#content-model-flag">content model flag</a> is set to either the
1.91 mike 1906: RCDATA state or the RAWTEXT state, and the <a href="#escape-flag">escape
1.1 mike 1907: flag</a> is true, and the last three characters in the input
1908: stream including this one are U+002D HYPHEN-MINUS, U+002D
1909: HYPHEN-MINUS, U+003E GREATER-THAN SIGN ("-->"), set the
1910: <a href="#escape-flag">escape flag</a> to false.</p> <!-- no need to check
1911: that there are enough characters, since you can only run into
1912: this if the flag is true in the first place, which requires four
1913: characters. -->
1914:
1915: <p>In any case, emit the input character as a character
1916: token. Stay in the <a href="#data-state">data state</a>.</p>
1917:
1918: </dd>
1919:
1920: <dt>EOF</dt>
1921: <dd>Emit an end-of-file token.</dd>
1922:
1923: <dt>Anything else</dt>
1924: <dd>Emit the input character as a character token. Stay in the
1925: <a href="#data-state">data state</a>.</dd>
1926:
1927: </dl><h5 id="character-reference-data-state"><span class="secno">9.2.4.2 </span><dfn>Character reference data state</dfn></h5>
1928:
1929: <p><i>(This cannot happen if the <a href="#content-model-flag">content model flag</a>
1.91 mike 1930: is set to the RAWTEXT state.)</i></p>
1.1 mike 1931:
1932: <p>Attempt to <a href="#consume-a-character-reference">consume a character reference</a>, with no
1933: <a href="#additional-allowed-character">additional allowed character</a>.</p>
1934:
1935: <p>If nothing is returned, emit a U+0026 AMPERSAND character
1936: token.</p>
1937:
1938: <p>Otherwise, emit the character token that was returned.</p>
1939:
1940: <p>Finally, switch to the <a href="#data-state">data state</a>.</p>
1941:
1942:
1943: <h5 id="tag-open-state"><span class="secno">9.2.4.3 </span><dfn>Tag open state</dfn></h5>
1944:
1945: <p>The behavior of this state depends on the <a href="#content-model-flag">content model
1946: flag</a>.</p>
1947:
1948: <dl><dt>If the <a href="#content-model-flag">content model flag</a> is set to the RCDATA
1.91 mike 1949: or RAWTEXT states</dt>
1.1 mike 1950:
1951: <dd>
1952:
1953: <p>Consume the <a href="#next-input-character">next input character</a>. If it is a
1954: U+002F SOLIDUS (/) character, switch to the <a href="#close-tag-open-state">close tag open
1955: state</a>. Otherwise, emit a U+003C LESS-THAN SIGN character
1956: token and reconsume the <a href="#current-input-character">current input character</a> in the
1957: <a href="#data-state">data state</a>.</p>
1958:
1959: </dd>
1960:
1961: <dt>If the <a href="#content-model-flag">content model flag</a> is set to the PCDATA
1962: state</dt>
1963:
1964: <dd>
1965:
1966: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
1967:
1968: <dl class="switch"><dt>U+0021 EXCLAMATION MARK (!)</dt>
1969: <dd>Switch to the <a href="#markup-declaration-open-state">markup declaration open state</a>.</dd>
1970:
1971: <dt>U+002F SOLIDUS (/)</dt>
1972: <dd>Switch to the <a href="#close-tag-open-state">close tag open state</a>.</dd>
1973:
1974: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
1975: <dd>Create a new start tag token, set its tag name to the
1976: lowercase version of the input character (add 0x0020 to the
1977: character's code point), then switch to the <a href="#tag-name-state">tag name
1978: state</a>. (Don't emit the token yet; further details will
1979: be filled in before it is emitted.)</dd>
1980:
1981: <dt>U+0061 LATIN SMALL LETTER A through to U+007A LATIN SMALL LETTER Z</dt>
1982: <dd>Create a new start tag token, set its tag name to the input
1983: character, then switch to the <a href="#tag-name-state">tag name
1984: state</a>. (Don't emit the token yet; further details will
1985: be filled in before it is emitted.)</dd>
1986:
1987: <dt>U+003E GREATER-THAN SIGN (>)</dt>
1988: <dd><a href="#parse-error">Parse error</a>. Emit a U+003C LESS-THAN SIGN
1989: character token and a U+003E GREATER-THAN SIGN character
1990: token. Switch to the <a href="#data-state">data state</a>.</dd>
1991:
1992: <dt>U+003F QUESTION MARK (?)</dt>
1993: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#bogus-comment-state">bogus
1994: comment state</a>.</dd>
1995:
1996: <dt>Anything else</dt>
1997: <dd><a href="#parse-error">Parse error</a>. Emit a U+003C LESS-THAN SIGN
1998: character token and reconsume the <a href="#current-input-character">current input character</a> in the
1999: <a href="#data-state">data state</a>.</dd>
2000:
2001: </dl></dd>
2002:
2003: </dl><h5 id="close-tag-open-state"><span class="secno">9.2.4.4 </span><dfn>Close tag open state</dfn></h5>
2004:
2005: <p>If the <a href="#content-model-flag">content model flag</a> is set to the RCDATA or
1.91 mike 2006: RAWTEXT states but no start tag token has ever been emitted by this
1.1 mike 2007: instance of the tokenizer (<a href="#fragment-case">fragment case</a>), or, if the
1.91 mike 2008: <a href="#content-model-flag">content model flag</a> is set to the RCDATA or RAWTEXT states
1.1 mike 2009: and the next few characters do not match the tag name of the last
2010: start tag token emitted (compared in an <a href="infrastructure.html#ascii-case-insensitive">ASCII
2011: case-insensitive</a> manner), or if they do but they are not
2012: immediately followed by one of the following characters:</p>
2013:
2014: <ul class="brief"><li>U+0009 CHARACTER TABULATION</li>
2015: <li>U+000A LINE FEED (LF)</li>
2016: <li>U+000C FORM FEED (FF)</li>
2017: <!--<li>U+000D CARRIAGE RETURN (CR)</li>-->
2018: <li>U+0020 SPACE</li>
2019: <li>U+003E GREATER-THAN SIGN (>)</li>
2020: <li>U+002F SOLIDUS (/)</li>
2021: <li>EOF</li>
2022: </ul><p>...then emit a U+003C LESS-THAN SIGN character token, a U+002F
2023: SOLIDUS character token, and switch to the <a href="#data-state">data state</a>
2024: to process the <a href="#next-input-character">next input character</a>.</p>
2025:
2026: <p>Otherwise, if the <a href="#content-model-flag">content model flag</a> is set to the
2027: PCDATA state, or if the next few characters <em>do</em> match that tag
2028: name, consume the <a href="#next-input-character">next input character</a>:</p>
2029:
2030: <dl class="switch"><dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2031: <dd>Create a new end tag token, set its tag name to the lowercase
2032: version of the input character (add 0x0020 to the character's
2033: code point), then switch to the <a href="#tag-name-state">tag name
2034: state</a>. (Don't emit the token yet; further details will be
2035: filled in before it is emitted.)</dd>
2036:
2037: <dt>U+0061 LATIN SMALL LETTER A through to U+007A LATIN SMALL LETTER Z</dt>
2038: <dd>Create a new end tag token, set its tag name to the input
2039: character, then switch to the <a href="#tag-name-state">tag name state</a>. (Don't
2040: emit the token yet; further details will be filled in before it
2041: is emitted.)</dd>
2042:
2043: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2044: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#data-state">data
2045: state</a>.</dd>
2046:
2047: <dt>EOF</dt>
2048: <dd><a href="#parse-error">Parse error</a>. Emit a U+003C LESS-THAN SIGN
2049: character token and a U+002F SOLIDUS character token. Reconsume
2050: the EOF character in the <a href="#data-state">data state</a>.</dd>
2051:
2052: <dt>Anything else</dt>
2053: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#bogus-comment-state">bogus
2054: comment state</a>.</dd>
2055:
2056: </dl><h5 id="tag-name-state"><span class="secno">9.2.4.5 </span><dfn>Tag name state</dfn></h5>
2057:
2058: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2059:
2060: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2061: <dt>U+000A LINE FEED (LF)</dt>
2062: <dt>U+000C FORM FEED (FF)</dt>
2063: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2064: <dt>U+0020 SPACE</dt>
2065: <dd>Switch to the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2066:
2067: <dt>U+002F SOLIDUS (/)</dt>
2068: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2069:
2070: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2071: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2072: state</a>.</dd>
2073:
2074: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2075: <dd>Append the lowercase version of the <a href="#current-input-character">current input character</a>
2076: (add 0x0020 to the character's code point) to the current tag
2077: token's tag name. Stay in the <a href="#tag-name-state">tag name state</a>.</dd>
2078:
2079: <dt>EOF</dt>
2080: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2081: <a href="#data-state">data state</a>.</dd>
2082:
2083: <dt>Anything else</dt>
2084: <dd>Append the <a href="#current-input-character">current input character</a> to the current tag token's
2085: tag name. Stay in the <a href="#tag-name-state">tag name state</a>.</dd>
2086:
2087: </dl><h5 id="before-attribute-name-state"><span class="secno">9.2.4.6 </span><dfn>Before attribute name state</dfn></h5>
2088:
2089: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2090:
2091: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2092: <dt>U+000A LINE FEED (LF)</dt>
2093: <dt>U+000C FORM FEED (FF)</dt>
2094: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2095: <dt>U+0020 SPACE</dt>
2096: <dd>Stay in the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2097:
2098: <dt>U+002F SOLIDUS (/)</dt>
2099: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2100:
2101: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2102: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2103: state</a>.</dd>
2104:
2105: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2106: <dd>Start a new attribute in the current tag token. Set that
2107: attribute's name to the lowercase version of the <a href="#current-input-character">current input
2108: character</a> (add 0x0020 to the character's code point), and its
2109: value to the empty string. Switch to the <a href="#attribute-name-state">attribute name
2110: state</a>.</dd>
2111:
2112: <dt>U+0022 QUOTATION MARK (")</dt>
2113: <dt>U+0027 APOSTROPHE (')</dt>
2114: <dt>U+003C LESS-THAN SIGN (<)</dt>
2115: <dt>U+003D EQUALS SIGN (=)</dt>
2116: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2117: entry below.</dd>
2118:
2119: <dt>EOF</dt>
2120: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2121: <a href="#data-state">data state</a>.</dd>
2122:
2123: <dt>Anything else</dt>
2124: <dd>Start a new attribute in the current tag token. Set that
2125: attribute's name to the <a href="#current-input-character">current input character</a>, and its value to
2126: the empty string. Switch to the <a href="#attribute-name-state">attribute name
2127: state</a>.</dd>
2128:
2129: </dl><h5 id="attribute-name-state"><span class="secno">9.2.4.7 </span><dfn>Attribute name state</dfn></h5>
2130:
2131: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2132:
2133: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2134: <dt>U+000A LINE FEED (LF)</dt>
2135: <dt>U+000C FORM FEED (FF)</dt>
2136: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2137: <dt>U+0020 SPACE</dt>
2138: <dd>Switch to the <a href="#after-attribute-name-state">after attribute name state</a>.</dd>
2139:
2140: <dt>U+002F SOLIDUS (/)</dt>
2141: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2142:
2143: <dt>U+003D EQUALS SIGN (=)</dt>
2144: <dd>Switch to the <a href="#before-attribute-value-state">before attribute value state</a>.</dd>
2145:
2146: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2147: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2148: state</a>.</dd>
2149:
2150: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2151: <dd>Append the lowercase version of the <a href="#current-input-character">current input character</a>
2152: (add 0x0020 to the character's code point) to the current
2153: attribute's name. Stay in the <a href="#attribute-name-state">attribute name
2154: state</a>.</dd>
2155:
2156: <dt>U+0022 QUOTATION MARK (")</dt>
2157: <dt>U+0027 APOSTROPHE (')</dt>
2158: <dt>U+003C LESS-THAN SIGN (<)</dt>
2159: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2160: entry below.</dd>
2161:
2162: <dt>EOF</dt>
2163: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2164: <a href="#data-state">data state</a>.</dd>
2165:
2166: <dt>Anything else</dt>
2167: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2168: name. Stay in the <a href="#attribute-name-state">attribute name state</a>.</dd>
2169:
2170: </dl><p>When the user agent leaves the attribute name state (and before
2171: emitting the tag token, if appropriate), the complete attribute's
2172: name must be compared to the other attributes on the same token;
2173: if there is already an attribute on the token with the exact same
2174: name, then this is a <a href="#parse-error">parse error</a> and the new
2175: attribute must be dropped, along with the value that gets
2176: associated with it (if any).</p>
2177:
2178:
2179: <h5 id="after-attribute-name-state"><span class="secno">9.2.4.8 </span><dfn>After attribute name state</dfn></h5>
2180:
2181: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2182:
2183: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2184: <dt>U+000A LINE FEED (LF)</dt>
2185: <dt>U+000C FORM FEED (FF)</dt>
2186: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2187: <dt>U+0020 SPACE</dt>
2188: <dd>Stay in the <a href="#after-attribute-name-state">after attribute name state</a>.</dd>
2189:
2190: <dt>U+002F SOLIDUS (/)</dt>
2191: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2192:
2193: <dt>U+003D EQUALS SIGN (=)</dt>
2194: <dd>Switch to the <a href="#before-attribute-value-state">before attribute value state</a>.</dd>
2195:
2196: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2197: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2198: state</a>.</dd>
2199:
2200: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2201: <dd>Start a new attribute in the current tag token. Set that
2202: attribute's name to the lowercase version of the <a href="#current-input-character">current input character</a>
2203: (add 0x0020 to the character's code point), and its value to
2204: the empty string. Switch to the <a href="#attribute-name-state">attribute name
2205: state</a>.</dd>
2206:
2207: <dt>U+0022 QUOTATION MARK (")</dt>
2208: <dt>U+0027 APOSTROPHE (')</dt>
2209: <dt>U+003C LESS-THAN SIGN (<)</dt>
2210: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2211: entry below.</dd>
2212:
2213: <dt>EOF</dt>
2214: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2215: <a href="#data-state">data state</a>.</dd>
2216:
2217: <dt>Anything else</dt>
2218: <dd>Start a new attribute in the current tag token. Set that
2219: attribute's name to the <a href="#current-input-character">current input character</a>, and its value to
2220: the empty string. Switch to the <a href="#attribute-name-state">attribute name
2221: state</a>.</dd>
2222:
2223: </dl><h5 id="before-attribute-value-state"><span class="secno">9.2.4.9 </span><dfn>Before attribute value state</dfn></h5>
2224:
2225: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2226:
2227: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2228: <dt>U+000A LINE FEED (LF)</dt>
2229: <dt>U+000C FORM FEED (FF)</dt>
2230: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2231: <dt>U+0020 SPACE</dt>
2232: <dd>Stay in the <a href="#before-attribute-value-state">before attribute value state</a>.</dd>
2233:
2234: <dt>U+0022 QUOTATION MARK (")</dt>
2235: <dd>Switch to the <a href="#attribute-value-double-quoted-state">attribute value (double-quoted) state</a>.</dd>
2236:
2237: <dt>U+0026 AMPERSAND (&)</dt>
2238: <dd>Switch to the <a href="#attribute-value-unquoted-state">attribute value (unquoted) state</a>
2239: and reconsume this input character.</dd>
2240:
2241: <dt>U+0027 APOSTROPHE (')</dt>
2242: <dd>Switch to the <a href="#attribute-value-single-quoted-state">attribute value (single-quoted) state</a>.</dd>
2243:
2244: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2245: <dd><a href="#parse-error">Parse error</a>. Emit the current tag token. Switch to
2246: the <a href="#data-state">data state</a>.</dd>
2247:
2248: <dt>U+003C LESS-THAN SIGN (<)</dt>
2249: <dt>U+003D EQUALS SIGN (=)</dt>
2250: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2251: entry below.</dd>
2252:
2253: <dt>EOF</dt>
2254: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2255: <a href="#data-state">data state</a>.</dd>
2256:
2257: <dt>Anything else</dt>
2258: <dd>Append the <a href="#current-input-character">current input character</a> to the current
2259: attribute's value. Switch to the <a href="#attribute-value-unquoted-state">attribute value (unquoted)
2260: state</a>.</dd>
2261:
2262: </dl><h5 id="attribute-value-double-quoted-state"><span class="secno">9.2.4.10 </span><dfn>Attribute value (double-quoted) state</dfn></h5>
2263:
2264: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2265:
2266: <dl class="switch"><dt>U+0022 QUOTATION MARK (")</dt>
2267: <dd>Switch to the <a href="#after-attribute-value-quoted-state">after attribute value (quoted)
2268: state</a>.</dd>
2269:
2270: <dt>U+0026 AMPERSAND (&)</dt>
2271: <dd>Switch to the <a href="#character-reference-in-attribute-value-state">character reference in attribute value
2272: state</a>, with the <a href="#additional-allowed-character">additional allowed character</a>
2273: being U+0022 QUOTATION MARK (").</dd>
2274:
2275: <dt>EOF</dt>
2276: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2277: <a href="#data-state">data state</a>.</dd>
2278:
2279: <dt>Anything else</dt>
2280: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2281: value. Stay in the <a href="#attribute-value-double-quoted-state">attribute value (double-quoted)
2282: state</a>.</dd>
2283:
2284: </dl><h5 id="attribute-value-single-quoted-state"><span class="secno">9.2.4.11 </span><dfn>Attribute value (single-quoted) state</dfn></h5>
2285:
2286: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2287:
2288: <dl class="switch"><dt>U+0027 APOSTROPHE (')</dt>
2289: <dd>Switch to the <a href="#after-attribute-value-quoted-state">after attribute value (quoted)
2290: state</a>.</dd>
2291:
2292: <dt>U+0026 AMPERSAND (&)</dt>
2293: <dd>Switch to the <a href="#character-reference-in-attribute-value-state">character reference in attribute value
2294: state</a>, with the <a href="#additional-allowed-character">additional allowed character</a>
2295: being U+0027 APOSTROPHE (').</dd>
2296:
2297: <dt>EOF</dt>
2298: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2299: <a href="#data-state">data state</a>.</dd>
2300:
2301: <dt>Anything else</dt>
2302: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2303: value. Stay in the <a href="#attribute-value-single-quoted-state">attribute value (single-quoted)
2304: state</a>.</dd>
2305:
2306: </dl><h5 id="attribute-value-unquoted-state"><span class="secno">9.2.4.12 </span><dfn>Attribute value (unquoted) state</dfn></h5>
2307:
2308: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2309:
2310: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2311: <dt>U+000A LINE FEED (LF)</dt>
2312: <dt>U+000C FORM FEED (FF)</dt>
2313: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2314: <dt>U+0020 SPACE</dt>
2315: <dd>Switch to the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2316:
2317: <dt>U+0026 AMPERSAND (&)</dt>
2318: <dd>Switch to the <a href="#character-reference-in-attribute-value-state">character reference in attribute value
2319: state</a>, with no <a href="#additional-allowed-character">additional allowed
2320: character</a>.</dd>
2321:
2322: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2323: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2324: state</a>.</dd>
2325:
2326: <dt>U+0022 QUOTATION MARK (")</dt>
2327: <dt>U+0027 APOSTROPHE (')</dt>
2328: <dt>U+003C LESS-THAN SIGN (<)</dt>
2329: <dt>U+003D EQUALS SIGN (=)</dt>
2330: <dd><a href="#parse-error">Parse error</a>. Treat it as per the "anything else"
2331: entry below.</dd>
2332:
2333: <dt>EOF</dt>
2334: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2335: <a href="#data-state">data state</a>.</dd>
2336:
2337: <dt>Anything else</dt>
2338: <dd>Append the <a href="#current-input-character">current input character</a> to the current attribute's
2339: value. Stay in the <a href="#attribute-value-unquoted-state">attribute value (unquoted)
2340: state</a>.</dd>
2341:
2342: </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>
2343:
2344: <p>Attempt to <a href="#consume-a-character-reference">consume a character reference</a>.</p>
2345:
2346: <p>If nothing is returned, append a U+0026 AMPERSAND character to
2347: the current attribute's value.</p>
2348:
2349: <p>Otherwise, append the returned character token to the current
2350: attribute's value.</p>
2351:
2352: <p>Finally, switch back to the attribute value state that you were
2353: in when were switched into this state.</p>
2354:
2355:
2356: <h5 id="after-attribute-value-quoted-state"><span class="secno">9.2.4.14 </span><dfn>After attribute value (quoted) state</dfn></h5>
2357:
2358: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2359:
2360: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2361: <dt>U+000A LINE FEED (LF)</dt>
2362: <dt>U+000C FORM FEED (FF)</dt>
2363: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2364: <dt>U+0020 SPACE</dt>
2365: <dd>Switch to the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2366:
2367: <dt>U+002F SOLIDUS (/)</dt>
2368: <dd>Switch to the <a href="#self-closing-start-tag-state">self-closing start tag state</a>.</dd>
2369:
2370: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2371: <dd>Emit the current tag token. Switch to the <a href="#data-state">data
2372: state</a>.</dd>
2373:
2374: <dt>EOF</dt>
2375: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2376: <a href="#data-state">data state</a>.</dd>
2377:
2378: <dt>Anything else</dt>
2379: <dd><a href="#parse-error">Parse error</a>. Reconsume the character in
2380: the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2381:
2382: </dl><h5 id="self-closing-start-tag-state"><span class="secno">9.2.4.15 </span><dfn>Self-closing start tag state</dfn></h5>
2383:
2384: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2385:
2386: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2387: <dd>Set the <i>self-closing flag</i> of the current tag
2388: token. Emit the current tag token. Switch to the <a href="#data-state">data
2389: state</a>.</dd>
2390:
2391: <dt>EOF</dt>
2392: <dd><a href="#parse-error">Parse error</a>. Reconsume the EOF character in the
2393: <a href="#data-state">data state</a>.</dd>
2394:
2395: <dt>Anything else</dt>
2396: <dd><a href="#parse-error">Parse error</a>. Reconsume the character in
2397: the <a href="#before-attribute-name-state">before attribute name state</a>.</dd>
2398:
2399: </dl><h5 id="bogus-comment-state"><span class="secno">9.2.4.16 </span><dfn>Bogus comment state</dfn></h5>
2400:
2401: <p><i>(This can only happen if the <a href="#content-model-flag">content model
2402: flag</a> is set to the PCDATA state.)</i></p>
2403:
2404: <p>Consume every character up to and including the first U+003E
2405: GREATER-THAN SIGN character (>) or the end of the file (EOF),
2406: whichever comes first. Emit a comment token whose data is the
2407: concatenation of all the characters starting from and including
2408: the character that caused the state machine to switch into the
2409: bogus comment state, up to and including the character immediately
2410: before the last consumed character (i.e. up to the character just
2411: before the U+003E or EOF character). (If the comment was started
2412: by the end of the file (EOF), the token is empty.)</p>
2413:
2414: <p>Switch to the <a href="#data-state">data state</a>.</p>
2415:
2416: <p>If the end of the file was reached, reconsume the EOF
2417: character.</p>
2418:
2419:
2420: <h5 id="markup-declaration-open-state"><span class="secno">9.2.4.17 </span><dfn>Markup declaration open state</dfn></h5>
2421:
2422: <p><i>(This can only happen if the <a href="#content-model-flag">content model
2423: flag</a> is set to the PCDATA state.)</i></p>
2424:
2425: <p>If the next two characters are both U+002D HYPHEN-MINUS (-)
2426: characters, consume those two characters, create a comment token
2427: whose data is the empty string, and switch to the <a href="#comment-start-state">comment
2428: start state</a>.</p>
2429:
2430: <p>Otherwise, if the next seven characters are an <a href="infrastructure.html#ascii-case-insensitive">ASCII
2431: case-insensitive</a> match for the word "DOCTYPE", then consume
2432: those characters and switch to the <a href="#doctype-state">DOCTYPE state</a>.</p>
2433:
2434: <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
2435: content</a>" and the <a href="#current-node">current node</a> is not an element
2436: in the <a href="#html-namespace-0">HTML namespace</a> and the next seven characters are
2437: an <span>ASCII case-sensitive</span> match for the string "[CDATA["
2438: (the five uppercase letters "CDATA" with a U+005B LEFT SQUARE
2439: BRACKET character before and after), then consume those characters
1.91 mike 2440: and switch to the <a href="#cdata-section-state">CDATA section state</a>.</p>
1.1 mike 2441:
2442: <p>Otherwise, this is a <a href="#parse-error">parse error</a>. Switch to the
2443: <a href="#bogus-comment-state">bogus comment state</a>. The next character that is
2444: consumed, if any, is the first character that will be in the
2445: comment.</p>
2446:
2447:
2448: <h5 id="comment-start-state"><span class="secno">9.2.4.18 </span><dfn>Comment start state</dfn></h5>
2449:
2450: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2451:
2452: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2453: <dd>Switch to the <a href="#comment-start-dash-state">comment start dash state</a>.</dd>
2454:
2455: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2456: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Switch to the
2457: <a href="#data-state">data state</a>.</dd> <!-- see comment in comment end state
2458: -->
2459:
2460: <dt>EOF</dt>
2461: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2462: the EOF character in the <a href="#data-state">data state</a>.</dd>
2463:
2464: <dt>Anything else</dt>
2465: <dd>Append the input character to the comment token's
2466: data. Switch to the <a href="#comment-state">comment state</a>.</dd>
2467:
2468: </dl><h5 id="comment-start-dash-state"><span class="secno">9.2.4.19 </span><dfn>Comment start dash state</dfn></h5>
2469:
2470: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2471:
2472: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2473: <dd>Switch to the <a href="#comment-end-state">comment end state</a></dd>
2474:
2475: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2476: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Switch to
2477: the <a href="#data-state">data state</a>.</dd>
2478:
2479: <dt>EOF</dt>
2480: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume the
2481: EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see comment
2482: in comment end state -->
2483:
2484: <dt>Anything else</dt>
2485: <dd>Append a U+002D HYPHEN-MINUS (-) character and the input
2486: character to the comment token's data. Switch to the
2487: <a href="#comment-state">comment state</a>.</dd>
2488:
2489: </dl><h5 id="comment-state"><span class="secno">9.2.4.20 </span><dfn id="comment">Comment state</dfn></h5>
2490:
2491: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2492:
2493: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2494: <dd>Switch to the <a href="#comment-end-dash-state">comment end dash state</a></dd>
2495:
2496: <dt>EOF</dt>
2497: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume the
2498: EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see comment
2499: in comment end state -->
2500:
2501: <dt>Anything else</dt>
2502: <dd>Append the input character to the comment token's data. Stay
2503: in the <a href="#comment-state">comment state</a>.</dd>
2504:
2505: </dl><h5 id="comment-end-dash-state"><span class="secno">9.2.4.21 </span><dfn>Comment end dash state</dfn></h5>
2506:
2507: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2508:
2509: <dl class="switch"><dt>U+002D HYPHEN-MINUS (-)</dt>
2510: <dd>Switch to the <a href="#comment-end-state">comment end state</a></dd>
2511:
2512: <dt>EOF</dt>
2513: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume the
2514: EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see comment
2515: in comment end state -->
2516:
2517: <dt>Anything else</dt>
2518: <dd>Append a U+002D HYPHEN-MINUS (-) character and the input
2519: character to the comment token's data. Switch to the
2520: <a href="#comment-state">comment state</a>.</dd>
2521:
2522: </dl><h5 id="comment-end-state"><span class="secno">9.2.4.22 </span><dfn>Comment end state</dfn></h5>
2523:
2524: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2525:
2526: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2527: <dd>Emit the comment token. Switch to the <a href="#data-state">data
2528: state</a>.</dd>
2529:
2530: <dt>U+002D HYPHEN-MINUS (-)</dt>
2531: <dd><a href="#parse-error">Parse error</a>. Append a U+002D HYPHEN-MINUS
2532: (-) character to the comment token's data. Stay in the
2533: <a href="#comment-end-state">comment end state</a>.</dd>
2534:
2535: <dt>U+0009 CHARACTER TABULATION</dt>
2536: <dt>U+000A LINE FEED (LF)</dt>
2537: <dt>U+000C FORM FEED (FF)</dt>
2538: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2539: <dt>U+0020 SPACE</dt>
2540: <dd><a href="#parse-error">Parse error</a>. Append two U+002D HYPHEN-MINUS (-)
2541: characters and the input character to the comment token's
2542: data. Switch to the <a href="#comment-end-space-state">comment end space state</a>.</dd>
2543:
2544: <dt>U+0021 EXCLAMATION MARK (!)</dt>
2545: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#comment-end-bang-state">comment end bang
2546: state</a>.</dd>
2547:
2548: <dt>EOF</dt>
2549: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2550: the EOF character in the <a href="#data-state">data state</a>.</dd> <!-- For
2551: security reasons: otherwise, hostile user could put a <script> in
2552: a comment e.g. in a blog comment and then DOS the server so that
2553: the end tag isn't read, and then the commented <script> tag would
2554: be treated as live code -->
2555:
2556: <dt>Anything else</dt>
2557: <dd><a href="#parse-error">Parse error</a>. Append two U+002D HYPHEN-MINUS (-)
2558: characters and the input character to the comment token's
2559: data. Switch to the <a href="#comment-state">comment state</a>.</dd>
2560:
2561: </dl><h5 id="comment-end-bang-state"><span class="secno">9.2.4.23 </span><dfn>Comment end bang state</dfn></h5>
2562:
2563: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2564:
2565: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2566: <dd>Emit the comment token. Switch to the <a href="#data-state">data
2567: state</a>.</dd>
2568:
2569: <dt>U+002D HYPHEN-MINUS (-)</dt>
2570: <dd>Append two U+002D HYPHEN-MINUS (-) characters and a U+0021
2571: EXCLAMATION MARK (!) character to the comment token's data. Switch
2572: to the <a href="#comment-end-dash-state">comment end dash state</a>.</dd>
2573:
2574: <dt>EOF</dt>
2575: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2576: the EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see
2577: comment in comment end state -->
2578:
2579: <dt>Anything else</dt>
2580: <dd>Append two U+002D HYPHEN-MINUS (-) characters, a U+0021
2581: EXCLAMATION MARK (!) character, and the input character to the
2582: comment token's data. Switch to the <a href="#comment-state">comment
2583: state</a>.</dd>
2584:
2585: </dl><h5 id="comment-end-space-state"><span class="secno">9.2.4.24 </span><dfn>Comment end space state</dfn></h5>
2586:
2587: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2588:
2589: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2590: <dd>Emit the comment token. Switch to the <a href="#data-state">data
2591: state</a>.</dd>
2592:
2593: <dt>U+002D HYPHEN-MINUS (-)</dt>
2594: <dd>Switch to the <a href="#comment-end-dash-state">comment end dash state</a>.</dd>
2595:
2596: <dt>U+0009 CHARACTER TABULATION</dt>
2597: <dt>U+000A LINE FEED (LF)</dt>
2598: <dt>U+000C FORM FEED (FF)</dt>
2599: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2600: <dt>U+0020 SPACE</dt>
2601: <dd>Append the input character to the comment token's data. Stay in
2602: the <a href="#comment-end-space-state">comment end space state</a>.</dd>
2603:
2604: <dt>EOF</dt>
2605: <dd><a href="#parse-error">Parse error</a>. Emit the comment token. Reconsume
2606: the EOF character in the <a href="#data-state">data state</a>.</dd> <!-- see
2607: comment in comment end state -->
2608:
2609: <dt>Anything else</dt>
2610: <dd>Append the input character to the comment token's data. Switch
2611: to the <a href="#comment-state">comment state</a>.</dd>
2612:
2613: </dl><h5 id="doctype-state"><span class="secno">9.2.4.25 </span><dfn>DOCTYPE state</dfn></h5>
2614:
2615: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2616:
2617: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2618: <dt>U+000A LINE FEED (LF)</dt>
2619: <dt>U+000C FORM FEED (FF)</dt>
2620: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2621: <dt>U+0020 SPACE</dt>
2622: <dd>Switch to the <a href="#before-doctype-name-state">before DOCTYPE name state</a>.</dd>
2623:
2624: <dt>EOF</dt>
2625: <dd><a href="#parse-error">Parse error</a>. Create a new DOCTYPE token. Set its
2626: <i>force-quirks flag</i> to <i>on</i>. Emit the token. Reconsume
2627: the EOF character in the <a href="#data-state">data state</a>.</dd>
2628:
2629: <dt>Anything else</dt>
2630: <dd><a href="#parse-error">Parse error</a>. Reconsume the current
2631: character in the <a href="#before-doctype-name-state">before DOCTYPE name state</a>.</dd>
2632:
2633: </dl><h5 id="before-doctype-name-state"><span class="secno">9.2.4.26 </span><dfn>Before DOCTYPE name state</dfn></h5>
2634:
2635: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2636:
2637: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2638: <dt>U+000A LINE FEED (LF)</dt>
2639: <dt>U+000C FORM FEED (FF)</dt>
2640: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2641: <dt>U+0020 SPACE</dt>
2642: <dd>Stay in the <a href="#before-doctype-name-state">before DOCTYPE name state</a>.</dd>
2643:
2644: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2645: <dd><a href="#parse-error">Parse error</a>. Create a new DOCTYPE token. Set its
2646: <i>force-quirks flag</i> to <i>on</i>. Emit the token. Switch to
2647: the <a href="#data-state">data state</a>.</dd>
2648:
2649: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2650: <dd>Create a new DOCTYPE token. Set the token's name to the
2651: lowercase version of the input character (add 0x0020 to the
2652: character's code point). Switch to the <a href="#doctype-name-state">DOCTYPE name
2653: state</a>.</dd>
2654:
2655: <dt>EOF</dt>
2656: <dd><a href="#parse-error">Parse error</a>. Create a new DOCTYPE token. Set its
2657: <i>force-quirks flag</i> to <i>on</i>. Emit the token. Reconsume
2658: the EOF character in the <a href="#data-state">data state</a>.</dd>
2659:
2660: <dt>Anything else</dt>
2661: <dd>Create a new DOCTYPE token. Set the token's name to the
2662: <a href="#current-input-character">current input character</a>. Switch to the <a href="#doctype-name-state">DOCTYPE name
2663: state</a>.</dd>
2664:
2665: </dl><h5 id="doctype-name-state"><span class="secno">9.2.4.27 </span><dfn>DOCTYPE name state</dfn></h5>
2666:
2667: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2668:
2669: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2670: <dt>U+000A LINE FEED (LF)</dt>
2671: <dt>U+000C FORM FEED (FF)</dt>
2672: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2673: <dt>U+0020 SPACE</dt>
2674: <dd>Switch to the <a href="#after-doctype-name-state">after DOCTYPE name state</a>.</dd>
2675:
2676: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2677: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2678: state</a>.</dd>
2679:
2680: <dt>U+0041 LATIN CAPITAL LETTER A through to U+005A LATIN CAPITAL LETTER Z</dt>
2681: <dd>Append the lowercase version of the input character (add 0x0020
2682: to the character's code point) to the current DOCTYPE token's
2683: name. Stay in the <a href="#doctype-name-state">DOCTYPE name state</a>.</dd>
2684:
2685: <dt>EOF</dt>
2686: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2687: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2688: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2689:
2690: <dt>Anything else</dt>
2691: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2692: token's name. Stay in the <a href="#doctype-name-state">DOCTYPE name state</a>.</dd>
2693:
2694: </dl><h5 id="after-doctype-name-state"><span class="secno">9.2.4.28 </span><dfn>After DOCTYPE name state</dfn></h5>
2695:
2696: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2697:
2698: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2699: <dt>U+000A LINE FEED (LF)</dt>
2700: <dt>U+000C FORM FEED (FF)</dt>
2701: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2702: <dt>U+0020 SPACE</dt>
2703: <dd>Stay in the <a href="#after-doctype-name-state">after DOCTYPE name state</a>.</dd>
2704:
2705: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2706: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2707: state</a>.</dd>
2708:
2709: <dt>EOF</dt>
2710: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2711: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2712: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2713:
2714: <dt>Anything else</dt>
2715: <dd>
2716:
2717: <p>If the six characters starting from the <a href="#current-input-character">current input
2718: character</a> are an <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> match
2719: for the word "PUBLIC", then consume those characters and switch to
2720: the <a href="#before-doctype-public-identifier-state">before DOCTYPE public identifier state</a>.</p>
2721:
2722: <p>Otherwise, if the six characters starting from the
2723: <a href="#current-input-character">current input character</a> are an <a href="infrastructure.html#ascii-case-insensitive">ASCII
2724: case-insensitive</a> match for the word "SYSTEM", then consume
2725: those characters and switch to the <a href="#before-doctype-system-identifier-state">before DOCTYPE system
2726: identifier state</a>.</p>
2727:
2728: <p>Otherwise, this is the <a href="#parse-error">parse error</a>. Set the
2729: DOCTYPE token's <i>force-quirks flag</i> to <i>on</i>. Switch to
2730: the <a href="#bogus-doctype-state">bogus DOCTYPE state</a>.</p>
2731:
2732: </dd>
2733:
2734: </dl><h5 id="before-doctype-public-identifier-state"><span class="secno">9.2.4.29 </span><dfn>Before DOCTYPE public identifier state</dfn></h5>
2735:
2736: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2737:
2738: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2739: <dt>U+000A LINE FEED (LF)</dt>
2740: <dt>U+000C FORM FEED (FF)</dt>
2741: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2742: <dt>U+0020 SPACE</dt>
2743: <dd>Stay in the <a href="#before-doctype-public-identifier-state">before DOCTYPE public identifier state</a>.</dd>
2744:
2745: <dt>U+0022 QUOTATION MARK (")</dt>
2746: <dd>Set the DOCTYPE token's public identifier to the empty string
2747: (not missing), then switch to the <a href="#doctype-public-identifier-double-quoted-state">DOCTYPE public identifier
2748: (double-quoted) state</a>.</dd>
2749:
2750: <dt>U+0027 APOSTROPHE (')</dt>
2751: <dd>Set the DOCTYPE token's public identifier to the empty string
2752: (not missing), then switch to the <a href="#doctype-public-identifier-single-quoted-state">DOCTYPE public identifier
2753: (single-quoted) state</a>.</dd>
2754:
2755: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2756: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2757: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2758: token. Switch to the <a href="#data-state">data state</a>.</dd>
2759:
2760: <dt>EOF</dt>
2761: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2762: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2763: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2764:
2765: <dt>Anything else</dt>
2766: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2767: <i>force-quirks flag</i> to <i>on</i>. Switch to the <a href="#bogus-doctype-state">bogus
2768: DOCTYPE state</a>.</dd>
2769:
2770: </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>
2771:
2772: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2773:
2774: <dl class="switch"><dt>U+0022 QUOTATION MARK (")</dt>
2775: <dd>Switch to the <a href="#after-doctype-public-identifier-state">after DOCTYPE public identifier state</a>.</dd>
2776:
2777: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2778: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2779: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2780: token. Switch to the <a href="#data-state">data state</a>.</dd>
2781:
2782: <dt>EOF</dt>
2783: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2784: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2785: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2786:
2787: <dt>Anything else</dt>
2788: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2789: token's public identifier. Stay in the <a href="#doctype-public-identifier-double-quoted-state">DOCTYPE public
2790: identifier (double-quoted) state</a>.</dd>
2791:
2792: </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>
2793:
2794: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2795:
2796: <dl class="switch"><dt>U+0027 APOSTROPHE (')</dt>
2797: <dd>Switch to the <a href="#after-doctype-public-identifier-state">after DOCTYPE public identifier state</a>.</dd>
2798:
2799: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2800: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2801: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2802: token. Switch to the <a href="#data-state">data state</a>.</dd>
2803:
2804: <dt>EOF</dt>
2805: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2806: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2807: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2808:
2809: <dt>Anything else</dt>
2810: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2811: token's public identifier. Stay in the <a href="#doctype-public-identifier-single-quoted-state">DOCTYPE public
2812: identifier (single-quoted) state</a>.</dd>
2813:
2814: </dl><h5 id="after-doctype-public-identifier-state"><span class="secno">9.2.4.32 </span><dfn>After DOCTYPE public identifier state</dfn></h5>
2815:
2816: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2817:
2818: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2819: <dt>U+000A LINE FEED (LF)</dt>
2820: <dt>U+000C FORM FEED (FF)</dt>
2821: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2822: <dt>U+0020 SPACE</dt>
2823: <dd>Stay in the <a href="#after-doctype-public-identifier-state">after DOCTYPE public identifier state</a>.</dd>
2824:
2825: <dt>U+0022 QUOTATION MARK (")</dt>
2826: <dd>Set the DOCTYPE token's system identifier to the empty string
2827: (not missing), then switch to the <a href="#doctype-system-identifier-double-quoted-state">DOCTYPE system identifier
2828: (double-quoted) state</a>.</dd>
2829:
2830: <dt>U+0027 APOSTROPHE (')</dt>
2831: <dd>Set the DOCTYPE token's system identifier to the empty string
2832: (not missing), then switch to the <a href="#doctype-system-identifier-single-quoted-state">DOCTYPE system identifier
2833: (single-quoted) state</a>.</dd>
2834:
2835: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2836: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2837: state</a>.</dd>
2838:
2839: <dt>EOF</dt>
2840: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2841: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2842: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2843:
2844: <dt>Anything else</dt>
2845: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2846: <i>force-quirks flag</i> to <i>on</i>. Switch to the <a href="#bogus-doctype-state">bogus
2847: DOCTYPE state</a>.</dd>
2848:
2849: </dl><h5 id="before-doctype-system-identifier-state"><span class="secno">9.2.4.33 </span><dfn>Before DOCTYPE system identifier state</dfn></h5>
2850:
2851: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2852:
2853: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2854: <dt>U+000A LINE FEED (LF)</dt>
2855: <dt>U+000C FORM FEED (FF)</dt>
2856: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2857: <dt>U+0020 SPACE</dt>
2858: <dd>Stay in the <a href="#before-doctype-system-identifier-state">before DOCTYPE system identifier state</a>.</dd>
2859:
2860: <dt>U+0022 QUOTATION MARK (")</dt>
2861: <dd>Set the DOCTYPE token's system identifier to the empty string
2862: (not missing), then switch to the <a href="#doctype-system-identifier-double-quoted-state">DOCTYPE system identifier
2863: (double-quoted) state</a>.</dd>
2864:
2865: <dt>U+0027 APOSTROPHE (')</dt>
2866: <dd>Set the DOCTYPE token's system identifier to the empty string
2867: (not missing), then switch to the <a href="#doctype-system-identifier-single-quoted-state">DOCTYPE system identifier
2868: (single-quoted) state</a>.</dd>
2869:
2870: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2871: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2872: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2873: token. Switch to the <a href="#data-state">data state</a>.</dd>
2874:
2875: <dt>EOF</dt>
2876: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2877: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2878: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2879:
2880: <dt>Anything else</dt>
2881: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2882: <i>force-quirks flag</i> to <i>on</i>. Switch to the <a href="#bogus-doctype-state">bogus
2883: DOCTYPE state</a>.</dd>
2884:
2885: </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>
2886:
2887: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2888:
2889: <dl class="switch"><dt>U+0022 QUOTATION MARK (")</dt>
2890: <dd>Switch to the <a href="#after-doctype-system-identifier-state">after DOCTYPE system identifier state</a>.</dd>
2891:
2892: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2893: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2894: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2895: token. Switch to the <a href="#data-state">data state</a>.</dd>
2896:
2897: <dt>EOF</dt>
2898: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2899: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2900: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2901:
2902: <dt>Anything else</dt>
2903: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2904: token's system identifier. Stay in the <a href="#doctype-system-identifier-double-quoted-state">DOCTYPE system
2905: identifier (double-quoted) state</a>.</dd>
2906:
2907: </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>
2908:
2909: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2910:
2911: <dl class="switch"><dt>U+0027 APOSTROPHE (')</dt>
2912: <dd>Switch to the <a href="#after-doctype-system-identifier-state">after DOCTYPE system identifier state</a>.</dd>
2913:
2914: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2915: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2916: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE
2917: token. Switch to the <a href="#data-state">data state</a>.</dd>
2918:
2919: <dt>EOF</dt>
2920: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2921: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2922: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2923:
2924: <dt>Anything else</dt>
2925: <dd>Append the <a href="#current-input-character">current input character</a> to the current DOCTYPE
2926: token's system identifier. Stay in the <a href="#doctype-system-identifier-single-quoted-state">DOCTYPE system
2927: identifier (single-quoted) state</a>.</dd>
2928:
2929: </dl><h5 id="after-doctype-system-identifier-state"><span class="secno">9.2.4.36 </span><dfn>After DOCTYPE system identifier state</dfn></h5>
2930:
2931: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2932:
2933: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
2934: <dt>U+000A LINE FEED (LF)</dt>
2935: <dt>U+000C FORM FEED (FF)</dt>
2936: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
2937: <dt>U+0020 SPACE</dt>
2938: <dd>Stay in the <a href="#after-doctype-system-identifier-state">after DOCTYPE system identifier state</a>.</dd>
2939:
2940: <dt>U+003E GREATER-THAN SIGN (>)</dt>
2941: <dd>Emit the current DOCTYPE token. Switch to the <a href="#data-state">data
2942: state</a>.</dd>
2943:
2944: <dt>EOF</dt>
2945: <dd><a href="#parse-error">Parse error</a>. Set the DOCTYPE token's
2946: <i>force-quirks flag</i> to <i>on</i>. Emit that DOCTYPE token.
2947: Reconsume the EOF character in the <a href="#data-state">data state</a>.</dd>
2948:
2949: <dt>Anything else</dt>
2950: <dd><a href="#parse-error">Parse error</a>. Switch to the <a href="#bogus-doctype-state">bogus DOCTYPE
2951: state</a>. (This does <em>not</em> set the DOCTYPE token's
2952: <i>force-quirks flag</i> to <i>on</i>.)</dd>
2953:
2954: </dl><h5 id="bogus-doctype-state"><span class="secno">9.2.4.37 </span><dfn>Bogus DOCTYPE state</dfn></h5>
2955:
2956: <p>Consume the <a href="#next-input-character">next input character</a>:</p>
2957:
2958: <dl class="switch"><dt>U+003E GREATER-THAN SIGN (>)</dt>
2959: <dd>Emit the DOCTYPE token. Switch to the <a href="#data-state">data
2960: state</a>.</dd>
2961:
2962: <dt>EOF</dt>
2963: <dd>Emit the DOCTYPE token. Reconsume the EOF character in the
2964: <a href="#data-state">data state</a>.</dd>
2965:
2966: <dt>Anything else</dt>
2967: <dd>Stay in the <a href="#bogus-doctype-state">bogus DOCTYPE state</a>.</dd>
2968:
2969: </dl><h5 id="cdata-section-state"><span class="secno">9.2.4.38 </span><dfn>CDATA section state</dfn></h5>
2970:
2971: <p><i>(This can only happen if the <a href="#content-model-flag">content model
1.91 mike 2972: flag</a> is set to the PCDATA state.)</i></p>
1.1 mike 2973:
2974: <p>Consume every character up to the next occurrence of the three
2975: character sequence U+005D RIGHT SQUARE BRACKET U+005D RIGHT SQUARE
2976: BRACKET U+003E GREATER-THAN SIGN (<code title="">]]></code>), or the
2977: end of the file (EOF), whichever comes first. Emit a series of
2978: character tokens consisting of all the characters consumed except
2979: the matching three character sequence at the end (if one was found
2980: before the end of the file).</p>
2981:
2982: <p>Switch to the <a href="#data-state">data state</a>.</p>
2983:
2984: <p>If the end of the file was reached, reconsume the EOF
2985: character.</p>
2986:
2987:
2988:
2989: <h5 id="tokenizing-character-references"><span class="secno">9.2.4.39 </span>Tokenizing character references</h5>
2990:
2991: <p>This section defines how to <dfn id="consume-a-character-reference">consume a character
2992: reference</dfn>. This definition is used when parsing character
2993: references <a href="#character-reference-data-state" title="character reference data state">in
2994: text</a> and <a href="#character-reference-in-attribute-value-state" title="character reference in attribute value
2995: state">in attributes</a>.</p>
2996:
2997: <p>The behavior depends on the identity of the next character (the
2998: one immediately after the U+0026 AMPERSAND character):</p>
2999:
3000: <dl class="switch"><dt>U+0009 CHARACTER TABULATION</dt>
3001: <dt>U+000A LINE FEED (LF)</dt>
3002: <dt>U+000C FORM FEED (FF)</dt>
3003: <!--<dt>U+000D CARRIAGE RETURN (CR)</dt>-->
3004: <dt>U+0020 SPACE</dt>
3005: <dt>U+003C LESS-THAN SIGN</dt>
3006: <dt>U+0026 AMPERSAND</dt>
3007: <dt>EOF</dt>
3008: <dt>The <dfn id="additional-allowed-character">additional allowed character</dfn>, if there is one</dt>
3009:
3010: <dd>Not a character reference. No characters are consumed, and
3011: nothing is returned. (This is not an error, either.)</dd>
3012:
3013:
3014: <dt>U+0023 NUMBER SIGN (#)</dt>
3015:
3016: <dd>
3017:
3018: <p>Consume the U+0023 NUMBER SIGN.</p>
3019:
3020: <p>The behavior further depends on the character after the U+0023
3021: NUMBER SIGN:</p>
3022:
3023: <dl class="switch"><dt>U+0078 LATIN SMALL LETTER X</dt>
3024: <dt>U+0058 LATIN CAPITAL LETTER X</dt>
3025:
3026: <dd>
3027:
3028: <p>Consume the X.</p>
3029:
3030: <p>Follow the steps below, but using the range of characters
3031: U+0030 DIGIT ZERO through to U+0039 DIGIT NINE, U+0061 LATIN
3032: SMALL LETTER A through to U+0066 LATIN SMALL LETTER F, and
3033: U+0041 LATIN CAPITAL LETTER A, through to U+0046 LATIN CAPITAL
3034: LETTER F (in other words, 0-9, A-F, a-f).</p>
3035:
3036: <p>When it comes to interpreting the number, interpret it as a
3037: hexadecimal number.</p>
3038:
3039: </dd>
3040:
3041:
3042: <dt>Anything else</dt>
3043:
3044: <dd>
3045:
3046: <p>Follow the steps below, but using the range of characters
3047: U+0030 DIGIT ZERO through to U+0039 DIGIT NINE (i.e. just
3048: 0-9).</p>
3049:
3050: <p>When it comes to interpreting the number, interpret it as a
3051: decimal number.</p>
3052:
3053: </dd>
3054:
3055: </dl><p>Consume as many characters as match the range of characters
3056: given above.</p>
3057:
3058: <p>If no characters match the range, then don't consume any
3059: characters (and unconsume the U+0023 NUMBER SIGN character and, if
3060: appropriate, the X character). This is a <a href="#parse-error">parse
3061: error</a>; nothing is returned.</p>
3062:
3063: <p>Otherwise, if the next character is a U+003B SEMICOLON, consume
3064: that too. If it isn't, there is a <a href="#parse-error">parse
3065: error</a>.</p>
3066:
3067: <p>If one or more characters match the range, then take them all
3068: and interpret the string of characters as a number (either
3069: hexadecimal or decimal as appropriate).</p>
3070:
3071: <p>If that number is one of the numbers in the first column of the
3072: following table, then this is a <a href="#parse-error">parse error</a>. Find the
3073: row with that number in the first column, and return a character
3074: token for the Unicode character given in the second column of that
3075: row.</p>
3076:
3077: <table><thead><tr><th>Number </th><th colspan="2">Unicode character
3078: </th></tr></thead><tbody><tr><td>0x00 </td><td>U+FFFD </td><td>REPLACEMENT CHARACTER
3079: </td></tr><tr><td>0x0D </td><td>U+000A </td><td>LINE FEED (LF)
3080: </td></tr><tr><td>0x80 </td><td>U+20AC </td><td>EURO SIGN ('€')
3081: </td></tr><tr><td>0x81 </td><td>U+0081 </td><td><control>
3082: </td></tr><tr><td>0x82 </td><td>U+201A </td><td>SINGLE LOW-9 QUOTATION MARK ('‚')
3083: </td></tr><tr><td>0x83 </td><td>U+0192 </td><td>LATIN SMALL LETTER F WITH HOOK ('ƒ')
3084: </td></tr><tr><td>0x84 </td><td>U+201E </td><td>DOUBLE LOW-9 QUOTATION MARK ('„')
3085: </td></tr><tr><td>0x85 </td><td>U+2026 </td><td>HORIZONTAL ELLIPSIS ('…')
3086: </td></tr><tr><td>0x86 </td><td>U+2020 </td><td>DAGGER ('†')
3087: </td></tr><tr><td>0x87 </td><td>U+2021 </td><td>DOUBLE DAGGER ('‡')
3088: </td></tr><tr><td>0x88 </td><td>U+02C6 </td><td>MODIFIER LETTER CIRCUMFLEX ACCENT ('ˆ')
3089: </td></tr><tr><td>0x89 </td><td>U+2030 </td><td>PER MILLE SIGN ('‰')
3090: </td></tr><tr><td>0x8A </td><td>U+0160 </td><td>LATIN CAPITAL LETTER S WITH CARON ('Š')
3091: </td></tr><tr><td>0x8B </td><td>U+2039 </td><td>SINGLE LEFT-POINTING ANGLE QUOTATION MARK ('‹')
3092: </td></tr><tr><td>0x8C </td><td>U+0152 </td><td>LATIN CAPITAL LIGATURE OE ('Œ')
3093: </td></tr><tr><td>0x8D </td><td>U+008D </td><td><control>
3094: </td></tr><tr><td>0x8E </td><td>U+017D </td><td>LATIN CAPITAL LETTER Z WITH CARON ('Ž')
3095: </td></tr><tr><td>0x8F </td><td>U+008F </td><td><control>
3096: </td></tr><tr><td>0x90 </td><td>U+0090 </td><td><control>
3097: </td></tr><tr><td>0x91 </td><td>U+2018 </td><td>LEFT SINGLE QUOTATION MARK ('‘')
3098: </td></tr><tr><td>0x92 </td><td>U+2019 </td><td>RIGHT SINGLE QUOTATION MARK ('’')
3099: </td></tr><tr><td>0x93 </td><td>U+201C </td><td>LEFT DOUBLE QUOTATION MARK ('“')
3100: </td></tr><tr><td>0x94 </td><td>U+201D </td><td>RIGHT DOUBLE QUOTATION MARK ('”')
3101: </td></tr><tr><td>0x95 </td><td>U+2022 </td><td>BULLET ('•')
3102: </td></tr><tr><td>0x96 </td><td>U+2013 </td><td>EN DASH ('–')
3103: </td></tr><tr><td>0x97 </td><td>U+2014 </td><td>EM DASH ('—')
3104: </td></tr><tr><td>0x98 </td><td>U+02DC </td><td>SMALL TILDE ('˜')
3105: </td></tr><tr><td>0x99 </td><td>U+2122 </td><td>TRADE MARK SIGN ('™')
3106: </td></tr><tr><td>0x9A </td><td>U+0161 </td><td>LATIN SMALL LETTER S WITH CARON ('š')
3107: </td></tr><tr><td>0x9B </td><td>U+203A </td><td>SINGLE RIGHT-POINTING ANGLE QUOTATION MARK ('›')
3108: </td></tr><tr><td>0x9C </td><td>U+0153 </td><td>LATIN SMALL LIGATURE OE ('œ')
3109: </td></tr><tr><td>0x9D </td><td>U+009D </td><td><control>
3110: </td></tr><tr><td>0x9E </td><td>U+017E </td><td>LATIN SMALL LETTER Z WITH CARON ('ž')
3111: </td></tr><tr><td>0x9F </td><td>U+0178 </td><td>LATIN CAPITAL LETTER Y WITH DIAERESIS ('Ÿ')
1.18 mike 3112: </td></tr></tbody></table><p>Otherwise, if the number is greater than 0x10FFFF, then this is
3113: a <a href="#parse-error">parse error</a>. Return a U+FFFD REPLACEMENT
3114: CHARACTER.</p>
3115:
3116: <p>Otherwise, return a character token for the Unicode character
1.1 mike 3117: whose code point is that number.
3118:
3119: <!-- this is the same as the equivalent list in the input stream
3120: section -->
3121: If the number is in the range 0x0001 to 0x0008, <!-- HT, LF
3122: allowed --> <!-- U+000B is in the next list --> <!-- FF, CR
3123: allowed --> 0x000E to 0x001F, <!-- ASCII allowed --> 0x007F <!--to
3124: 0x0084, (0x0085 NEL not allowed), 0x0086--> to 0x009F, 0xD800 to
3125: 0xDFFF<!-- surrogates not allowed -->, 0xFDD0 to 0xFDEF, or is one
3126: of 0x000B, 0xFFFE, 0xFFFF, 0x1FFFE, 0x1FFFF, 0x2FFFE, 0x2FFFF,
3127: 0x3FFFE, 0x3FFFF, 0x4FFFE, 0x4FFFF, 0x5FFFE, 0x5FFFF, 0x6FFFE,
3128: 0x6FFFF, 0x7FFFE, 0x7FFFF, 0x8FFFE, 0x8FFFF, 0x9FFFE, 0x9FFFF,
3129: 0xAFFFE, 0xAFFFF, 0xBFFFE, 0xBFFFF, 0xCFFFE, 0xCFFFF, 0xDFFFE,
3130: 0xDFFFF, 0xEFFFE, 0xEFFFF, 0xFFFFE, 0xFFFFF, 0x10FFFE, or
1.18 mike 3131: 0x10FFFF, then this is a <a href="#parse-error">parse error</a>.</p>
1.1 mike 3132:
3133: </dd>
3134:
3135:
3136: <dt>Anything else</dt>
3137:
3138: <dd>
3139:
3140: <p>Consume the maximum number of characters possible, with the
3141: consumed characters matching one of the identifiers in the first
3142: column of the <a href="named-character-references.html#named-character-references">named character references</a> table (in a
3143: <a href="infrastructure.html#case-sensitive">case-sensitive</a> manner).</p>
3144:
3145: <p>If no match can be made, then this is a <a href="#parse-error">parse
3146: error</a>. No characters are consumed, and nothing is
3147: returned.</p>
3148:
3149: <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>
3150:
3151: <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
3152: attribute</a>, and the last character matched is not a U+003B
3153: SEMICOLON (<code title="">;</code>), and the next character is in
3154: the range U+0030 DIGIT ZERO to U+0039 DIGIT NINE, U+0041 LATIN
3155: CAPITAL LETTER A to U+005A LATIN CAPITAL LETTER Z, or U+0061 LATIN
3156: SMALL LETTER A to U+007A LATIN SMALL LETTER Z, then, for
3157: historical reasons, all the characters that were matched after the
3158: U+0026 AMPERSAND (&) must be unconsumed, and nothing is
3159: returned.</p>
3160:
3161: <p>Otherwise, return a character token for the character
3162: corresponding to the character reference name (as given by the
3163: second column of the <a href="named-character-references.html#named-character-references">named character references</a>
3164: table).</p>
3165:
3166: <div class="example">
3167:
3168: <p>If the markup contains <code title="">I'm &notit; I tell
3169: you</code>, the character reference is parsed as "not", as in,
3170: <code title="">I'm ¬it; I tell you</code>. But if the markup
3171: was <code title="">I'm &notin; I tell you</code>, the
3172: character reference would be parsed as "notin;", resulting in
3173: <code title="">I'm ∉ I tell you</code>.</p>
3174:
3175: </div>
3176:
3177: </dd>
3178:
3179: </dl><h4 id="tree-construction"><span class="secno">9.2.5 </span><dfn>Tree construction</dfn></h4>
3180:
3181: <p>The input to the tree construction stage is a sequence of tokens
3182: from the <a href="#tokenization">tokenization</a> stage. The tree construction
3183: stage is associated with a DOM <code>Document</code> object when a
3184: parser is created. The "output" of this stage consists of
3185: dynamically modifying or extending that document's DOM tree.</p>
3186:
3187: <p>This specification does not define when an interactive user agent
3188: has to render the <code>Document</code> so that it is available to
3189: the user, or when it has to begin accepting user input.</p>
3190:
3191: <p>As each token is emitted from the tokenizer, the user agent must
3192: process the token according to the rules given in the section
3193: corresponding to the current <a href="#insertion-mode">insertion mode</a>.</p>
3194:
3195: <p>When the steps below require the UA to <dfn id="insert-a-character">insert a
3196: character</dfn> into a node, if that node has a child immediately
3197: before where the character is to be inserted, and that child is a
3198: <code>Text</code> node, and that <code>Text</code> node was the last
3199: node that the parser inserted into the document, then the character
3200: must be appended to that <code>Text</code> node; otherwise, a new
3201: <code>Text</code> node whose data is just that character must be
3202: inserted in the appropriate place.</p>
3203:
3204: <div class="example">
3205:
3206: <p>Here are some sample inputs to the parser and the corresponding
3207: number of text nodes that they result in, assuming a user agent
3208: that executes scripts.</p>
3209:
3210: <table><thead><tr><th>Input </th><th>Number of text nodes
3211: </th></tr></thead><tbody><tr><td><pre>A<script>
3212: var script = document.getElementsByTagName('script')[0];
3213: document.body.removeChild(script);
3214: </script>B</pre>
3215: </td><td>Two adjacent text nodes in the document, containing "A" and "B".
3216: </td></tr><tr><td><pre>A<script>
3217: var text = document.createTextNode('B');
3218: document.body.appendChild(text);
3219: </script>C</pre>
3220: </td><td>Four text nodes; "A" before the script, the script's contents, "B" after the script, and then, immediately after that, "C".
3221: </td></tr><tr><td><pre>A<script>
3222: var text = document.getElementsByTagName('script')[0].firstChild;
3223: text.data = 'B';
3224: document.body.appendChild(text);
3225: </script>B</pre>
3226: </td><td>Two adjacent text nodes in the document, containing "A" and "BB".
3227: </td></tr><tr><td><pre>A<table>B<tr>C</tr>C</table></pre>
3228: </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>.)
3229: </td></tr><tr><td><pre>A<table><tr> B</tr> B</table></pre>
3230: </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>.)
3231: </td></tr><tr><td><pre>A<table><tr> B</tr> </em>C</table></pre>
3232: </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.)
3233: </td></tr></tbody></table></div>
3234:
3235: <p id="mutation-during-parsing">DOM mutation events must not fire
3236: for changes caused by the UA parsing the document. (Conceptually,
3237: the parser is not mutating the DOM, it is constructing it.) This
1.159 mike 3238: 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 3239:
3240: <p class="note">Not all of the tag names mentioned below are
3241: conformant tag names in this specification; many are included to
3242: handle legacy content. They still form part of the algorithm that
3243: implementations are required to implement to claim conformance.</p>
3244:
3245: <p class="note">The algorithm described below places no limit on the
3246: depth of the DOM tree generated, or on the length of tag names,
3247: attribute names, attribute values, text nodes, etc. While
3248: implementors are encouraged to avoid arbitrary limits, it is
3249: recognized that <a href="infrastructure.html#hardwareLimitations">practical
3250: concerns</a> will likely force user agents to impose nesting
3251: depths.</p>
3252:
3253:
3254: <h5 id="creating-and-inserting-elements"><span class="secno">9.2.5.1 </span>Creating and inserting elements</h5>
3255:
3256: <p>When the steps below require the UA to <dfn id="create-an-element-for-the-token" title="create an
3257: element for the token">create an element for a token</dfn> in a
3258: particular namespace, the UA must create a node implementing the
3259: interface appropriate for the element type corresponding to the tag
3260: name of the token in the given namespace (as given in the
3261: specification that defines that element, e.g. for an <code><a href="text-level-semantics.html#the-a-element">a</a></code>
3262: element in the <a href="#html-namespace-0">HTML namespace</a>, this specification
3263: defines it to be the <code><a href="text-level-semantics.html#htmlanchorelement">HTMLAnchorElement</a></code> interface), with
3264: the tag name being the name of that element, with the node being in
3265: the given namespace, and with the attributes on the node being those
3266: given in the given token.</p>
3267:
3268: <p>The interface appropriate for an element in the <a href="#html-namespace-0">HTML
3269: namespace</a> that is not defined in this specification is
1.44 mike 3270: <code><a href="dom.html#htmlunknownelement">HTMLUnknownElement</a></code>. Element in other namespaces whose
1.1 mike 3271: interface is not defined by that namespace's specification must use
3272: the interface <code>Element</code>.</p>
3273:
3274: <p>When a <a href="forms.html#category-reset" title="category-reset">resettable</a> element is
3275: created in this manner, its <a href="forms.html#concept-form-reset-control" title="concept-form-reset-control">reset algorithm</a> must be
3276: invoked once the attributes are set. (This initializes the element's
3277: <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
3278: attributes.)</p>
3279:
3280: <hr><p>When the steps below require the UA to <dfn id="insert-an-html-element">insert an HTML
3281: element</dfn> for a token, the UA must first <a href="#create-an-element-for-the-token">create an element
3282: for the token</a> in the <a href="#html-namespace-0">HTML namespace</a>, and then
3283: append this node to the <a href="#current-node">current node</a>, and push it onto
3284: the <a href="#stack-of-open-elements">stack of open elements</a> so that it is the new
3285: <a href="#current-node">current node</a>.</p>
3286:
3287: <p>The steps below may also require that the UA insert an HTML
3288: element in a particular place, in which case the UA must follow the
3289: same steps except that it must insert or append the new node in the
3290: location specified instead of appending it to the <a href="#current-node">current
3291: node</a>. (This happens in particular during the parsing of
3292: tables with invalid content.)</p>
3293:
3294: <p>If an element created by the <a href="#insert-an-html-element">insert an HTML element</a>
3295: algorithm is a <a href="forms.html#form-associated-element">form-associated element</a>, and the
3296: <a href="#form-element-pointer"><code title="">form</code> element pointer</a> is not null,
3297: 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
3298: <a href="forms.html#concept-form-association" title="concept-form-association">associate</a> the newly
3299: created element with the <code><a href="forms.html#the-form-element">form</a></code> element pointed to by the
3300: <a href="#form-element-pointer"><code title="">form</code> element pointer</a> before
3301: inserting it wherever it is to be inserted.</p>
3302:
3303: <hr><p>When the steps below require the UA to <dfn id="insert-a-foreign-element">insert a foreign
3304: element</dfn> for a token, the UA must first <a href="#create-an-element-for-the-token">create an element
3305: for the token</a> in the given namespace, and then append this
3306: node to the <a href="#current-node">current node</a>, and push it onto the
3307: <a href="#stack-of-open-elements">stack of open elements</a> so that it is the new
3308: <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>
3309: whose value is not exactly the same as the element's namespace, that
3310: is a <a href="#parse-error">parse error</a>. Similarly, if the newly created
3311: element has an <code title="">xmlns:xlink</code> attribute in the
3312: <a href="#xmlns-namespace">XMLNS namespace</a> whose value is not the <a href="#xlink-namespace">XLink
3313: Namespace</a>, that is a <a href="#parse-error">parse error</a>.</p>
3314:
3315: <p>When the steps below require the user agent to <dfn id="adjust-mathml-attributes">adjust MathML
3316: attributes</dfn> for a token, then, if the token has an attribute
3317: named <code title="">definitionurl</code>, change its name to <code title="">definitionURL</code> (note the case difference).</p>
3318:
3319: <p>When the steps below require the user agent to <dfn id="adjust-svg-attributes">adjust SVG
3320: attributes</dfn> for a token, then, for each attribute on the token
3321: whose attribute name is one of the ones in the first column of the
3322: following table, change the attribute's name to the name given in
3323: the corresponding cell in the second column. (This fixes the case of
3324: SVG attributes that are not all lowercase.)</p>
3325:
3326: <table><thead><tr><th> Attribute name on token </th><th> Attribute name on element
3327: </th></tr></thead><tbody><tr><td> <code title="">attributename</code> </td><td> <code title="">attributeName</code>
3328: </td></tr><tr><td> <code title="">attributetype</code> </td><td> <code title="">attributeType</code>
3329: </td></tr><tr><td> <code title="">basefrequency</code> </td><td> <code title="">baseFrequency</code>
3330: </td></tr><tr><td> <code title="">baseprofile</code> </td><td> <code title="">baseProfile</code>
3331: </td></tr><tr><td> <code title="">calcmode</code> </td><td> <code title="">calcMode</code>
3332: </td></tr><tr><td> <code title="">clippathunits</code> </td><td> <code title="">clipPathUnits</code>
3333: </td></tr><tr><td> <code title="">contentscripttype</code> </td><td> <code title="">contentScriptType</code>
3334: </td></tr><tr><td> <code title="">contentstyletype</code> </td><td> <code title="">contentStyleType</code>
3335: </td></tr><tr><td> <code title="">diffuseconstant</code> </td><td> <code title="">diffuseConstant</code>
3336: </td></tr><tr><td> <code title="">edgemode</code> </td><td> <code title="">edgeMode</code>
3337: </td></tr><tr><td> <code title="">externalresourcesrequired</code> </td><td> <code title="">externalResourcesRequired</code>
3338: </td></tr><tr><td> <code title="">filterres</code> </td><td> <code title="">filterRes</code>
3339: </td></tr><tr><td> <code title="">filterunits</code> </td><td> <code title="">filterUnits</code>
3340: </td></tr><tr><td> <code title="">glyphref</code> </td><td> <code title="">glyphRef</code>
3341: </td></tr><tr><td> <code title="">gradienttransform</code> </td><td> <code title="">gradientTransform</code>
3342: </td></tr><tr><td> <code title="">gradientunits</code> </td><td> <code title="">gradientUnits</code>
3343: </td></tr><tr><td> <code title="">kernelmatrix</code> </td><td> <code title="">kernelMatrix</code>
3344: </td></tr><tr><td> <code title="">kernelunitlength</code> </td><td> <code title="">kernelUnitLength</code>
3345: </td></tr><tr><td> <code title="">keypoints</code> </td><td> <code title="">keyPoints</code>
3346: </td></tr><tr><td> <code title="">keysplines</code> </td><td> <code title="">keySplines</code>
3347: </td></tr><tr><td> <code title="">keytimes</code> </td><td> <code title="">keyTimes</code>
3348: </td></tr><tr><td> <code title="">lengthadjust</code> </td><td> <code title="">lengthAdjust</code>
3349: </td></tr><tr><td> <code title="">limitingconeangle</code> </td><td> <code title="">limitingConeAngle</code>
3350: </td></tr><tr><td> <code title="">markerheight</code> </td><td> <code title="">markerHeight</code>
3351: </td></tr><tr><td> <code title="">markerunits</code> </td><td> <code title="">markerUnits</code>
3352: </td></tr><tr><td> <code title="">markerwidth</code> </td><td> <code title="">markerWidth</code>
3353: </td></tr><tr><td> <code title="">maskcontentunits</code> </td><td> <code title="">maskContentUnits</code>
3354: </td></tr><tr><td> <code title="">maskunits</code> </td><td> <code title="">maskUnits</code>
3355: </td></tr><tr><td> <code title="">numoctaves</code> </td><td> <code title="">numOctaves</code>
3356: </td></tr><tr><td> <code title="">pathlength</code> </td><td> <code title="">pathLength</code>
3357: </td></tr><tr><td> <code title="">patterncontentunits</code> </td><td> <code title="">patternContentUnits</code>
3358: </td></tr><tr><td> <code title="">patterntransform</code> </td><td> <code title="">patternTransform</code>
3359: </td></tr><tr><td> <code title="">patternunits</code> </td><td> <code title="">patternUnits</code>
3360: </td></tr><tr><td> <code title="">pointsatx</code> </td><td> <code title="">pointsAtX</code>
3361: </td></tr><tr><td> <code title="">pointsaty</code> </td><td> <code title="">pointsAtY</code>
3362: </td></tr><tr><td> <code title="">pointsatz</code> </td><td> <code title="">pointsAtZ</code>
3363: </td></tr><tr><td> <code title="">preservealpha</code> </td><td> <code title="">preserveAlpha</code>
3364: </td></tr><tr><td> <code title="">preserveaspectratio</code> </td><td> <code title="">preserveAspectRatio</code>
3365: </td></tr><tr><td> <code title="">primitiveunits</code> </td><td> <code title="">primitiveUnits</code>
3366: </td></tr><tr><td> <code title="">refx</code> </td><td> <code title="">refX</code>
3367: </td></tr><tr><td> <code title="">refy</code> </td><td> <code title="">refY</code>
3368: </td></tr><tr><td> <code title="">repeatcount</code> </td><td> <code title="">repeatCount</code>
3369: </td></tr><tr><td> <code title="">repeatdur</code> </td><td> <code title="">repeatDur</code>
3370: </td></tr><tr><td> <code title="">requiredextensions</code> </td><td> <code title="">requiredExtensions</code>
3371: </td></tr><tr><td> <code title="">requiredfeatures</code> </td><td> <code title="">requiredFeatures</code>
3372: </td></tr><tr><td> <code title="">specularconstant</code> </td><td> <code title="">specularConstant</code>
3373: </td></tr><tr><td> <code title="">specularexponent</code> </td><td> <code title="">specularExponent</code>
3374: </td></tr><tr><td> <code title="">spreadmethod</code> </td><td> <code title="">spreadMethod</code>
3375: </td></tr><tr><td> <code title="">startoffset</code> </td><td> <code title="">startOffset</code>
3376: </td></tr><tr><td> <code title="">stddeviation</code> </td><td> <code title="">stdDeviation</code>
3377: </td></tr><tr><td> <code title="">stitchtiles</code> </td><td> <code title="">stitchTiles</code>
3378: </td></tr><tr><td> <code title="">surfacescale</code> </td><td> <code title="">surfaceScale</code>
3379: </td></tr><tr><td> <code title="">systemlanguage</code> </td><td> <code title="">systemLanguage</code>
3380: </td></tr><tr><td> <code title="">tablevalues</code> </td><td> <code title="">tableValues</code>
3381: </td></tr><tr><td> <code title="">targetx</code> </td><td> <code title="">targetX</code>
3382: </td></tr><tr><td> <code title="">targety</code> </td><td> <code title="">targetY</code>
3383: </td></tr><tr><td> <code title="">textlength</code> </td><td> <code title="">textLength</code>
3384: </td></tr><tr><td> <code title="">viewbox</code> </td><td> <code title="">viewBox</code>
3385: </td></tr><tr><td> <code title="">viewtarget</code> </td><td> <code title="">viewTarget</code>
3386: </td></tr><tr><td> <code title="">xchannelselector</code> </td><td> <code title="">xChannelSelector</code>
3387: </td></tr><tr><td> <code title="">ychannelselector</code> </td><td> <code title="">yChannelSelector</code>
3388: </td></tr><tr><td> <code title="">zoomandpan</code> </td><td> <code title="">zoomAndPan</code>
3389: </td></tr></tbody></table><p>When the steps below require the user agent to <dfn id="adjust-foreign-attributes">adjust
3390: foreign attributes</dfn> for a token, then, if any of the attributes
3391: on the token match the strings given in the first column of the
3392: following table, let the attribute be a namespaced attribute, with
3393: the prefix being the string given in the corresponding cell in the
3394: second column, the local name being the string given in the
3395: corresponding cell in the third column, and the namespace being the
3396: namespace given in the corresponding cell in the fourth
3397: column. (This fixes the use of namespaced attributes, in particular
3398: <a href="dom.html#attr-xml-lang" title="attr-xml-lang"><code title="">lang</code> attributes in
3399: the <span>XML namespace</span></a>.)</p>
3400:
3401: <table><thead><tr><th> Attribute name </th><th> Prefix </th><th> Local name </th><th> Namespace
3402: </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>
3403: </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>
3404: </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>
3405: </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>
3406: </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>
3407: </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>
3408: </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>
3409: </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 -->
3410: </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>
3411: </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>
3412: </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>
3413: </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 3414: </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 3415: <dfn id="generic-rcdata-element-parsing-algorithm">generic RCDATA element parsing algorithm</dfn> consist of the
3416: following steps. These algorithms are always invoked in response to
3417: a start tag token.</p>
3418:
3419: <ol><li><p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p></li>
3420:
1.91 mike 3421: <li><p>If the algorithm that was invoked is the <a href="#generic-raw-text-element-parsing-algorithm">generic raw
3422: text element parsing algorithm</a>, switch the tokenizer's
3423: <a href="#content-model-flag">content model flag</a> to the RAWTEXT state; otherwise the
1.1 mike 3424: algorithm invoked was the <a href="#generic-rcdata-element-parsing-algorithm">generic RCDATA element parsing
3425: algorithm</a>, switch the tokenizer's <a href="#content-model-flag">content model
3426: flag</a> to the RCDATA state.</p></li>
3427:
3428: <li><p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the current
3429: <a href="#insertion-mode">insertion mode</a>.</p>
3430:
1.91 mike 3431: </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
3432: RAWTEXT/RCDATA</a>".</p></li>
1.1 mike 3433:
3434: </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>
3435:
3436: <p>When the steps below require the UA to <dfn id="generate-implied-end-tags">generate implied end
3437: tags</dfn>, then, while the <a href="#current-node">current node</a> is a
3438: <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
3439: <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
3440: <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
3441: <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
3442: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
3443: elements</a>.</p>
3444:
3445: <p>If a step requires the UA to generate implied end tags but lists
3446: an element to exclude from the process, then the UA must perform the
3447: above steps as if that element was not in the above list.</p>
3448:
3449:
3450: <h5 id="foster-parenting"><span class="secno">9.2.5.3 </span>Foster parenting</h5>
3451:
3452: <p>Foster parenting happens when content is misnested in tables.</p>
3453:
3454: <p>When a node <var title="">node</var> is to be <dfn id="foster-parent" title="foster
3455: parent">foster parented</dfn>, the node <var title="">node</var>
3456: must be inserted into the <i><a href="#foster-parent-element">foster parent element</a></i>.</p>
3457:
3458: <p>The <dfn id="foster-parent-element">foster parent element</dfn> is the parent element of the
3459: 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
3460: elements</a>, if there is a <code><a href="tabular-data.html#the-table-element">table</a></code> element and it has
3461: such a parent element. If there is no <code><a href="tabular-data.html#the-table-element">table</a></code> element in
3462: the <a href="#stack-of-open-elements">stack of open elements</a> (<a href="#fragment-case">fragment
3463: case</a>), then the <i><a href="#foster-parent-element">foster parent element</a></i> is the first
3464: element in the <a href="#stack-of-open-elements">stack of open elements</a> (the
1.159 mike 3465: <code><a href="semantics.html#the-html-element-0">html</a></code> element). Otherwise, if there is a
1.1 mike 3466: <code><a href="tabular-data.html#the-table-element">table</a></code> element in the <a href="#stack-of-open-elements">stack of open
3467: elements</a>, but the last <code><a href="tabular-data.html#the-table-element">table</a></code> element in the
3468: <a href="#stack-of-open-elements">stack of open elements</a> has no parent, or its parent
3469: node is not an element, then the <i><a href="#foster-parent-element">foster parent element</a></i> is
3470: the element before the last <code><a href="tabular-data.html#the-table-element">table</a></code> element in the
3471: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
3472:
3473: <p>If the <i><a href="#foster-parent-element">foster parent element</a></i> is the parent element of the
3474: 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
3475: elements</a>, then <var title="">node</var> must be inserted
3476: immediately <em>before</em> the last <code><a href="tabular-data.html#the-table-element">table</a></code> element in
3477: the <a href="#stack-of-open-elements">stack of open elements</a> in the <i><a href="#foster-parent-element">foster parent
3478: element</a></i>; otherwise, <var title="">node</var> must be
3479: <em>appended</em> to the <i><a href="#foster-parent-element">foster parent element</a></i>.</p>
3480:
3481:
3482:
3483: <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>
3484:
3485: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-initial-insertion-mode" title="insertion
3486: mode: initial">initial</a>", tokens must be handled as follows:</p>
3487:
3488: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
3489: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3490: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3491: <dd>
3492: <p>Ignore the token.</p>
3493: </dd>
3494:
3495: <dt>A comment token</dt>
3496: <dd>
3497: <p>Append a <code>Comment</code> node to the <code>Document</code>
3498: object with the <code title="">data</code> attribute set to the
3499: data given in the comment token.</p>
3500: </dd>
3501:
3502: <dt>A DOCTYPE token</dt>
3503: <dd>
3504:
3505: <p>If the DOCTYPE token's name is not a
3506: <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
3507: missing, or the token's system identifier is neither missing nor a
3508: <a href="infrastructure.html#case-sensitive">case-sensitive</a> match for the string
3509: "<code>about:legacy-compat</code>", and none of the sets of
3510: conditions in the following list are matched, then there is a
3511: <a href="#parse-error">parse error</a>. If one of the sets of conditions in the
3512: following list is matched, then there is an <dfn id="obsolete-permitted-doctype">obsolete
3513: permitted DOCTYPE</dfn>.</p>
3514:
3515: <ul><!-- only things that trigger no-quirks mode and were valid in
3516: 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 3517: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3518: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD HTML 4.0//EN</code>", and the
3519: token's system identifier is either missing or the
3520: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">http://www.w3.org/TR/REC-html40/strict.dtd</code>".</li>
3521:
3522: <li>The DOCTYPE token's name is an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.98 mike 3523: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3524: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD HTML 4.01//EN</code>", and the
3525: token's system identifier is either missing or the
3526: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">http://www.w3.org/TR/html4/strict.dtd</code>".</li>
3527:
3528: <li>The DOCTYPE token's name is an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.98 mike 3529: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3530: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD XHTML 1.0 Strict//EN</code>",
3531: and the token's system identifier is the
3532: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</code>".</li>
3533:
3534: <li>The DOCTYPE token's name is an <a href="infrastructure.html#ascii-case-insensitive">ASCII
1.98 mike 3535: case-insensitive</a> match for the string "<code title="">html</code>", the token's public identifier is the
1.1 mike 3536: <a href="infrastructure.html#case-sensitive">case-sensitive</a> string "<code title="">-//W3C//DTD XHTML 1.1//EN</code>", and the
3537: token's system identifier is the <a href="infrastructure.html#case-sensitive">case-sensitive</a>
3538: string "<code title="">http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd</code>".</li>
3539:
3540: </ul><p>Conformance checkers may, based on the values (including
3541: presence or lack thereof) of the DOCTYPE token's name, public
3542: identifier, or system identifier, switch to a conformance checking
3543: mode for another language (e.g. based on the DOCTYPE token a
3544: conformance checker could recognize that the document is an
3545: HTML 4-era document, and defer to an HTML 4 conformance
3546: checker.)</p>
3547:
3548: <p>Append a <code>DocumentType</code> node to the
3549: <code>Document</code> node, with the <code title="">name</code>
3550: attribute set to the name given in the DOCTYPE token, or the empty
3551: string if the name was missing; the <code title="">publicId</code>
3552: attribute set to the public identifier given in the DOCTYPE token,
3553: or the empty string if the public identifier was missing; the
3554: <code title="">systemId</code> attribute set to the system
3555: identifier given in the DOCTYPE token, or the empty string if the
3556: system identifier was missing; and the other attributes specific
3557: to <code>DocumentType</code> objects set to null and empty lists
3558: as appropriate. Associate the <code>DocumentType</code> node with
3559: the <code>Document</code> object so that it is returned as the
3560: value of the <code title="">doctype</code> attribute of the
3561: <code>Document</code> object.</p>
3562:
3563: <p id="quirks-mode-doctypes">Then, if the DOCTYPE token matches
3564: one of the conditions in the following list, then set the
3565: <code>Document</code> to <a href="dom.html#quirks-mode">quirks mode</a>:</p>
3566:
3567: <ul class="brief"><li> The <i>force-quirks flag</i> is set to <i>on</i>. </li>
3568: <li> The name is set to anything other than "<code title="">HTML</code>". </li>
3569: <li> The public identifier starts with: "<code title="">+//Silmaril//dtd html Pro v0r11 19970101//<!--EN--></code>" </li>
3570: <li> The public identifier starts with: "<code title="">-//AdvaSoft Ltd//DTD HTML 3.0 asWedit + extensions//<!--EN--></code>" </li>
3571: <li> The public identifier starts with: "<code title="">-//AS//DTD HTML 3.0 asWedit + extensions//<!--EN--></code>" </li>
3572: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Level 1//<!--EN--></code>" </li>
3573: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Level 2//<!--EN--></code>" </li>
3574: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Strict Level 1//<!--EN--></code>" </li>
3575: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Strict Level 2//<!--EN--></code>" </li>
3576: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0 Strict//<!--EN--></code>" </li>
3577: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.0//<!--EN--></code>" </li>
3578: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 2.1E//<!--EN--></code>" </li>
3579: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3.0//<!--EN--></code>" </li>
3580: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML 3.0//EN//</code>" </li>-->
3581: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3.2 Final//<!--EN--></code>" </li>
3582: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3.2//<!--EN--></code>" </li>
3583: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML 3//<!--EN--></code>" </li>
3584: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 0//<!--EN--></code>" </li>
3585: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 0//EN//2.0</code>" </li>-->
3586: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 1//<!--EN--></code>" </li>
3587: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 1//EN//2.0</code>" </li>-->
3588: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 2//<!--EN--></code>" </li>
3589: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 2//EN//2.0</code>" </li>-->
3590: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Level 3//<!--EN--></code>" </li>
3591: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Level 3//EN//3.0</code>" </li>-->
3592: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 0//<!--EN--></code>" </li>
3593: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 0//EN//2.0</code>" </li>-->
3594: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 1//<!--EN--></code>" </li>
3595: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 1//EN//2.0</code>" </li>-->
3596: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 2//<!--EN--></code>" </li>
3597: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 2//EN//2.0</code>" </li>-->
3598: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict Level 3//<!--EN--></code>" </li>
3599: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict Level 3//EN//3.0</code>" </li>-->
3600: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML Strict//<!--EN--></code>" </li>
3601: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict//EN//2.0</code>" </li>-->
3602: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML Strict//EN//3.0</code>" </li>-->
3603: <li> The public identifier starts with: "<code title="">-//IETF//DTD HTML//<!--EN--></code>" </li>
3604: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML//EN//2.0</code>" </li>-->
3605: <!--<li> The public identifier is set to: "<code title="">-//IETF//DTD HTML//EN//3.0</code>" </li>-->
3606: <li> The public identifier starts with: "<code title="">-//Metrius//DTD Metrius Presentational//<!--EN--></code>" </li>
3607: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 2.0 HTML Strict//<!--EN--></code>" </li>
3608: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 2.0 HTML//<!--EN--></code>" </li>
3609: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 2.0 Tables//<!--EN--></code>" </li>
3610: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 3.0 HTML Strict//<!--EN--></code>" </li>
3611: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 3.0 HTML//<!--EN--></code>" </li>
3612: <li> The public identifier starts with: "<code title="">-//Microsoft//DTD Internet Explorer 3.0 Tables//<!--EN--></code>" </li>
3613: <li> The public identifier starts with: "<code title="">-//Netscape Comm. Corp.//DTD HTML//<!--EN--></code>" </li>
3614: <li> The public identifier starts with: "<code title="">-//Netscape Comm. Corp.//DTD Strict HTML//<!--EN--></code>" </li>
3615: <li> The public identifier starts with: "<code title="">-//O'Reilly and Associates//DTD HTML 2.0//<!--EN--></code>" </li>
3616: <li> The public identifier starts with: "<code title="">-//O'Reilly and Associates//DTD HTML Extended 1.0//<!--EN--></code>" </li>
3617: <li> The public identifier starts with: "<code title="">-//O'Reilly and Associates//DTD HTML Extended Relaxed 1.0//<!--EN--></code>" </li>
3618: <li> The public identifier starts with: "<code title="">-//SoftQuad Software//DTD HoTMetaL PRO 6.0::19990601::extensions to HTML 4.0//<!--EN--></code>" </li>
3619: <li> The public identifier starts with: "<code title="">-//SoftQuad//DTD HoTMetaL PRO 4.0::19971010::extensions to HTML 4.0//<!--EN--></code>" </li>
3620: <li> The public identifier starts with: "<code title="">-//Spyglass//DTD HTML 2.0 Extended//<!--EN--></code>" </li>
3621: <li> The public identifier starts with: "<code title="">-//SQ//DTD HTML 2.0 HoTMetaL + extensions//<!--EN--></code>" </li>
3622: <li> The public identifier starts with: "<code title="">-//Sun Microsystems Corp.//DTD HotJava HTML//<!--EN--></code>" </li>
3623: <li> The public identifier starts with: "<code title="">-//Sun Microsystems Corp.//DTD HotJava Strict HTML//<!--EN--></code>" </li>
3624: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3 1995-03-24//<!--EN--></code>" </li>
3625: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2 Draft//<!--EN--></code>" </li>
3626: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2 Final//<!--EN--></code>" </li>
3627: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2//<!--EN--></code>" </li>
3628: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 3.2S Draft//<!--EN--></code>" </li>
3629: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 4.0 Frameset//<!--EN--></code>" </li>
3630: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML 4.0 Transitional//<!--EN--></code>" </li>
3631: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML Experimental 19960712//<!--EN--></code>" </li>
3632: <li> The public identifier starts with: "<code title="">-//W3C//DTD HTML Experimental 970421//<!--EN--></code>" </li>
3633: <li> The public identifier starts with: "<code title="">-//W3C//DTD W3 HTML//<!--EN--></code>" </li>
3634: <li> The public identifier starts with: "<code title="">-//W3O//DTD W3 HTML 3.0//<!--EN--></code>" </li>
3635: <!--<li> The public identifier is set to: "<code title="">-//W3O//DTD W3 HTML 3.0//EN//</code>" </li>-->
3636: <li> The public identifier is set to: "<code title="">-//W3O//DTD W3 HTML Strict 3.0//EN//</code>" </li>
3637: <li> The public identifier starts with: "<code title="">-//WebTechs//DTD Mozilla HTML 2.0//<!--EN--></code>" </li>
3638: <li> The public identifier starts with: "<code title="">-//WebTechs//DTD Mozilla HTML//<!--EN--></code>" </li>
3639: <li> The public identifier is set to: "<code title="">-/W3C/DTD HTML 4.0 Transitional/EN</code>" </li>
3640: <li> The public identifier is set to: "<code title="">HTML</code>" </li>
3641: <li> The system identifier is set to: "<code title="">http://www.ibm.com/data/dtd/v11/ibmxhtml1-transitional.dtd</code>" </li>
3642: <li> The system identifier is missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Frameset//<!--EN--></code>" </li>
3643: <li> The system identifier is missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Transitional//<!--EN--></code>" </li>
3644: </ul><p>Otherwise, if the DOCTYPE token matches one of the conditions
3645: in the following list, then set the <code>Document</code> to
3646: <a href="dom.html#limited-quirks-mode">limited quirks mode</a>:</p>
3647:
3648: <ul class="brief"><li> The public identifier starts with: "<code title="">-//W3C//DTD XHTML 1.0 Frameset//<!--EN--></code>" </li>
3649: <li> The public identifier starts with: "<code title="">-//W3C//DTD XHTML 1.0 Transitional//<!--EN--></code>" </li>
3650: <li> The system identifier is not missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Frameset//<!--EN--></code>" </li>
3651: <li> The system identifier is not missing and the public identifier starts with: "<code title="">-//W3C//DTD HTML 4.01 Transitional//<!--EN--></code>" </li>
3652: </ul><p>The name, system identifier, and public identifier strings must
3653: be compared to the values given in the lists above in an
3654: <a href="infrastructure.html#ascii-case-insensitive">ASCII case-insensitive</a> manner. A system identifier
3655: whose value is the empty string is not considered missing for the
3656: purposes of the conditions above.</p>
3657:
3658: <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>
3659:
3660: </dd>
3661:
3662: <dt>Anything else</dt>
3663: <dd>
3664:
3665: <p><a href="#parse-error">Parse error</a>.</p>
3666:
3667: <p>Set the <code>Document</code> to <a href="dom.html#quirks-mode">quirks mode</a>.</p>
3668:
3669: <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
3670: reprocess the current token.</p>
3671:
3672: </dd>
3673:
3674: </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>
3675:
3676: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-before-html-insertion-mode" title="insertion
3677: mode: before html">before html</a>", tokens must be handled as follows:</p>
3678:
3679: <dl class="switch"><dt>A DOCTYPE token</dt>
3680: <dd>
3681: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3682: </dd>
3683:
3684: <dt>A comment token</dt>
3685: <dd>
3686: <p>Append a <code>Comment</code> node to the <code>Document</code>
3687: object with the <code title="">data</code> attribute set to the
3688: data given in the comment token.</p>
3689: </dd>
3690:
3691: <dt>A character token that is one of U+0009 CHARACTER
3692: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3693: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3694: <dd>
3695: <p>Ignore the token.</p>
3696: </dd>
3697:
3698: <dt>A start tag whose tag name is "html"</dt>
3699: <dd>
3700:
3701: <p><a href="#create-an-element-for-the-token">Create an element for the token</a> in the <a href="#html-namespace-0">HTML
3702: namespace</a>. Append it to the <code>Document</code>
3703: object. Put this element in the <a href="#stack-of-open-elements">stack of open
3704: elements</a>.</p>
3705:
3706: <p id="parser-appcache">If the <code>Document</code> is being
3707: loaded as part of <a href="history.html#navigate" title="navigate">navigation</a> of a
3708: <a href="browsers.html#browsing-context">browsing context</a>, then: if the newly created element
3709: has a <code title="attr-html-manifest"><a href="semantics.html#attr-html-manifest">manifest</a></code> attribute,
3710: then <a href="infrastructure.html#resolve-a-url" title="resolve a url">resolve</a> the value of that
3711: attribute to an <a href="infrastructure.html#absolute-url">absolute URL</a>, relative to the newly
3712: 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 3713: algorithm</a> with the resulting <a href="infrastructure.html#absolute-url">absolute URL</a> with
3714: any <a href="infrastructure.html#url-fragment" title="url-fragment"><fragment></a> component
3715: removed; otherwise, if there is no such attribute or resolving it
3716: fails, run the <a href="offline.html#concept-appcache-init" title="concept-appcache-init">application
3717: cache selection algorithm</a> with no manifest. The algorithm
3718: must be passed the <code>Document</code> object.</p>
1.1 mike 3719:
3720: <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>
3721:
3722: </dd>
3723:
3724: <dt>Anything else</dt>
3725: <dd>
3726:
1.159 mike 3727: <p>Create an <code><a href="semantics.html#the-html-element-0">html</a></code> element. Append it to the
1.1 mike 3728: <code>Document</code> object. Put this element in the <a href="#stack-of-open-elements">stack
3729: of open elements</a>.</p>
3730:
3731: <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
3732: context</a>, then: run the <a href="offline.html#concept-appcache-init" title="concept-appcache-init">application cache selection
3733: algorithm</a> with no manifest, passing it the
3734: <code>Document</code> object.</p>
3735:
3736: <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
3737: reprocess the current token.</p>
3738:
3739: <p class="XXX">Should probably make end tags be ignored, so
3740: that "</head><!-- --><html>" puts the comment before the
3741: root node (or should we?)</p>
3742:
3743: </dd>
3744:
3745: </dl><p>The root element can end up being removed from the
3746: <code>Document</code> object, e.g. by scripts; nothing in particular
3747: happens in such cases, content continues being appended to the nodes
3748: as described in the next section.</p>
3749:
3750:
3751: <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>
3752:
3753: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-before-head-insertion-mode" title="insertion
3754: mode: before head">before head</a>", tokens must be handled as follows:</p>
3755:
3756: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
3757: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3758: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3759: <dd>
3760: <p>Ignore the token.</p> <!-- :-( -->
3761: </dd>
3762:
3763: <dt>A comment token</dt>
3764: <dd>
3765: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
3766: node</a> with the <code title="">data</code> attribute set to
3767: the data given in the comment token.</p>
3768: </dd>
3769:
3770: <dt>A DOCTYPE token</dt>
3771: <dd>
3772: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3773: </dd>
3774:
3775: <dt>A start tag whose tag name is "html"</dt>
3776: <dd>
3777: <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
3778: mode</a>.</p>
3779: </dd>
3780:
3781: <dt>A start tag whose tag name is "head"</dt>
3782: <dd>
3783:
3784: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
3785:
3786: <p>Set the <a href="#head-element-pointer"><code title="">head</code> element pointer</a>
1.159 mike 3787: to the newly created <code><a href="semantics.html#the-head-element-0">head</a></code> element.</p>
1.1 mike 3788:
3789: <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>
3790:
3791: </dd>
3792:
3793: <dt>An end tag whose tag name is one of: "head", "body", "html", "br"</dt>
3794: <dd>
3795:
3796: <p>Act as if a start tag token with the tag name "head" and no
3797: attributes had been seen, then reprocess the current token.</p>
3798:
3799: </dd>
3800:
3801: <dt>Any other end tag</dt>
3802: <dd>
3803:
3804: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3805:
3806: </dd>
3807:
3808: <dt>Anything else</dt>
3809: <dd>
3810:
3811: <p>Act as if a start tag token with the tag name "head" and no
3812: attributes had been seen, then reprocess the current
3813: token.</p>
3814:
3815: </dd>
3816:
3817: </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>
3818:
3819: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inhead" title="insertion
3820: mode: in head">in head</a>", tokens must be handled as follows:</p>
3821:
3822: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
3823: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
3824: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
3825: <dd>
3826: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
3827: the <a href="#current-node">current node</a>.</p>
3828: </dd>
3829:
3830: <dt>A comment token</dt>
3831: <dd>
3832: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
3833: node</a> with the <code title="">data</code> attribute set to
3834: the data given in the comment token.</p>
3835: </dd>
3836:
3837: <dt>A DOCTYPE token</dt>
3838: <dd>
3839: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3840: </dd>
3841:
3842: <dt>A start tag whose tag name is "html"</dt>
3843: <dd>
3844: <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
3845: mode</a>.</p>
3846: </dd>
3847:
3848: <dt>A start tag whose tag name is one of: "base", "command",
3849: "link"</dt>
3850: <dd>
3851:
3852: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
3853: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
3854: elements</a>.</p>
3855:
3856: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
3857: token's <i>self-closing flag</i></a>, if it is set.</p>
3858:
3859: </dd>
3860:
3861: <dt>A start tag whose tag name is "meta"</dt>
3862: <dd>
3863:
3864: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
3865: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
3866: elements</a>.</p>
3867:
3868: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
3869: token's <i>self-closing flag</i></a>, if it is set.</p>
3870:
3871: <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
3872: value is a supported encoding, and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
3873: currently <i>tentative</i>, then <a href="#change-the-encoding">change the
3874: encoding</a> to the encoding given by the value of the
3875: <code title="attr-meta-charset"><a href="semantics.html#attr-meta-charset">charset</a></code> attribute.</p>
3876:
3877: <p>Otherwise, if the element has a <code title="attr-meta-charset"><a href="semantics.html#attr-meta-charset">content</a></code> attribute, and
3878: applying the <a href="infrastructure.html#algorithm-for-extracting-an-encoding-from-a-content-type">algorithm for extracting an encoding from a
3879: Content-Type</a> to its value returns a supported encoding
3880: <var title="">encoding</var>, and the <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
3881: currently <i>tentative</i>, then <a href="#change-the-encoding">change the
3882: encoding</a> to the encoding <var title="">encoding</var>.</p>
3883:
3884: </dd>
3885:
3886: <dt>A start tag whose tag name is "title"</dt>
3887: <dd>
3888: <p>Follow the <a href="#generic-rcdata-element-parsing-algorithm">generic RCDATA element parsing algorithm</a>.</p>
3889: </dd>
3890:
3891: <dt>A start tag whose tag name is "noscript", if the <a href="#scripting-flag">scripting flag</a> is enabled</dt>
3892: <dt>A start tag whose tag name is one of: "noframes", "style"</dt>
3893: <dd>
1.91 mike 3894: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 3895: </dd>
3896:
3897: <dt>A start tag whose tag name is "noscript", if the <a href="#scripting-flag">scripting flag</a> is disabled</dt>
3898: <dd>
3899:
3900: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
3901:
3902: <p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inheadnoscript" title="insertion mode: in head noscript">in head
3903: noscript</a>".</p>
3904:
3905: </dd>
3906:
3907: <dt id="scriptTag">A start tag whose tag name is "script"</dt>
3908: <dd>
3909:
3910: <ol><li><p><a href="#create-an-element-for-the-token">Create an element for the token</a> in the
3911: <a href="#html-namespace-0">HTML namespace</a>.</p></li>
3912:
3913: <li>
3914:
3915: <p>Mark the element as being <a href="semantics.html#parser-inserted">"parser-inserted"</a>.</p>
3916:
3917: <p class="note">This ensures that, if the script is external,
1.159 mike 3918: any <code title="dom-document-write"><a href="embedded-content-0.html#dom-document-write">document.write()</a></code>
1.1 mike 3919: calls in the script will execute in-line, instead of blowing the
3920: document away, as would happen in most other cases. It also
3921: prevents the script from executing until the end tag is
3922: seen.</p>
3923:
3924: </li>
3925:
3926: <li><p>If the parser was originally created for the <a href="#html-fragment-parsing-algorithm">HTML
3927: fragment parsing algorithm</a>, then mark the
3928: <code><a href="semantics.html#script">script</a></code> element as <a href="semantics.html#already-executed">"already
3929: executed"</a>. (<a href="#fragment-case">fragment case</a>)</p></li>
3930:
3931: <li><p>Append the new element to the <a href="#current-node">current node</a>
3932: and push it onto the <a href="#stack-of-open-elements">stack of open
3933: elements</a>.</p></li>
3934:
3935: <li><p>Switch the tokenizer's <a href="#content-model-flag">content model flag</a> to
1.91 mike 3936: the RAWTEXT state.</p></li>
1.1 mike 3937:
3938: <li><p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the current
3939: <a href="#insertion-mode">insertion mode</a>.</p>
3940:
1.91 mike 3941: </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
3942: RAWTEXT/RCDATA</a>".</p></li>
1.1 mike 3943:
3944: </ol></dd>
3945:
3946: <dt>An end tag whose tag name is "head"</dt>
3947: <dd>
3948:
3949: <p>Pop the <a href="#current-node">current node</a> (which will be the
1.159 mike 3950: <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 3951: elements</a>.</p>
3952:
3953: <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>
3954:
3955: </dd>
3956:
3957: <dt>An end tag whose tag name is one of: "body", "html", "br"</dt>
3958: <dd>
3959: <p>Act as described in the "anything else" entry below.</p>
3960: </dd>
3961:
3962: <dt>A start tag whose tag name is "head"</dt>
3963: <dt>Any other end tag</dt>
3964: <dd>
3965: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3966: </dd>
3967:
3968: <dt>Anything else</dt>
3969: <dd>
3970:
3971: <!-- can't get here with an EOF and a fragment case -->
3972:
3973: <p>Act as if an end tag token with the tag name "head" had
3974: been seen, and reprocess the current token.</p>
3975:
3976: <p class="XXX">In certain UAs, <a href="https://bugzilla.mozilla.org/attachment.cgi?id=180157&action=view">some
3977: elements</a> don't trigger the "in body" mode straight away,
3978: but instead get put into the head. Do we want to copy
3979: that?</p>
3980:
3981: </dd>
3982:
3983: </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>
3984:
3985: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inheadnoscript" title="insertion
3986: mode: in head noscript">in head noscript</a>", tokens must be handled as follows:</p>
3987:
3988: <dl class="switch"><dt>A DOCTYPE token</dt>
3989: <dd>
3990: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
3991: </dd>
3992:
3993: <dt>A start tag whose tag name is "html"</dt>
3994: <dd>
3995: <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
3996: mode</a>.</p>
3997: </dd>
3998:
3999: <dt>An end tag whose tag name is "noscript"</dt>
4000: <dd>
4001:
4002: <p>Pop the <a href="#current-node">current node</a> (which will be a
4003: <code><a href="semantics.html#the-noscript-element">noscript</a></code> element) from the <a href="#stack-of-open-elements">stack of open
4004: elements</a>; the new <a href="#current-node">current node</a> will be a
1.159 mike 4005: <code><a href="semantics.html#the-head-element-0">head</a></code> element.</p>
1.1 mike 4006:
4007: <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>
4008:
4009: </dd>
4010:
4011: <dt>A character token that is one of U+0009 CHARACTER
4012: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
4013: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
4014: <dt>A comment token</dt>
4015: <dt>A start tag whose tag name is one of: "link", "meta", "noframes", "style"</dt>
4016: <dd>
4017: <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
4018: mode</a>.</p>
4019: </dd>
4020:
4021: <dt>An end tag whose tag name is "br"</dt>
4022: <dd>
4023: <p>Act as described in the "anything else" entry below.</p>
4024: </dd>
4025:
4026: <dt>A start tag whose tag name is one of: "head", "noscript"</dt>
4027: <dt>Any other end tag</dt>
4028: <dd>
4029: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4030: </dd>
4031:
4032: <dt>Anything else</dt>
4033: <dd>
4034:
4035: <!-- can't get here with an EOF and a fragment case -->
4036:
4037: <p><a href="#parse-error">Parse error</a>. Act as if an end tag with the tag
4038: name "noscript" had been seen and reprocess the current
4039: token.</p>
4040:
4041: </dd>
4042:
4043: </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>
4044:
4045: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-after-head-insertion-mode" title="insertion
4046: mode: after head">after head</a>", tokens must be handled as follows:</p>
4047:
4048: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
4049: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
4050: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
4051: <dd>
4052: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
4053: the <a href="#current-node">current node</a>.</p>
4054: </dd>
4055:
4056: <dt>A comment token</dt>
4057: <dd>
4058: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
4059: node</a> with the <code title="">data</code> attribute set to
4060: the data given in the comment token.</p>
4061: </dd>
4062:
4063: <dt>A DOCTYPE token</dt>
4064: <dd>
4065: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4066: </dd>
4067:
4068: <dt>A start tag whose tag name is "html"</dt>
4069: <dd>
4070: <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
4071: mode</a>.</p>
4072: </dd>
4073:
4074: <dt>A start tag whose tag name is "body"</dt>
4075: <dd>
4076:
4077: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4078:
4079: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4080:
4081: <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>
4082:
4083: </dd>
4084:
4085: <dt>A start tag whose tag name is "frameset"</dt>
4086: <dd>
4087:
4088: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4089:
4090: <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>
4091:
4092: </dd>
4093:
4094: <dt>A start tag token whose tag name is one of: "base", "link",
4095: "meta", "noframes", "script", "style", "title"</dt>
4096: <dd>
4097:
4098: <p><a href="#parse-error">Parse error</a>.</p>
4099:
4100: <p>Push the node pointed to by the <a href="#head-element-pointer"><code title="">head</code> element pointer</a> onto the
4101: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
4102:
4103: <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
4104: mode</a>.</p>
4105:
4106: <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
4107: of open elements</a>.</p>
4108:
4109: <p class="note">The <a href="#head-element-pointer"><code title="">head</code> element
4110: pointer</a> cannot be null at this point.</p>
4111:
4112: </dd>
4113:
4114: <dt>An end tag whose tag name is one of: "body", "html", "br"</dt>
4115: <dd>
4116: <p>Act as described in the "anything else" entry below.</p>
4117: </dd>
4118:
4119: <dt>A start tag whose tag name is "head"</dt>
4120: <dt>Any other end tag</dt>
4121: <dd>
4122: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4123: </dd>
4124:
4125: <dt>Anything else</dt>
4126: <dd>
4127: <p>Act as if a start tag token with the tag name "body" and no
4128: attributes had been seen, then set the <a href="#frameset-ok-flag">frameset-ok
4129: flag</a> back to "ok", and then reprocess the current
4130: token.</p>
4131: </dd>
4132:
4133: </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>
4134:
4135: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inbody" title="insertion
4136: mode: in body">in body</a>", tokens must be handled as follows:</p>
4137:
4138: <dl class="switch"><dt>A character token</dt>
4139: <dd>
4140:
4141: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4142: any.</p>
4143:
4144: <p><a href="#insert-a-character" title="insert a character">Insert the token's
4145: character</a> into the <a href="#current-node">current node</a>.</p>
4146:
4147: <p>If the token is not one of U+0009 CHARACTER TABULATION, U+000A
4148: LINE FEED (LF), U+000C FORM FEED (FF), <!--U+000D CARRIAGE RETURN
4149: (CR),--> or U+0020 SPACE, then set the <a href="#frameset-ok-flag">frameset-ok
4150: flag</a> to "not ok".</p>
4151:
4152: </dd>
4153:
4154: <dt>A comment token</dt>
4155: <dd>
4156: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
4157: node</a> with the <code title="">data</code> attribute set to
4158: the data given in the comment token.</p>
4159: </dd>
4160:
4161: <dt>A DOCTYPE token</dt>
4162: <dd>
4163: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
4164: </dd>
4165:
4166: <dt>A start tag whose tag name is "html"</dt>
4167: <dd>
4168: <p><a href="#parse-error">Parse error</a>. For each attribute on the token,
4169: check to see if the attribute is already present on the top
4170: element of the <a href="#stack-of-open-elements">stack of open elements</a>. If it is not,
4171: add the attribute and its corresponding value to that element.</p>
4172: </dd>
4173:
4174: <dt>A start tag token whose tag name is one of: "base", "command",
4175: "link", "meta", "noframes", "script", "style", "title"</dt>
4176: <dd>
4177: <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
4178: mode</a>.</p>
4179: </dd>
4180:
4181: <dt>A start tag whose tag name is "body"</dt>
4182: <dd>
4183:
4184: <p><a href="#parse-error">Parse error</a>.</p>
4185:
4186: <p>If the second element on the <a href="#stack-of-open-elements">stack of open
1.159 mike 4187: elements</a> is not a <code><a href="semantics.html#the-body-element-0">body</a></code> element, or, if the
1.1 mike 4188: <a href="#stack-of-open-elements">stack of open elements</a> has only one node on it,
4189: then ignore the token. (<a href="#fragment-case">fragment case</a>)</p>
4190:
4191: <p>Otherwise, for each attribute on the token, check to see if
1.159 mike 4192: the attribute is already present on the <code><a href="semantics.html#the-body-element-0">body</a></code>
1.1 mike 4193: element (the second element) on the <a href="#stack-of-open-elements">stack of open
4194: elements</a>. If it is not, add the attribute and its
4195: corresponding value to that element.</p>
4196:
4197: </dd>
4198:
4199: <dt>A start tag whose tag name is "frameset"</dt>
4200: <dd>
4201:
4202: <p><a href="#parse-error">Parse error</a>.</p>
4203:
4204: <p>If the second element on the <a href="#stack-of-open-elements">stack of open
1.159 mike 4205: elements</a> is not a <code><a href="semantics.html#the-body-element-0">body</a></code> element, or, if the
1.1 mike 4206: <a href="#stack-of-open-elements">stack of open elements</a> has only one node on it,
4207: then ignore the token. (<a href="#fragment-case">fragment case</a>)</p>
4208:
4209: <p>If the <a href="#frameset-ok-flag">frameset-ok flag</a> is set to "not ok", ignore
4210: the token.</p>
4211:
4212: <p>Otherwise, run the following steps:</p>
4213:
4214: <ol><li><p>Remove the second element on the <a href="#stack-of-open-elements">stack of open
4215: elements</a> from its parent node, if it has one.</p></li>
4216:
4217: <li><p>Pop all the nodes from the bottom of the <a href="#stack-of-open-elements">stack of
4218: open elements</a>, from the <a href="#current-node">current node</a> up to,
1.159 mike 4219: but not including, the root <code><a href="semantics.html#the-html-element-0">html</a></code> element.</p>
1.1 mike 4220:
4221: </li><li><p><a href="#insert-an-html-element">Insert an HTML element</a> for the
4222: token.</p></li>
4223:
4224: <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>
4225:
4226: </li></ol></dd>
4227:
4228: <dt>An end-of-file token</dt>
4229: <dd>
4230:
4231: <p>If there is a node in the <a href="#stack-of-open-elements">stack of open elements</a>
4232: 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>
4233: 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
4234: <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
4235: <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
4236: <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 4237: <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 4238: this is a <a href="#parse-error">parse error</a>.</p> <!-- (some of those are
4239: fragment cases) -->
4240:
4241: <p><a href="#stop-parsing">Stop parsing</a>.</p>
4242:
4243: </dd>
4244:
4245: <dt>An end tag whose tag name is "body"</dt>
4246: <dd>
4247:
4248: <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
4249: in scope</a>, this is a <a href="#parse-error">parse error</a>; ignore the
4250: token.</p>
4251:
4252: <!-- if we get here, the insertion mode here is forcibly "in
4253: body". -->
4254:
4255: <p>Otherwise, if there is a node in the <a href="#stack-of-open-elements">stack of open
4256: elements</a> that is not either a <code><a href="semantics.html#the-dd-element">dd</a></code> element, a
4257: <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
4258: <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
4259: <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
4260: <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
4261: <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
4262: <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 4263: <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
4264: <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 4265: error</a>.</p> <!-- (some of those are fragment cases, e.g. for
4266: <tbody> you'd have hit the first paragraph since the <body>
4267: wouldn't be in scope, unless it was a fragment case) -->
4268:
4269: <!-- If we ever change the frameset-ok flag to an insertion mode,
4270: then we'd have to somehow keep track of its state when we switch
4271: to after-body. -->
4272:
4273: <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>
4274:
4275: </dd>
4276:
4277: <dt>An end tag whose tag name is "html"</dt>
4278: <dd>
4279:
4280: <p>Act as if an end tag with tag name "body" had been seen,
4281: then, if that token wasn't ignored, reprocess the current
4282: token.</p>
4283:
4284: <p class="note">The fake end tag token here can only be
4285: ignored in the <a href="#fragment-case">fragment case</a>.</p>
4286:
4287: </dd>
4288:
4289: <!-- start tags for non-phrasing flow content elements -->
4290:
4291: <!-- the normal ones -->
4292: <dt>A start tag whose tag name is one of: "address", "article",
1.86 mike 4293: "aside", "blockquote", "center", <!--v2DATAGRID-->"datagrid",
4294: "details", "dialog", "dir", "div", "dl", "fieldset", "figure",
4295: "footer", "header", "hgroup", "menu", "nav", "ol", "p", "section",
4296: "ul"</dt>
1.1 mike 4297: <dd>
4298:
4299: <!-- As of May 2008 this doesn't match any browser exactly, but is
4300: as close to what IE does as I can get without doing the non-tree
4301: DOM nonsense, and thus should actually afford better compatibility
4302: when implemented by the other browsers. -->
4303:
4304: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4305: an element in scope">has a <code>p</code> element in
4306: scope</a>, then act as if an end tag with the tag name
4307: "p" had been seen.</p>
4308:
4309: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4310:
4311: </dd>
4312:
4313: <!-- as normal, but close h1-h6 if it's the current node -->
4314: <dt>A start tag whose tag name is one of: "h1", "h2", "h3", "h4",
4315: "h5", "h6"</dt>
4316: <dd>
4317:
4318: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4319: an element in scope">has a <code>p</code> element in
4320: scope</a>, then act as if an end tag with the tag name
4321: "p" had been seen.</p>
4322:
4323: <p>If the <a href="#current-node">current node</a> is an element whose tag name
4324: is one of "h1", "h2", "h3", "h4", "h5", or "h6", then this is a
4325: <a href="#parse-error">parse error</a>; pop the <a href="#current-node">current node</a> off
4326: the <a href="#stack-of-open-elements">stack of open elements</a>.</p>
4327: <!-- See https://bugs.webkit.org/show_bug.cgi?id=12646 -->
4328:
4329: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4330:
4331: </dd>
4332:
4333: <!-- as normal, but drops leading newline -->
4334: <dt>A start tag whose tag name is one of: "pre", "listing"</dt>
4335: <dd>
4336:
4337: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4338: an element in scope">has a <code>p</code> element in
4339: scope</a>, then act as if an end tag with the tag name
4340: "p" had been seen.</p>
4341:
4342: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4343:
4344: <p>If the next token is a U+000A LINE FEED (LF) character
4345: token, then ignore that token and move on to the next
4346: one. (Newlines at the start of <code><a href="semantics.html#the-pre-element">pre</a></code> blocks are
4347: ignored as an authoring convenience.)</p>
4348:
4349: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4350:
4351: </dd>
4352:
4353: <!-- as normal, but interacts with the form element pointer -->
4354: <dt>A start tag whose tag name is "form"</dt>
4355: <dd>
4356:
4357: <p>If the <a href="#form-element-pointer"><code title="form">form</code> element
4358: pointer</a> is not null, then this is a <a href="#parse-error">parse
4359: error</a>; ignore the token.</p>
4360:
4361: <p>Otherwise:</p>
4362:
4363: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4364: an element in scope">has a <code>p</code> element in
4365: scope</a>, then act as if an end tag with the tag name
4366: "p" had been seen.</p>
4367:
4368: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, and set the
4369: <a href="#form-element-pointer"><code title="form">form</code> element pointer</a> to
4370: point to the element created.</p>
4371:
4372: </dd>
4373:
4374: <!-- as normal, but imply </li> when there's another <li> open in weird cases -->
4375: <dt>A start tag whose tag name is "li"</dt>
4376: <dd>
4377:
4378: <p>Run the following algorithm:</p>
4379:
4380: <ol><li><p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p></li>
4381:
4382: <li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
4383: node</a> (the bottommost node of the stack).</p></li>
4384:
4385: <li><p>If <var title="">node</var> is an <code><a href="semantics.html#the-li-element">li</a></code> element,
4386: then act as if an end tag with the tag name "li" had
4387: been seen, then jump to the last step.</p></li>
4388:
4389: <li><p><i>Loop</i>: If <var title="">node</var> is not in the
4390: <a href="#formatting">formatting</a> category, and is not in the
4391: <a href="#phrasing">phrasing</a> category, and is not an
4392: <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>
4393: element, then jump to the last step.</p></li> <!-- an element
4394: <foo> is in this list if the following markup:
4395:
4396: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><body><ol><li><foo><li>
4397:
4398: ...results in the second <li> not being (in any way) a descendant
4399: of the first <li>, or if <foo> is a formatting element that gets
4400: reopened later. -->
4401:
4402: <li><p>Otherwise, set <var title="">node</var> to the previous
4403: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to
4404: the step labeled <i>loop</i>.</p></li>
4405:
4406: <li>
4407:
4408: <p>This is the last step.</p>
4409:
4410: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4411: an element in scope">has a <code>p</code> element in
4412: scope</a>, then act as if an end tag with the tag name
4413: "p" had been seen.</p>
4414:
4415: <p>Finally, <a href="#insert-an-html-element">insert an HTML element</a> for the
4416: token.</p>
4417:
4418: </li>
4419:
4420: </ol></dd>
4421:
4422: <!-- as normal, but imply </dt> or </dd> when there's another <dt> or <dd> open in weird cases -->
4423: <dt>A start tag whose tag name is one of: "dd", "dt"</dt>
4424: <dd>
4425:
4426: <p>Run the following algorithm:</p>
4427:
4428: <ol><li><p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p></li>
4429:
4430: <li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
4431: node</a> (the bottommost node of the stack).</p></li>
4432:
4433: <li><p><i>Loop</i>: If <var title="">node</var> is a
4434: <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
4435: tag with the same tag name as <var title="">node</var> had been
4436: seen, then jump to the last step.</p></li>
4437:
4438: <li><p>If <var title="">node</var> is not in the
4439: <a href="#formatting">formatting</a> category, and is not in the
4440: <a href="#phrasing">phrasing</a> category, and is not an
4441: <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>
4442: element, then jump to the last step.</p></li> <!-- an element
4443: <foo> is in this list if the following markup:
4444:
4445: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><body><dl><dt><foo><dt>
4446:
4447: ...results in the second <dt> not being (in any way) a descendant
4448: of the first <dt>, or if <foo> is a formatting element that gets
4449: reopened later. -->
4450:
4451: <li><p>Otherwise, set <var title="">node</var> to the previous
4452: entry in the <a href="#stack-of-open-elements">stack of open elements</a> and return to
4453: the step labeled <i>loop</i>.</p></li>
4454:
4455: <li>
4456:
4457: <p>This is the last step.</p>
4458:
4459: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4460: an element in scope">has a <code>p</code> element in
4461: scope</a>, then act as if an end tag with the tag name
4462: "p" had been seen.</p>
4463:
4464: <p>Finally, <a href="#insert-an-html-element">insert an HTML element</a> for the
4465: token.</p>
4466:
4467: </li>
4468:
4469: </ol></dd>
4470:
4471: <!-- same as normal, but effectively ends parsing -->
4472: <dt>A start tag whose tag name is "plaintext"</dt>
4473: <dd>
4474:
4475: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4476: an element in scope">has a <code>p</code> element in
4477: scope</a>, then act as if an end tag with the tag name
4478: "p" had been seen.</p>
4479:
4480: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4481:
4482: <p>Switch the <a href="#content-model-flag">content model flag</a> to the PLAINTEXT
4483: state.</p>
4484:
4485: <p class="note">Once a start tag with the tag name "plaintext"
4486: has been seen, that will be the last token ever seen other
4487: than character tokens (and the end-of-file token), because
4488: there is no way to switch the <a href="#content-model-flag">content model flag</a>
4489: out of the PLAINTEXT state.</p>
4490:
4491: </dd>
4492:
4493: <!-- end tags for non-phrasing flow content elements -->
4494:
4495: <!-- the normal ones -->
4496: <dt>An end tag whose tag name is one of: "address", "article",
1.86 mike 4497: "aside", "blockquote", "center", <!--v2DATAGRID-->"datagrid",
4498: "details", "dialog", "dir", "div", "dl", "fieldset", "figure",
4499: "footer", "header", "hgroup", "listing", "menu", "nav", "ol",
4500: "pre", "section", "ul"</dt>
1.1 mike 4501: <dd>
4502:
4503: <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>
4504: with the same tag name as that of the token, then this is a
4505: <a href="#parse-error">parse error</a>; ignore the token.</p>
4506:
4507: <p>Otherwise, run these steps:</p>
4508:
4509: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4510:
4511: <li><p>If the <a href="#current-node">current node</a> is not an element with
4512: the same tag name as that of the token, then this is a
4513: <a href="#parse-error">parse error</a>.</p></li>
4514:
4515: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4516: until an element with the same tag name as the token has been
4517: popped from the stack.</p></li>
4518:
4519: </ol></dd>
4520:
4521: <!-- removes the form element pointer instead of the matching node -->
4522: <dt>An end tag whose tag name is "form"</dt>
4523: <dd>
4524:
4525: <p>Let <var title="">node</var> be the element that the
4526: <a href="#form-element-pointer"><code title="">form</code> element pointer</a> is set
4527: to.</p>
4528:
4529: <p>Set the <a href="#form-element-pointer"><code title="">form</code> element pointer</a>
4530: to null.</p>
4531:
4532: <p>If <var title="">node</var> is null or the <a href="#stack-of-open-elements">stack of open
4533: elements</a> does not <a href="#has-an-element-in-scope" title="has an element in
4534: scope">have <var title="">node</var> in scope</a>, then this is
4535: a <a href="#parse-error">parse error</a>; ignore the token.</p>
4536:
4537: <p>Otherwise, run these steps:</p>
4538:
4539: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4540:
4541: <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
4542: error</a>.</p></li>
4543:
4544: <li><p>Remove <var title="">node</var> from the <a href="#stack-of-open-elements">stack of
4545: open elements</a>.</p></li>
4546:
4547: </ol></dd>
4548:
4549: <!-- as normal, except </p> implies <p> if there's no <p> in scope, and needs care as the elements have optional tags -->
4550: <dt>An end tag whose tag name is "p"</dt>
4551: <dd>
4552:
4553: <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>
4554: with the same tag name as that of the token, then this is a
4555: <a href="#parse-error">parse error</a>; act as if a start tag with the tag name
4556: "p" had been seen, then reprocess the current token.</p>
4557:
4558: <p>Otherwise, run these steps:</p>
4559:
4560: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>, except
4561: for elements with the same tag name as the token.</p></li>
4562:
4563: <li><p>If the <a href="#current-node">current node</a> is not an element with
4564: the same tag name as that of the token, then this is a
4565: <a href="#parse-error">parse error</a>.</p></li>
4566:
4567: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4568: until an element with the same tag name as the token has been
4569: popped from the stack.</p></li>
4570:
4571: </ol></dd>
4572:
4573: <!-- as normal, but needs care as the elements have optional tags -->
4574: <dt>An end tag whose tag name is one of: "dd", "dt", "li"</dt>
4575: <dd>
4576:
4577: <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>
4578: with the same tag name as that of the token, then this is a
4579: <a href="#parse-error">parse error</a>; ignore the token.</p>
4580:
4581: <p>Otherwise, run these steps:</p>
4582:
4583: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>, except
4584: for elements with the same tag name as the token.</p></li>
4585:
4586: <li><p>If the <a href="#current-node">current node</a> is not an element with
4587: the same tag name as that of the token, then this is a
4588: <a href="#parse-error">parse error</a>.</p></li>
4589:
4590: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4591: until an element with the same tag name as the token has been
4592: popped from the stack.</p></li>
4593:
4594: </ol></dd>
4595:
4596: <!-- as normal, except acts as a closer for any of the h1-h6 elements -->
4597: <dt>An end tag whose tag name is one of: "h1", "h2", "h3", "h4", "h5", "h6"</dt>
4598: <dd>
4599:
4600: <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>
4601: whose tag name is one of "h1", "h2", "h3", "h4", "h5", or "h6",
4602: then this is a <a href="#parse-error">parse error</a>; ignore the token.</p>
4603:
4604: <p>Otherwise, run these steps:</p>
4605:
4606: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4607:
4608: <li><p>If the <a href="#current-node">current node</a> is not an element with
4609: the same tag name as that of the token, then this is a
4610: <a href="#parse-error">parse error</a>.</p></li>
4611:
4612: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4613: until an element whose tag name is one of "h1", "h2", "h3", "h4",
4614: "h5", or "h6" has been popped from the stack.</p></li>
4615:
4616: </ol></dd>
4617:
4618: <dt>An end tag whose tag name is "sarcasm"</dt>
4619: <dd>
4620: <p>Take a deep breath, then act as described in the "any other end
4621: tag" entry below.</p>
4622: </dd>
4623:
4624: <!-- ADOPTION AGENCY ELEMENTS
4625: Mozilla-only: bdo blink del ins sub sup q
4626: Safari-only: code dfn kbd nobr samp var wbr
4627: Both: a b big em font i s small strike strong tt u -->
4628:
4629: <dt>A start tag whose tag name is "a"</dt>
4630: <dd>
4631:
4632: <p>If the <a href="#list-of-active-formatting-elements">list of active formatting elements</a>
4633: contains an element whose tag name is "a" between the end of
4634: the list and the last marker on the list (or the start of the
4635: list if there is no marker on the list), then this is a
4636: <a href="#parse-error">parse error</a>; act as if an end tag with the tag
4637: name "a" had been seen, then remove that element from the
4638: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> and the
4639: <a href="#stack-of-open-elements">stack of open elements</a> if the end tag didn't
4640: already remove it (it might not have if the element is not
4641: <a href="#has-an-element-in-table-scope" title="has an element in table scope">in table
4642: scope</a>).</p>
4643:
4644: <p class="example">In the non-conforming stream
4645: <code><a href="a">a<table><a href="b">b</table>x</code>,
4646: the first <code><a href="text-level-semantics.html#the-a-element">a</a></code> element would be closed upon seeing
4647: the second one, and the "x" character would be inside a link
4648: to "b", not to "a". This is despite the fact that the outer
4649: <code><a href="text-level-semantics.html#the-a-element">a</a></code> element is not in table scope (meaning that a
4650: regular <code></a></code> end tag at the start of the table
4651: wouldn't close the outer <code><a href="text-level-semantics.html#the-a-element">a</a></code> element).</p>
4652:
4653: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4654: any.</p>
4655:
4656: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Add that
4657: element to the <a href="#list-of-active-formatting-elements">list of active formatting
4658: elements</a>.</p>
4659:
4660: </dd>
4661:
4662: <dt>A start tag whose tag name is one of: "b", "big", "code", "em",
4663: "font", "i", "s", "small", "strike", "strong", "tt", "u"</dt>
4664: <dd>
4665:
4666: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4667: any.</p>
4668:
4669: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Add that
4670: element to the <a href="#list-of-active-formatting-elements">list of active formatting
4671: elements</a>.</p>
4672:
4673: </dd>
4674:
4675: <dt>A start tag whose tag name is "nobr"</dt>
4676: <dd>
4677:
4678: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4679: any.</p>
4680:
4681: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has an
4682: element in scope">has a <code>nobr</code> element in scope</a>,
4683: then this is a <a href="#parse-error">parse error</a>; act as if an end tag with
4684: the tag name "nobr" had been seen, then once again
4685: <a href="#reconstruct-the-active-formatting-elements">reconstruct the active formatting elements</a>, if
4686: any.</p>
4687:
4688: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Add that
4689: element to the <a href="#list-of-active-formatting-elements">list of active formatting
4690: elements</a>.</p>
4691:
4692: </dd>
4693:
4694: <dt id="adoptionAgency">An end tag whose tag name is one of: "a",
4695: "b", "big", "code", "em", "font", "i", "nobr", "s", "small",
4696: "strike", "strong", "tt", "u"</dt>
4697: <dd>
4698:
4699: <p>Follow these steps:</p>
4700:
4701: <ol><li>
4702:
4703: <p>Let the <var title="">formatting element</var> be the
4704: last element in the <a href="#list-of-active-formatting-elements">list of active formatting
4705: elements</a> that:</p>
4706:
4707: <ul><li>is between the end of the list and the last scope
4708: marker in the list, if any, or the start of the list
4709: otherwise, and</li>
4710:
4711: <li>has the same tag name as the token.</li>
4712:
4713: </ul><p>If there is no such node, or, if that node is also in the
4714: <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
4715: <a href="#parse-error">parse error</a>; ignore the token, and abort these
4716: steps.</p>
4717:
4718: <p>Otherwise, if there is such a node, but that node is not
4719: in the <a href="#stack-of-open-elements">stack of open elements</a>, then this is a
4720: <a href="#parse-error">parse error</a>; remove the element from the list,
4721: and abort these steps.</p>
4722:
4723: <p>Otherwise, there is a <var title="">formatting
4724: element</var> and that element is in <a href="#stack-of-open-elements" title="stack of
4725: open elements">the stack</a> and is <a href="#has-an-element-in-scope" title="has an
4726: element in scope">in scope</a>. If the element is not the
4727: <a href="#current-node">current node</a>, this is a <a href="#parse-error">parse
4728: error</a>. In any case, proceed with the algorithm as
4729: written in the following steps.</p>
4730:
4731: </li>
4732:
4733: <li><p>Let the <var title="">furthest block</var> be the
4734: topmost node in the <a href="#stack-of-open-elements">stack of open elements</a> that
4735: is lower in the stack than the <var title="">formatting
4736: element</var>, and is not an element in the
4737: <a href="#phrasing">phrasing</a> or <a href="#formatting">formatting</a>
4738: categories. There might not be one.</p></li>
4739:
4740: <li><p>If there is no <var title="">furthest block</var>,
4741: then the UA must skip the subsequent steps and instead just
4742: pop all the nodes from the bottom of the <a href="#stack-of-open-elements">stack of open
4743: elements</a>, from the <a href="#current-node">current node</a> up to and
4744: including the <var title="">formatting element</var>, and
4745: remove the <var title="">formatting element</var> from the
4746: <a href="#list-of-active-formatting-elements">list of active formatting elements</a>.</p></li>
4747:
4748: <li><p>Let the <var title="">common ancestor</var> be the element
4749: immediately above the <var title="">formatting element</var> in the
4750: <a href="#stack-of-open-elements">stack of open elements</a>.</p></li>
4751:
4752: <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
4753: formatting elements</a> relative to the elements on either
4754: side of it in the list.</p></li>
4755:
4756: <li>
4757:
4758: <p>Let <var title="">node</var> and <var title="">last node</var> be the
4759: <var title="">furthest block</var>. Follow these steps:</p>
4760:
4761: <ol><li>Let <var title="">node</var> be the element immediately
4762: above <var title="">node</var> in the <a href="#stack-of-open-elements">stack of open
4763: elements</a>.</li>
4764:
4765: <li>If <var title="">node</var> is not in the <a href="#list-of-active-formatting-elements">list of
4766: active formatting elements</a>, then remove <var title="">node</var> from the <a href="#stack-of-open-elements">stack of open
4767: elements</a> and then go back to step 1.</li>
4768:
4769: <li>Otherwise, if <var title="">node</var> is the <var title="">formatting element</var>, then go to the next step
4770: in the overall algorithm.</li>
4771:
4772: <li>Otherwise, if <var title="">last node</var> is the <var title="">furthest block</var>, then move the aforementioned
4773: bookmark to be immediately after the <var title="">node</var> in the <a href="#list-of-active-formatting-elements">list of active formatting
4774: elements</a>.</li>
4775:
4776: <li><a href="#create-an-element-for-the-token">Create an element for the token</a> for which the
4777: element <var title="">node</var> was created, replace the entry
4778: for <var title="">node</var> in the <a href="#list-of-active-formatting-elements">list of active
4779: formatting elements</a> with an entry for the new element,
4780: replace the entry for <var title="">node</var> in the
4781: <a href="#stack-of-open-elements">stack of open elements</a> with an entry for the new
4782: element, and let <var title="">node</var> be the new
4783: element.</li>
4784:
4785: <li>Insert <var title="">last node</var> into <var title="">node</var>, first removing it from its previous
4786: parent node if any.</li>
4787:
4788: <li>Let <var title="">last node</var> be <var title="">node</var>.</li>
4789:
4790: <li>Return to step 1 of this inner set of steps.</li>
4791:
4792: </ol></li>
4793:
4794: <li>
4795:
4796: <p>If the <var title="">common ancestor</var> node is a
4797: <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>,
4798: <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,
4799: <a href="#foster-parent">foster parent</a> whatever <var title="">last
4800: node</var> ended up being in the previous step, first removing
4801: it from its previous parent node if any.</p>
4802:
4803: <p>Otherwise, append whatever <var title="">last node</var>
4804: ended up being in the previous step to the <var title="">common
4805: ancestor</var> node, first removing it from its previous parent
4806: node if any.</p>
4807:
4808: </li>
4809:
4810: <li><p><a href="#create-an-element-for-the-token">Create an element for the token</a> for which the
4811: <var title="">formatting element</var> was created.</p></li>
4812:
4813: <li><p>Take all of the child nodes of the <var title="">furthest
4814: block</var> and append them to the element created in the last
4815: step.</p></li>
4816:
4817: <li><p>Append that new element to the <var title="">furthest
4818: block</var>.</p></li>
4819:
4820: <li><p>Remove the <var title="">formatting element</var> from the
4821: <a href="#list-of-active-formatting-elements">list of active formatting elements</a>, and insert the
4822: new element into the <a href="#list-of-active-formatting-elements">list of active formatting
4823: elements</a> at the position of the aforementioned
4824: bookmark.</p></li>
4825:
4826: <li><p>Remove the <var title="">formatting element</var> from the
4827: <a href="#stack-of-open-elements">stack of open elements</a>, and insert the new element
4828: into the <a href="#stack-of-open-elements">stack of open elements</a> immediately below
4829: the position of the <var title="">furthest block</var> in that
4830: stack.</p></li>
4831:
4832: <li><p>Jump back to step 1 in this series of steps.</p></li>
4833:
4834: </ol><!--XXX
4835: <div class="example">
4836: <p class="XXX">Need an example.</p>
4837: </div>
4838: --><p class="note">Because of the way this algorithm causes elements to
4839: change parents, it has been dubbed the "adoption agency algorithm"
4840: (in contrast with other possibly algorithms for dealing with
4841: misnested content, which included the "incest algorithm", the
4842: "secret affair algorithm", and the "Heisenberg algorithm").</p>
4843:
4844: </dd>
4845:
4846: <dt>A start tag whose tag name is "button"</dt>
4847: <dd>
4848:
4849: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4850: an element in scope">has a <code>button</code> element in
4851: scope</a>, then this is a <a href="#parse-error">parse error</a>;
4852: act as if an end tag with the tag name "button" had been seen,
4853: then reprocess the token.</p>
4854:
4855: <p>Otherwise:</p>
4856:
4857: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4858: any.</p>
4859:
4860: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4861:
4862: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
4863: formatting elements</a>.</p>
4864:
4865: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4866:
4867: </dd>
4868:
4869: <dt>A start tag token whose tag name is one of: "applet",
4870: "marquee", "object"</dt>
4871: <dd>
4872:
4873: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4874: any.</p>
4875:
4876: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4877:
4878: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
4879: formatting elements</a>.</p>
4880:
4881: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4882:
4883: </dd>
4884:
4885: <dt>An end tag token whose tag name is one of: "applet", "button",
4886: "marquee", "object"</dt>
4887: <dd>
4888:
4889: <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>
4890: with the same tag name as that of the token, then this is a
4891: <a href="#parse-error">parse error</a>; ignore the token.</p>
4892:
4893: <p>Otherwise, run these steps:</p>
4894:
4895: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
4896:
4897: <li><p>If the <a href="#current-node">current node</a> is not an element with
4898: the same tag name as that of the token, then this is a
4899: <a href="#parse-error">parse error</a>.</p></li>
4900:
4901: <li><p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
4902: until an element with the same tag name as the token has been
4903: popped from the stack.</p></li>
4904:
4905: <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
4906: last marker</a>.</li>
4907:
4908: </ol></dd>
4909:
4910: <dt>A start tag whose tag name is "table"</dt>
4911: <dd>
4912:
4913: <p>If the <code>Document</code> is <em>not</em> set to
4914: <a href="dom.html#quirks-mode">quirks mode</a>, and the <a href="#stack-of-open-elements">stack of open
4915: elements</a> <a href="#has-an-element-in-scope" title="has an element in scope">has a
4916: <code>p</code> element in scope</a>, then act as if an end tag
4917: with the tag name "p" had been seen.</p> <!-- i hate myself (this
4918: quirk was basically caused by acid2; if i'd realised we could
4919: change the specs when i wrote acid2, we could have avoided having
4920: any parsing-mode quirks) -Hixie -->
4921:
4922: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
4923:
4924: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4925:
4926: <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>
4927:
4928: </dd>
4929:
4930: <dt>A start tag whose tag name is one of: "area", "basefont",
4931: "bgsound", "br", "embed", "img", "input", "keygen", "spacer",
4932: "wbr"</dt>
4933: <dd>
4934:
4935: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
4936: any.</p>
4937:
4938: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
4939: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
4940: elements</a>.</p>
4941:
4942: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
4943: token's <i>self-closing flag</i></a>, if it is set.</p>
4944:
4945: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p> <!--
4946: shouldn't really do it for <area>, <basefont>, <bgsound>, and
4947: <spacer> -->
4948:
4949: </dd>
4950:
4951: <dt>A start tag whose tag name is one of: "param", "source"</dt>
4952: <dd>
4953:
4954: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
4955: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
4956: elements</a>.</p>
4957:
4958: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
4959: token's <i>self-closing flag</i></a>, if it is set.</p>
4960:
4961: </dd>
4962:
4963: <dt>A start tag whose tag name is "hr"</dt>
4964: <dd>
4965:
4966: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has
4967: an element in scope">has a <code>p</code> element in
4968: scope</a>, then act as if an end tag with the tag name
4969: "p" had been seen.</p>
4970:
4971: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
4972: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
4973: elements</a>.</p>
4974:
4975: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
4976: token's <i>self-closing flag</i></a>, if it is set.</p>
4977:
4978: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
4979:
4980: </dd>
4981:
4982: <dt>A start tag whose tag name is "image"</dt>
4983: <dd>
4984: <p><a href="#parse-error">Parse error</a>. Change the token's tag name
4985: to "img" and reprocess it. (Don't ask.)</p> <!-- As of
4986: 2005-12, studies showed that around 0.2% of pages used the
4987: <image> element. -->
4988: </dd>
4989:
4990: <dt id="isindex">A start tag whose tag name is "isindex"</dt>
4991: <dd>
4992:
4993: <p><a href="#parse-error">Parse error</a>.</p>
4994:
4995: <p>If the <a href="#form-element-pointer"><code title="">form</code> element
4996: pointer</a> is not null, then ignore the token.</p>
4997:
4998: <p>Otherwise:</p>
4999:
5000: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
5001: token's <i>self-closing flag</i></a>, if it is set.</p> <!--
5002: purely to reduce the number of errors (we don't care if they
5003: included the /, they're not supposed to be including the tag at
5004: all! -->
5005:
5006: <p>Act as if a start tag token with the tag name "form" had been seen.</p>
5007:
5008: <p>If the token has an attribute called "action", set the
5009: <code title="attr-form-action">action</code> attribute on the
5010: resulting <code><a href="forms.html#the-form-element">form</a></code> element to the value of the
5011: "action" attribute of the token.</p>
5012:
5013: <p>Act as if a start tag token with the tag name "hr" had been
5014: seen.</p>
5015:
5016: <p>Act as if a start tag token with the tag name "label" had been
5017: seen.</p>
5018:
5019: <p>Act as if a stream of character tokens had been seen (see below
5020: for what they should say).</p>
5021:
5022: <p>Act as if a start tag token with the tag name "input" had been
5023: seen, with all the attributes from the "isindex" token except
5024: "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
5025: <code><a href="forms.html#the-input-element">input</a></code> element to the value "<code title="">isindex</code>".</p>
5026:
5027: <p>Act as if a stream of character tokens had been seen (see
5028: below for what they should say).</p>
5029:
5030: <p>Act as if an end tag token with the tag name "label" had been
5031: seen.</p>
5032:
5033: <p>Act as if a start tag token with the tag name "hr" had been
5034: seen.</p>
5035:
5036: <p>Act as if an end tag token with the tag name "form" had been
5037: seen.</p>
5038:
5039: <p>If the token has an attribute with the name "prompt", then the
5040: first stream of characters must be the same string as given in
5041: that attribute, and the second stream of characters must be
5042: empty. Otherwise, the two streams of character tokens together
5043: should, together with the <code><a href="forms.html#the-input-element">input</a></code> element, express the
5044: equivalent of "This is a searchable index. Insert your search
5045: keywords here: (input field)" in the user's preferred
5046: language.</p>
5047:
5048: </dd>
5049:
5050: <dt>A start tag whose tag name is "textarea"</dt>
5051: <dd>
5052:
5053: <ol><li><p><a href="#insert-an-html-element">Insert an HTML element</a> for the
5054: token.</p></li>
5055:
5056: <li><p>If the next token is a U+000A LINE FEED (LF) character
5057: token, then ignore that token and move on to the next
5058: one. (Newlines at the start of <code><a href="forms.html#the-textarea-element">textarea</a></code> elements are
5059: ignored as an authoring convenience.)</p></li>
5060:
5061: <li><p>Switch the tokenizer's <a href="#content-model-flag">content model flag</a> to
5062: the RCDATA state.</p></li>
5063:
5064: <li><p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the
5065: current <a href="#insertion-mode">insertion mode</a>.</p>
5066:
5067: </li><li><p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not
5068: ok".</p></li>
5069:
1.91 mike 5070: <li><p>Switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incdata" title="insertion mode: in RAWTEXT/RCDATA">in
5071: RAWTEXT/RCDATA</a>".</p></li>
1.1 mike 5072:
5073: </ol></dd>
5074:
5075: <dt>A start tag whose tag name is "xmp"</dt>
5076: <dd>
5077:
5078: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5079: any.</p>
5080:
5081: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
5082:
1.91 mike 5083: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 5084:
5085: </dd>
5086:
5087: <dt>A start tag whose tag name is "iframe"</dt>
5088: <dd>
5089:
5090: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
5091:
1.91 mike 5092: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 5093:
5094: </dd>
5095:
5096: <dt>A start tag whose tag name is "noembed"</dt>
5097: <dt>A start tag whose tag name is "noscript", if the <a href="#scripting-flag">scripting flag</a> is enabled</dt>
5098: <dd>
5099:
1.91 mike 5100: <p>Follow the <a href="#generic-raw-text-element-parsing-algorithm">generic raw text element parsing algorithm</a>.</p>
1.1 mike 5101:
5102: </dd>
5103:
5104: <dt>A start tag whose tag name is "select"</dt>
5105: <dd>
5106:
5107: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5108: any.</p>
5109:
5110: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5111:
5112: <p>Set the <a href="#frameset-ok-flag">frameset-ok flag</a> to "not ok".</p>
5113:
5114: <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>",
5115: "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
5116: body</a>", "<a href="#parsing-main-intr" title="insertion mode: in row">in
5117: row</a>", or "<a href="#parsing-main-intd" title="insertion mode: in cell">in
5118: cell</a>", then switch the <a href="#insertion-mode">insertion mode</a> to
5119: "<a href="#parsing-main-inselectintable" title="insertion mode: in select in table">in select in
5120: table</a>". Otherwise, switch the <a href="#insertion-mode">insertion mode</a>
5121: to "<a href="#parsing-main-inselect" title="insertion mode: in select">in select</a>".</p>
5122:
5123: </dd>
5124:
5125: <dt>A start tag whose tag name is one of: "optgroup", "option"</dt>
5126: <dd>
5127:
5128: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has an
5129: element in scope">has an <code>option</code> element in
5130: scope</a>, then act as if an end tag with the tag name "option"
5131: had been seen.</p>
5132:
5133: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5134: any.</p>
5135:
5136: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5137:
5138: </dd>
5139:
5140: <dt>A start tag whose tag name is one of: "rp", "rt"</dt>
5141: <dd>
5142:
5143: <!-- the parsing rules for ruby really don't match IE much at all,
5144: but in practice the markup used is very simple and so strict
5145: compatibility with IE isn't required. For example, as defined
5146: here we get very, very different behaviour than IE for
5147: pathological cases like:
5148:
5149: <ruby><ol><li><p>a<rt>b
5150: <ruby>a<rt>b<p>c
5151:
5152: But in practice most ruby markup falls into these cases:
5153:
5154: <ruby>a<rt>b</ruby>
5155: <ruby>a<rp>b<rt>c<rp>d</ruby>
5156: <ruby>a<rt>b</rt></ruby>
5157: <ruby>a<rp>b</rp><rt>c</rt><rp>d</rp></ruby>
5158:
5159: -->
5160:
5161: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-scope" title="has an
5162: element in scope">has a <code>ruby</code> element in scope</a>,
5163: then <a href="#generate-implied-end-tags">generate implied end tags</a>. If the <a href="#current-node">current
5164: node</a> is not then a <code><a href="text-level-semantics.html#the-ruby-element">ruby</a></code> element, this is a
5165: <a href="#parse-error">parse error</a>; pop all the nodes from the <a href="#current-node">current
5166: node</a> up to the node immediately before the bottommost
5167: <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
5168: elements</a>.</p>
5169:
5170: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5171:
5172: </dd>
5173:
5174: <dt>An end tag whose tag name is "br"</dt>
5175: <dd>
5176: <p><a href="#parse-error">Parse error</a>. Act as if a start tag token with
5177: the tag name "br" had been seen. Ignore the end tag token.</p>
5178: </dd>
5179:
5180: <dt>A start tag whose tag name is "math"</dt>
5181: <dd>
5182:
5183: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5184: any.</p>
5185:
5186: <p><a href="#adjust-mathml-attributes">Adjust MathML attributes</a> for the token. (This
5187: fixes the case of MathML attributes that are not all
5188: lowercase.)</p>
5189:
5190: <p><a href="#adjust-foreign-attributes">Adjust foreign attributes</a> for the token. (This
5191: fixes the use of namespaced attributes, in particular XLink.)</p>
5192:
5193: <p><a href="#insert-a-foreign-element">Insert a foreign element</a> for the token, in the
5194: <a href="#mathml-namespace">MathML namespace</a>.</p>
5195:
5196: <!-- If we ever change the frameset-ok flag to an insertion mode,
5197: the following change would be implied, except we'd have to do it
5198: even in the face of a self-closed tag:
5199: <p>Set the <span>frameset-ok flag</span> to "not ok".</p>
5200: -->
5201:
5202: <p>If the token has its <i>self-closing flag</i> set, pop the
5203: <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5204: elements</a> and <a href="#acknowledge-self-closing-flag" title="acknowledge self-closing
5205: flag">acknowledge the token's <i>self-closing flag</i></a>.</p>
5206:
5207: <p>Otherwise, if the <a href="#insertion-mode">insertion mode</a> is not already
5208: "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in foreign
5209: content</a>", let the <a href="#secondary-insertion-mode">secondary insertion mode</a> be
5210: the current <a href="#insertion-mode">insertion mode</a>, and then switch the
5211: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inforeign" title="insertion mode: in
5212: foreign content">in foreign content</a>".</p>
5213:
5214: </dd>
5215:
5216: <dt>A start tag whose tag name is "svg"</dt>
5217: <dd>
5218:
5219: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5220: any.</p>
5221:
5222: <p><a href="#adjust-svg-attributes">Adjust SVG attributes</a> for the token. (This fixes
5223: the case of SVG attributes that are not all lowercase.)</p>
5224:
5225: <p><a href="#adjust-foreign-attributes">Adjust foreign attributes</a> for the token. (This
5226: fixes the use of namespaced attributes, in particular XLink in
5227: SVG.)</p>
5228:
5229: <p><a href="#insert-a-foreign-element">Insert a foreign element</a> for the token, in the
5230: <a href="#svg-namespace">SVG namespace</a>.</p>
5231:
5232: <!-- If we ever change the frameset-ok flag to an insertion mode,
5233: the following change would be implied, except we'd have to do it
5234: even in the face of a self-closed tag:
5235: <p>Set the <span>frameset-ok flag</span> to "not ok".</p>
5236: -->
5237:
5238: <p>If the token has its <i>self-closing flag</i> set, pop the
5239: <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5240: elements</a> and <a href="#acknowledge-self-closing-flag" title="acknowledge self-closing
5241: flag">acknowledge the token's <i>self-closing flag</i></a>.</p>
5242:
5243: <p>Otherwise, if the <a href="#insertion-mode">insertion mode</a> is not already
5244: "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in foreign
5245: content</a>", let the <a href="#secondary-insertion-mode">secondary insertion mode</a> be
5246: the current <a href="#insertion-mode">insertion mode</a>, and then switch the
5247: <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-inforeign" title="insertion mode: in
5248: foreign content">in foreign content</a>".</p>
5249:
5250: </dd>
5251:
5252: <dt>A start <!--or end--> tag whose tag name is one of: "caption",
5253: "col", "colgroup", "frame", "head", "tbody", "td", "tfoot", "th",
5254: "thead", "tr"</dt>
5255: <!--<dt>An end tag whose tag name is one of: "area", "base",
5256: "basefont", "bgsound", "command", "embed", "hr", "iframe", "image",
5257: "img", "input", "isindex", "keygen", "link", "meta", "noembed",
5258: "noframes", "param", "script", "select", "source", "spacer",
5259: "style", "table", "textarea", "title", "wbr"</dt>-->
5260: <!--<dt>An end tag whose tag name is "noscript", if the
5261: <span>scripting flag</span> is enabled</dt>-->
5262: <dd>
5263: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5264: <!-- end tags are commented out because since they can never end
5265: up on the stack anyway, the default end tag clause will
5266: automatically handle them. we don't want to have text in the spec
5267: that is just an optimisation, as that detracts from the spec
5268: itself -->
5269: </dd>
5270:
5271: <dt>Any other start tag</dt>
5272: <dd>
5273:
5274: <p><a href="#reconstruct-the-active-formatting-elements">Reconstruct the active formatting elements</a>, if
5275: any.</p>
5276:
5277: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5278:
5279: <p class="note">This element will be a <a href="#phrasing">phrasing</a>
5280: element.</p>
5281:
5282: </dd>
5283:
5284: <dt>Any other end tag</dt>
5285: <dd>
5286:
5287: <p>Run the following steps:</p>
5288:
5289: <ol><li><p>Initialize <var title="">node</var> to be the <a href="#current-node">current
5290: node</a> (the bottommost node of the stack).</p></li>
5291:
5292: <li><p>If <var title="">node</var> has the same tag name as
5293: the end tag token, then:</p>
5294:
5295: <ol><li><p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p></li>
5296:
5297: <li><p>If the tag name of the end tag token does not match
5298: the tag name of the <a href="#current-node">current node</a>, this is a
5299: <a href="#parse-error">parse error</a>.</p></li>
5300:
5301: <li><p>Pop all the nodes from the <a href="#current-node">current node</a> up
5302: to <var title="">node</var>, including <var title="">node</var>, then stop these steps.</p></li>
5303:
5304: </ol></li>
5305:
5306: <li><p>Otherwise, if <var title="">node</var> is in neither the
5307: <a href="#formatting">formatting</a> category nor the <a href="#phrasing">phrasing</a>
5308: category, then this is a <a href="#parse-error">parse error</a>; ignore the
5309: token, and abort these steps.</p></li>
5310:
5311: <li><p>Set <var title="">node</var> to the previous entry in the
5312: <a href="#stack-of-open-elements">stack of open elements</a>.</p></li>
5313:
5314: <li><p>Return to step 2.</p></li>
5315:
5316: </ol></dd>
5317:
1.91 mike 5318: </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 5319:
5320: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-incdata" title="insertion
1.91 mike 5321: mode: in RAWTEXT/RCDATA">in RAWTEXT/RCDATA</a>", tokens must be
1.1 mike 5322: handled as follows:</p>
5323:
5324: <dl class="switch"><dt>A character token</dt>
5325: <dd>
5326:
5327: <p><a href="#insert-a-character" title="insert a character">Insert the token's
5328: character</a> into the <a href="#current-node">current node</a>.</p>
5329:
5330: </dd>
5331:
5332: <dt>An end-of-file token</dt>
5333: <dd>
5334:
5335: <!-- can't be the fragment case -->
5336: <p><a href="#parse-error">Parse error</a>.</p>
5337:
5338: <p>If the <a href="#current-node">current node</a> is a <code><a href="semantics.html#script">script</a></code>
5339: element, mark the <code><a href="semantics.html#script">script</a></code> element as <a href="semantics.html#already-executed">"already
5340: executed"</a>.</p>
5341:
5342: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5343: elements</a>.</p>
5344:
5345: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5346: insertion mode</a> and reprocess the current token.</p>
5347:
5348: </dd>
5349:
5350: <dt>An end tag whose tag name is "script"</dt>
5351: <dd>
5352:
5353: <p>Let <var title="">script</var> be the <a href="#current-node">current node</a>
5354: (which will be a <code><a href="semantics.html#script">script</a></code> element).</p>
5355:
5356: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5357: elements</a>.</p>
5358:
5359: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5360: insertion mode</a>.</p>
5361:
5362: <p>Let the <var title="">old insertion point</var> have the
5363: same value as the current <a href="#insertion-point">insertion point</a>. Let
5364: the <a href="#insertion-point">insertion point</a> be just before the <a href="#next-input-character">next
5365: input character</a>.</p>
5366:
5367: <p>Increment the parser's <a href="#script-nesting-level">script nesting level</a> by
5368: one.</p>
5369:
5370: <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 5371: which might cause <a href="embedded-content-0.html#dom-document-write" title="dom-document-write">new characters
1.1 mike 5372: to be inserted into the tokenizer</a>, and might cause the
5373: tokenizer to output more tokens, resulting in a <a href="#nestedParsing">reentrant invocation of the parser</a>.</p>
5374:
5375: <p>Decrement the parser's <a href="#script-nesting-level">script nesting level</a> by
5376: one. If the parser's <a href="#script-nesting-level">script nesting level</a> is zero,
5377: then set the <a href="#parser-pause-flag">parser pause flag</a> to false.</p>
5378:
5379: <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
5380: <a href="#insertion-point">insertion point</a> to its previous value. This value
5381: might be the "undefined" value.)</p>
5382:
5383: <p id="scriptTagParserResumes">At this stage, if there is a
5384: <a href="semantics.html#pending-external-script">pending external script</a>, then:</p>
5385:
5386: <dl class="switch"><dt>If the <a href="#script-nesting-level">script nesting level</a> is not zero:</dt>
5387:
5388: <dd>
5389:
5390: <p>Set the <a href="#parser-pause-flag">parser pause flag</a> to true, and abort the
5391: processing of any nested invocations of the tokenizer, yielding
5392: control back to the caller. (Tokenization will resume when the
5393: caller returns to the "outer" tree construction stage.)</p>
5394:
5395: <p class="note">The tree construction stage of this particular
5396: parser is <a href="#nestedParsing">being called reentrantly</a>,
1.159 mike 5397: 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 5398:
5399: </dd>
5400:
5401:
5402: <dt>Otherwise:</dt>
5403:
5404: <dd>
5405:
5406: <p>Follow these steps:</p>
5407:
5408: <ol><li><p>Let <var title="">the script</var> be the <a href="semantics.html#pending-external-script">pending
5409: external script</a>. There is no longer a <a href="semantics.html#pending-external-script">pending
5410: external script</a>.</p></li>
5411:
5412: <li><p><a href="browsers.html#pause">Pause</a> until the script has <a href="semantics.html#completed-loading">completed
5413: loading</a>.</p></li>
5414:
5415: <li><p>Let the <a href="#insertion-point">insertion point</a> be just before the
5416: <a href="#next-input-character">next input character</a>.</p></li>
5417:
5418: <li><p>Increment the parser's <a href="#script-nesting-level">script nesting level</a>
5419: by one (it should be zero before this step, so this sets it to
5420: one).</p></li>
5421:
5422: <li><p><a href="semantics.html#executing-a-script-block" title="executing a script block">Execute the
5423: script</a>.</p></li>
5424:
5425: <li><p>Decrement the parser's <a href="#script-nesting-level">script nesting level</a>
5426: by one. If the parser's <a href="#script-nesting-level">script nesting level</a> is
5427: zero (which it always should be at this point), then set the
5428: <a href="#parser-pause-flag">parser pause flag</a> to false.</p>
5429:
5430: </li><li><p>Let the <a href="#insertion-point">insertion point</a> be undefined
5431: again.</p></li>
5432:
5433: <li><p>If there is once again a <a href="semantics.html#pending-external-script">pending external
5434: script</a>, then repeat these steps from step 1.</p></li>
5435:
5436: </ol></dd>
5437:
5438: </dl></dd>
5439:
5440: <dt>Any other end tag</dt>
5441: <dd>
5442:
5443: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5444: elements</a>.</p>
5445:
5446: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5447: insertion mode</a>.</p>
5448:
5449: </dd>
5450:
5451: </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>
5452:
5453: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intable" title="insertion
5454: mode: in table">in table</a>", tokens must be handled as follows:</p>
5455:
5456: <dl class="switch"><dt>A character token</dt>
5457: <dd>
5458:
5459: <p>Let the <dfn id="pending-table-character-tokens"><var>pending table character tokens</var></dfn>
5460: be an empty list of tokens.</p>
5461:
5462: <p>Let the <a href="#original-insertion-mode">original insertion mode</a> be the current
5463: <a href="#insertion-mode">insertion mode</a>.</p>
5464:
5465: <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
5466: reprocess the token.</p>
5467:
5468: </dd>
5469:
5470: <dt>A comment token</dt>
5471: <dd>
5472: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
5473: node</a> with the <code title="">data</code> attribute set to
5474: the data given in the comment token.</p>
5475: </dd>
5476:
5477: <dt>A DOCTYPE token</dt>
5478: <dd>
5479: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5480: </dd>
5481:
5482: <dt>A start tag whose tag name is "caption"</dt>
5483: <dd>
5484:
5485: <p><a href="#clear-the-stack-back-to-a-table-context">Clear the stack back to a table context</a>. (See
5486: below.)</p>
5487:
5488: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
5489: formatting elements</a>.</p>
5490:
5491: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then
5492: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incaption" title="insertion mode: in caption">in caption</a>".</p>
5493:
5494: </dd>
5495:
5496: <dt>A start tag whose tag name is "colgroup"</dt>
5497: <dd>
5498:
5499: <p><a href="#clear-the-stack-back-to-a-table-context">Clear the stack back to a table context</a>. (See
5500: below.)</p>
5501:
5502: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then
5503: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-incolgroup" title="insertion mode: in column group">in column
5504: group</a>".</p>
5505:
5506: </dd>
5507:
5508: <dt>A start tag whose tag name is "col"</dt>
5509: <dd>
5510: <p>Act as if a start tag token with the tag name "colgroup"
5511: had been seen, then reprocess the current token.</p>
5512: </dd>
5513:
5514: <dt>A start tag whose tag name is one of: "tbody", "tfoot", "thead"</dt>
5515: <dd>
5516:
5517: <p><a href="#clear-the-stack-back-to-a-table-context">Clear the stack back to a table context</a>. (See
5518: below.)</p>
5519:
5520: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then
5521: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
5522: body</a>".</p>
5523:
5524: </dd>
5525:
5526: <dt>A start tag whose tag name is one of: "td", "th", "tr"</dt>
5527: <dd>
5528: <p>Act as if a start tag token with the tag name "tbody" had
5529: been seen, then reprocess the current token.</p>
5530: </dd>
5531:
5532: <dt>A start tag whose tag name is "table"</dt>
5533: <dd>
5534:
5535: <p><a href="#parse-error">Parse error</a>. Act as if an end tag token with
5536: the tag name "table" had been seen, then, if that token wasn't
5537: ignored, reprocess the current token.</p>
5538:
5539: <p class="note">The fake end tag token here can only be
5540: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5541:
5542: </dd>
5543:
5544: <dt>An end tag whose tag name is "table"</dt>
5545: <dd>
5546:
5547: <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
5548: scope</a> with the same tag name as the token, this is a
5549: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
5550: case</a>)</p>
5551:
5552: <p>Otherwise:</p>
5553:
5554: <p>Pop elements from this stack until a <code><a href="tabular-data.html#the-table-element">table</a></code>
5555: element has been popped from the stack.</p>
5556:
5557: <p><a href="#reset-the-insertion-mode-appropriately">Reset the insertion mode appropriately</a>.</p>
5558:
5559: </dd>
5560:
5561: <dt>An end tag whose tag name is one of: "body", "caption",
5562: "col", "colgroup", "html", "tbody", "td", "tfoot", "th",
5563: "thead", "tr"</dt>
5564: <dd>
5565: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5566: </dd>
5567:
5568: <dt>A start tag whose tag name is one of: "style", "script"</dt>
5569: <dd>
5570:
5571: <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
5572: mode</a>.</p>
5573:
5574: </dd>
5575:
5576: <dt>A start tag whose tag name is "input"</dt>
5577: <dd>
5578:
5579: <p>If the token does not have an attribute with the name "type",
5580: or if it does, but that attribute's value is not an <a href="infrastructure.html#ascii-case-insensitive">ASCII
5581: case-insensitive</a> match for the string "<code title="">hidden</code>", then: act as described in the "anything
5582: else" entry below.</p>
5583:
5584: <p>Otherwise:</p>
5585:
5586: <p><a href="#parse-error">Parse error</a>.</p>
5587:
5588: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
5589:
5590: <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
5591: open elements</a>.</p>
5592:
5593: </dd>
5594:
5595: <dt>An end-of-file token</dt>
5596: <dd>
5597:
5598: <p>If the <a href="#current-node">current node</a> is not the root
1.159 mike 5599: <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 5600: error</a>.</p>
5601:
5602: <p class="note">It can only be the <a href="#current-node">current node</a> in
5603: the <a href="#fragment-case">fragment case</a>.</p>
5604:
5605: <p><a href="#stop-parsing">Stop parsing</a>.</p>
5606:
5607: </dd>
5608:
5609: <dt>Anything else</dt>
5610: <dd>
5611:
5612: <p><a href="#parse-error">Parse error</a>. Process the token <a href="#using-the-rules-for">using the
5613: rules for</a> the "<a href="#parsing-main-inbody" title="insertion mode: in body">in
5614: body</a>" <a href="#insertion-mode">insertion mode</a>, except that if the
5615: <a href="#current-node">current node</a> is a <code><a href="tabular-data.html#the-table-element">table</a></code>,
5616: <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
5617: <code><a href="tabular-data.html#the-tr-element">tr</a></code> element, then, whenever a node would be inserted
5618: into the <a href="#current-node">current node</a>, it must instead be <a href="#foster-parent" title="foster parent">foster parented</a>.</p>
5619:
5620: </dd>
5621:
5622: </dl><p>When the steps above require the UA to <dfn id="clear-the-stack-back-to-a-table-context">clear the stack
5623: back to a table context</dfn>, it means that the UA must, while
5624: 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 5625: element or an <code><a href="semantics.html#the-html-element-0">html</a></code> element, pop elements from the
1.1 mike 5626: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
5627:
5628: <p class="note">The <a href="#current-node">current node</a> being an
1.159 mike 5629: <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 5630: case</a>.</p>
5631:
5632:
5633:
5634: <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>
5635:
5636: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intabletext" title="insertion
5637: mode: in table text">in table text</a>", tokens must be handled
5638: as follows:</p>
5639:
5640: <dl class="switch"><dt>A character token</dt>
5641: <dd>
5642:
5643: <p>Append the character token to the <var><a href="#pending-table-character-tokens">pending table character
5644: tokens</a></var> list.</p>
5645:
5646: </dd>
5647:
5648:
5649: <dt>Anything else</dt>
5650: <dd>
5651:
5652: <p>If any of the tokens in the <var><a href="#pending-table-character-tokens">pending table character
5653: tokens</a></var> list are character tokens that are not one of U+0009
5654: CHARACTER TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED
5655: (FF), <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE, then
5656: reprocess those character tokens using the rules given in the
5657: "anything else" entry in the <a href="#parsing-main-intable" title="insertion mode: in
5658: table">in table</a>" insertion mode.</p>
5659:
5660: <p>Otherwise, <a href="#insert-a-character" title="insert a character">insert the
5661: characters</a> given by the <var><a href="#pending-table-character-tokens">pending table character
5662: tokens</a></var> list into the <a href="#current-node">current node</a>.</p>
5663:
5664: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#original-insertion-mode">original
5665: insertion mode</a> and reprocess the token.</p>
5666:
5667: </dd>
5668:
5669: </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>
5670:
5671: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-incaption" title="insertion
5672: mode: in caption">in caption</a>", tokens must be handled as follows:</p>
5673:
5674: <dl class="switch"><dt>An end tag whose tag name is "caption"</dt>
5675: <dd>
5676:
5677: <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
5678: scope</a> with the same tag name as the token, this is a
5679: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
5680: case</a>)</p>
5681:
5682: <p>Otherwise:</p>
5683:
5684: <p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p>
5685:
5686: <p>Now, if the <a href="#current-node">current node</a> is not a
5687: <code><a href="tabular-data.html#the-caption-element">caption</a></code> element, then this is a <a href="#parse-error">parse
5688: error</a>.</p>
5689:
5690: <p>Pop elements from this stack until a <code><a href="tabular-data.html#the-caption-element">caption</a></code>
5691: element has been popped from the stack.</p>
5692:
5693: <p><a href="#clear-the-list-of-active-formatting-elements-up-to-the-last-marker">Clear the list of active formatting elements up to
5694: the last marker</a>.</p>
5695:
5696: <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>
5697:
5698: </dd>
5699:
5700: <dt>A start tag whose tag name is one of: "caption", "col",
5701: "colgroup", "tbody", "td", "tfoot", "th", "thead", "tr"</dt>
5702: <dt>An end tag whose tag name is "table"</dt>
5703: <dd>
5704:
5705: <p><a href="#parse-error">Parse error</a>. Act as if an end tag with the tag
5706: name "caption" had been seen, then, if that token wasn't
5707: ignored, reprocess the current token.</p>
5708:
5709: <p class="note">The fake end tag token here can only be
5710: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5711:
5712: </dd>
5713:
5714: <dt>An end tag whose tag name is one of: "body", "col",
5715: "colgroup", "html", "tbody", "td", "tfoot", "th", "thead",
5716: "tr"</dt>
5717: <dd>
5718: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5719: </dd>
5720:
5721: <dt>Anything else</dt>
5722: <dd>
5723: <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
5724: mode</a>.</p>
5725: </dd>
5726:
5727: </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>
5728:
5729: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-incolgroup" title="insertion
5730: mode: in column group">in column group</a>", tokens must be handled as follows:</p>
5731:
5732: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
5733: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
5734: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
5735: <dd>
5736: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
5737: the <a href="#current-node">current node</a>.</p>
5738: </dd>
5739:
5740: <dt>A comment token</dt>
5741: <dd>
5742: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
5743: node</a> with the <code title="">data</code> attribute set to
5744: the data given in the comment token.</p>
5745: </dd>
5746:
5747: <dt>A DOCTYPE token</dt>
5748: <dd>
5749: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5750: </dd>
5751:
5752: <dt>A start tag whose tag name is "html"</dt>
5753: <dd>
5754: <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
5755: mode</a>.</p>
5756: </dd>
5757:
5758: <dt>A start tag whose tag name is "col"</dt>
5759: <dd>
5760:
5761: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token. Immediately
5762: pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
5763: elements</a>.</p>
5764:
5765: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
5766: token's <i>self-closing flag</i></a>, if it is set.</p>
5767:
5768: </dd>
5769:
5770: <dt>An end tag whose tag name is "colgroup"</dt>
5771: <dd>
5772:
5773: <p>If the <a href="#current-node">current node</a> is the root
1.159 mike 5774: <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 5775: error</a>; ignore the token. (<a href="#fragment-case">fragment
5776: case</a>)</p>
5777:
5778: <p>Otherwise, pop the <a href="#current-node">current node</a> (which will be
5779: 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
5780: elements</a>. Switch the <a href="#insertion-mode">insertion mode</a> to
5781: "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>".</p>
5782:
5783: </dd>
5784:
5785: <dt>An end tag whose tag name is "col"</dt>
5786: <dd>
5787: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5788: </dd>
5789:
5790: <dt>An end-of-file token</dt>
5791: <dd>
5792:
1.159 mike 5793: <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 5794: element, then <a href="#stop-parsing">stop parsing</a>. (<a href="#fragment-case">fragment
5795: case</a>)</p>
5796:
5797: <p>Otherwise, act as described in the "anything else" entry
5798: below.</p>
5799:
5800: </dd>
5801:
5802: <dt>Anything else</dt>
5803: <dd>
5804:
5805: <p>Act as if an end tag with the tag name "colgroup" had been
5806: seen, and then, if that token wasn't ignored, reprocess the
5807: current token.</p>
5808:
5809: <p class="note">The fake end tag token here can only be
5810: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5811:
5812: </dd>
5813:
5814: </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>
5815:
5816: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intbody" title="insertion
5817: mode: in table body">in table body</a>", tokens must be handled as follows:</p>
5818:
5819: <dl class="switch"><dt>A start tag whose tag name is "tr"</dt>
5820: <dd>
5821:
5822: <p><a href="#clear-the-stack-back-to-a-table-body-context">Clear the stack back to a table body
5823: context</a>. (See below.)</p>
5824:
5825: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then switch
5826: the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intr" title="insertion mode:
5827: in row">in row</a>".</p>
5828:
5829: </dd>
5830:
5831: <dt>A start tag whose tag name is one of: "th", "td"</dt>
5832: <dd>
5833: <p><a href="#parse-error">Parse error</a>. Act as if a start tag with
5834: the tag name "tr" had been seen, then reprocess the current
5835: token.</p>
5836: </dd>
5837:
5838: <dt>An end tag whose tag name is one of: "tbody", "tfoot",
5839: "thead"</dt>
5840: <dd>
5841:
5842: <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
5843: scope</a> with the same tag name as the token, this is a
5844: <a href="#parse-error">parse error</a>. Ignore the token.</p>
5845:
5846: <p>Otherwise:</p>
5847:
5848: <p><a href="#clear-the-stack-back-to-a-table-body-context">Clear the stack back to a table body
5849: context</a>. (See below.)</p>
5850:
5851: <p>Pop the <a href="#current-node">current node</a> from the <a href="#stack-of-open-elements">stack of
5852: open elements</a>. Switch the <a href="#insertion-mode">insertion mode</a>
5853: to "<a href="#parsing-main-intable" title="insertion mode: in table">in table</a>".</p>
5854:
5855: </dd>
5856:
5857: <dt>A start tag whose tag name is one of: "caption", "col",
5858: "colgroup", "tbody", "tfoot", "thead"</dt>
5859: <dt>An end tag whose tag name is "table"</dt>
5860: <dd>
5861:
5862: <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
5863: <code>tbody</code>, <code>thead</code>, or <code>tfoot</code>
5864: element in table scope</a>, this is a <a href="#parse-error">parse
5865: error</a>. Ignore the token. (<a href="#fragment-case">fragment
5866: case</a>)</p>
5867:
5868: <p>Otherwise:</p>
5869:
5870: <p><a href="#clear-the-stack-back-to-a-table-body-context">Clear the stack back to a table body
5871: context</a>. (See below.)</p>
5872:
5873: <p>Act as if an end tag with the same tag name as the
5874: <a href="#current-node">current node</a> ("tbody", "tfoot", or "thead") had
5875: been seen, then reprocess the current token.</p>
5876:
5877: </dd>
5878:
5879: <dt>An end tag whose tag name is one of: "body", "caption",
5880: "col", "colgroup", "html", "td", "th", "tr"</dt>
5881: <dd>
5882: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5883: </dd>
5884:
5885: <dt>Anything else</dt>
5886: <dd>
5887: <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
5888: mode</a>.</p>
5889: </dd>
5890:
5891: </dl><p>When the steps above require the UA to <dfn id="clear-the-stack-back-to-a-table-body-context">clear the stack
5892: back to a table body context</dfn>, it means that the UA must,
5893: 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 5894: <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 5895: element, pop elements from the <a href="#stack-of-open-elements">stack of open
5896: elements</a>.</p>
5897:
5898: <p class="note">The <a href="#current-node">current node</a> being an
1.159 mike 5899: <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 5900: case</a>.</p>
5901:
5902:
5903: <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>
5904:
5905: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intr" title="insertion
5906: mode: in row">in row</a>", tokens must be handled as follows:</p>
5907:
5908: <dl class="switch"><dt>A start tag whose tag name is one of: "th", "td"</dt>
5909: <dd>
5910:
5911: <p><a href="#clear-the-stack-back-to-a-table-row-context">Clear the stack back to a table row
5912: context</a>. (See below.)</p>
5913:
5914: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token, then switch
5915: the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-intd" title="insertion mode:
5916: in cell">in cell</a>".</p>
5917:
5918: <p>Insert a marker at the end of the <a href="#list-of-active-formatting-elements">list of active
5919: formatting elements</a>.</p>
5920:
5921: </dd>
5922:
5923: <dt>An end tag whose tag name is "tr"</dt>
5924: <dd>
5925:
5926: <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
5927: scope</a> with the same tag name as the token, this is a
5928: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
5929: case</a>)</p>
5930:
5931: <p>Otherwise:</p>
5932:
5933: <p><a href="#clear-the-stack-back-to-a-table-row-context">Clear the stack back to a table row
5934: context</a>. (See below.)</p>
5935:
5936: <p>Pop the <a href="#current-node">current node</a> (which will be a
5937: <code><a href="tabular-data.html#the-tr-element">tr</a></code> element) from the <a href="#stack-of-open-elements">stack of open
5938: elements</a>. Switch the <a href="#insertion-mode">insertion mode</a> to
5939: "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
5940: body</a>".</p>
5941:
5942: </dd>
5943:
5944: <dt>A start tag whose tag name is one of: "caption", "col",
5945: "colgroup", "tbody", "tfoot", "thead", "tr"</dt>
5946: <dt>An end tag whose tag name is "table"</dt>
5947: <dd>
5948:
5949: <p>Act as if an end tag with the tag name "tr" had been seen,
5950: then, if that token wasn't ignored, reprocess the current
5951: token.</p>
5952:
5953: <p class="note">The fake end tag token here can only be
5954: ignored in the <a href="#fragment-case">fragment case</a>.</p>
5955:
5956: </dd>
5957:
5958: <dt>An end tag whose tag name is one of: "tbody", "tfoot",
5959: "thead"</dt>
5960: <dd>
5961:
5962: <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
5963: scope</a> with the same tag name as the token, this is a
5964: <a href="#parse-error">parse error</a>. Ignore the token.</p>
5965:
5966: <p>Otherwise, act as if an end tag with the tag name "tr" had
5967: been seen, then reprocess the current token.</p>
5968:
5969: </dd>
5970:
5971: <dt>An end tag whose tag name is one of: "body", "caption",
5972: "col", "colgroup", "html", "td", "th"</dt>
5973: <dd>
5974: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
5975: </dd>
5976:
5977: <dt>Anything else</dt>
5978: <dd>
5979: <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
5980: mode</a>.</p>
5981: </dd>
5982:
5983: </dl><p>When the steps above require the UA to <dfn id="clear-the-stack-back-to-a-table-row-context">clear the stack
5984: back to a table row context</dfn>, it means that the UA must,
5985: 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 5986: element or an <code><a href="semantics.html#the-html-element-0">html</a></code> element, pop elements from the
1.1 mike 5987: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
5988:
5989: <p class="note">The <a href="#current-node">current node</a> being an
1.159 mike 5990: <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 5991: case</a>.</p>
5992:
5993:
5994: <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>
5995:
5996: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intd" title="insertion
5997: mode: in cell">in cell</a>", tokens must be handled as follows:</p>
5998:
5999: <dl class="switch"><dt>An end tag whose tag name is one of: "td", "th"</dt>
6000: <dd>
6001:
6002: <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
6003: scope</a> with the same tag name as that of the token, then
6004: this is a <a href="#parse-error">parse error</a> and the token must be
6005: ignored.</p>
6006:
6007: <p>Otherwise:</p>
6008:
6009: <p><a href="#generate-implied-end-tags">Generate implied end tags</a>.</p>
6010:
6011: <p>Now, if the <a href="#current-node">current node</a> is not an element
6012: with the same tag name as the token, then this is a
6013: <a href="#parse-error">parse error</a>.</p>
6014:
6015: <p>Pop elements from this stack until an element with the same
6016: tag name as the token has been popped from the stack.</p>
6017:
6018: <p><a href="#clear-the-list-of-active-formatting-elements-up-to-the-last-marker">Clear the list of active formatting elements up to
6019: the last marker</a>.</p>
6020:
6021: <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
6022: <a href="#current-node">current node</a> will be a <code><a href="tabular-data.html#the-tr-element">tr</a></code> element at
6023: this point.)</p>
6024:
6025: </dd>
6026:
6027: <dt>A start tag whose tag name is one of: "caption", "col",
6028: "colgroup", "tbody", "td", "tfoot", "th", "thead", "tr"</dt>
6029: <dd>
6030:
6031: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> does
6032: <em>not</em> <a href="#has-an-element-in-table-scope" title="has an element in table scope">have
6033: a <code>td</code> or <code>th</code> element in table
6034: scope</a>, then this is a <a href="#parse-error">parse error</a>; ignore
6035: the token. (<a href="#fragment-case">fragment case</a>)</p>
6036:
6037: <p>Otherwise, <a href="#close-the-cell">close the cell</a> (see below) and
6038: reprocess the current token.</p>
6039:
6040: </dd>
6041:
6042: <dt>An end tag whose tag name is one of: "body", "caption",
6043: "col", "colgroup", "html"</dt>
6044: <dd>
6045: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6046: </dd>
6047:
6048: <dt>An end tag whose tag name is one of: "table", "tbody",
6049: "tfoot", "thead", "tr"</dt>
6050: <dd>
6051:
6052: <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
6053: scope</a> with the same tag name as that of the token
6054: (which can only happen for "tbody", "tfoot" and "thead", or,
6055: in the <a href="#fragment-case">fragment case</a>), then this is a <a href="#parse-error">parse
6056: error</a> and the token must be ignored.</p>
6057:
6058: <p>Otherwise, <a href="#close-the-cell">close the cell</a> (see below) and
6059: reprocess the current token.</p>
6060:
6061: </dd>
6062:
6063: <dt>Anything else</dt>
6064: <dd>
6065: <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
6066: mode</a>.</p>
6067: </dd>
6068:
6069: </dl><p>Where the steps above say to <dfn id="close-the-cell">close the cell</dfn>, they
6070: mean to run the following algorithm:</p>
6071:
6072: <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>
6073: element in table scope</a>, then act as if an end tag token
6074: with the tag name "td" had been seen.</p></li>
6075:
6076: <li><p>Otherwise, the <a href="#stack-of-open-elements">stack of open elements</a> will
6077: <a href="#has-an-element-in-table-scope" title="has an element in table scope">have a
6078: <code>th</code> element in table scope</a>; act as if an end
6079: tag token with the tag name "th" had been seen.</p></li>
6080:
6081: </ol><p class="note">The <a href="#stack-of-open-elements">stack of open elements</a> cannot
6082: 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
6083: the same time, nor can it have neither when the <a href="#insertion-mode">insertion
6084: mode</a> is "<a href="#parsing-main-intd" title="insertion mode: in cell">in
6085: cell</a>".</p>
6086:
6087:
6088: <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>
6089:
6090: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inselect" title="insertion
6091: mode: in select">in select</a>", tokens must be handled as follows:</p>
6092:
6093: <dl class="switch"><dt>A character token</dt>
6094: <dd>
6095: <p><a href="#insert-a-character" title="insert a character">Insert the token's
6096: character</a> into the <a href="#current-node">current node</a>.</p>
6097: </dd>
6098:
6099: <dt>A comment token</dt>
6100: <dd>
6101: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6102: node</a> with the <code title="">data</code> attribute set to
6103: the data given in the comment token.</p>
6104: </dd>
6105:
6106: <dt>A DOCTYPE token</dt>
6107: <dd>
6108: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6109: </dd>
6110:
6111: <dt>A start tag whose tag name is "html"</dt>
6112: <dd>
6113: <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
6114: mode</a>.</p>
6115: </dd>
6116:
6117: <dt>A start tag whose tag name is "option"</dt>
6118: <dd>
6119:
6120: <p>If the <a href="#current-node">current node</a> is an <code><a href="forms.html#the-option-element">option</a></code>
6121: element, act as if an end tag with the tag name "option" had
6122: been seen.</p>
6123:
6124: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
6125:
6126: </dd>
6127:
6128: <dt>A start tag whose tag name is "optgroup"</dt>
6129: <dd>
6130:
6131: <p>If the <a href="#current-node">current node</a> is an <code><a href="forms.html#the-option-element">option</a></code>
6132: element, act as if an end tag with the tag name "option" had
6133: been seen.</p>
6134:
6135: <p>If the <a href="#current-node">current node</a> is an
6136: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, act as if an end tag with the
6137: tag name "optgroup" had been seen.</p>
6138:
6139: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
6140:
6141: </dd>
6142:
6143: <dt>An end tag whose tag name is "optgroup"</dt>
6144: <dd>
6145:
6146: <p>First, if the <a href="#current-node">current node</a> is an
6147: <code><a href="forms.html#the-option-element">option</a></code> element, and the node immediately before
6148: it in the <a href="#stack-of-open-elements">stack of open elements</a> is an
6149: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, then act as if an end tag with
6150: the tag name "option" had been seen.</p>
6151:
6152: <p>If the <a href="#current-node">current node</a> is an
6153: <code><a href="forms.html#the-optgroup-element">optgroup</a></code> element, then pop that node from the
6154: <a href="#stack-of-open-elements">stack of open elements</a>. Otherwise, this is a
6155: <a href="#parse-error">parse error</a>; ignore the token.</p>
6156:
6157: </dd>
6158:
6159: <dt>An end tag whose tag name is "option"</dt>
6160: <dd>
6161:
6162: <p>If the <a href="#current-node">current node</a> is an <code><a href="forms.html#the-option-element">option</a></code>
6163: element, then pop that node from the <a href="#stack-of-open-elements">stack of open
6164: elements</a>. Otherwise, this is a <a href="#parse-error">parse
6165: error</a>; ignore the token.</p>
6166:
6167: </dd>
6168:
6169: <dt>An end tag whose tag name is "select"</dt>
6170: <dd>
6171:
6172: <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
6173: scope</a> with the same tag name as the token, this is a
6174: <a href="#parse-error">parse error</a>. Ignore the token. (<a href="#fragment-case">fragment
6175: case</a>)</p>
6176:
6177: <p>Otherwise:</p>
6178:
6179: <p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a>
6180: until a <code><a href="forms.html#the-select-element">select</a></code> element has been popped from the
6181: stack.</p>
6182:
6183: <p><a href="#reset-the-insertion-mode-appropriately">Reset the insertion mode appropriately</a>.</p>
6184:
6185: </dd>
6186:
6187: <dt>A start tag whose tag name is "select"</dt>
6188: <dd>
6189:
6190: <p><a href="#parse-error">Parse error</a>. Act as if the token had been
6191: an end tag with the tag name "select" instead.</p>
6192:
6193: </dd>
6194:
6195: <dt>A start tag whose tag name is one of: "input", "keygen", "textarea"</dt>
6196: <dd>
1.73 mike 6197:
6198: <p><a href="#parse-error">Parse error</a>.</p>
6199:
1.124 mike 6200: <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>
6201: element in table scope</a>, ignore the token. (<a href="#fragment-case">fragment
6202: case</a>)</p>
1.73 mike 6203:
6204: <p>Otherwise, act as if an end tag with the tag name "select" had
6205: been seen, and reprocess the token.</p>
6206:
1.1 mike 6207: </dd>
6208:
6209: <dt>A start tag token whose tag name is "script"</dt>
6210: <dd>
6211: <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
6212: mode</a>.</p>
6213: </dd>
6214:
6215: <dt>An end-of-file token</dt>
6216: <dd>
6217:
6218: <p>If the <a href="#current-node">current node</a> is not the root
1.159 mike 6219: <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 6220: error</a>.</p>
6221:
6222: <p class="note">It can only be the <a href="#current-node">current node</a> in
6223: the <a href="#fragment-case">fragment case</a>.</p>
6224:
6225: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6226:
6227: </dd>
6228:
6229: <dt>Anything else</dt>
6230: <dd>
6231: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6232: </dd>
6233:
6234: </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>
6235:
6236: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inselectintable" title="insertion
6237: mode: in select in table">in select in table</a>", tokens must be handled as follows:</p>
6238:
6239: <dl class="switch"><dt>A start tag whose tag name is one of: "caption", "table",
6240: "tbody", "tfoot", "thead", "tr", "td", "th"</dt>
6241: <dd>
6242: <p><a href="#parse-error">Parse error</a>. Act as if an end tag with the tag
6243: name "select" had been seen, and reprocess the token.</p>
6244: </dd>
6245:
6246: <dt>An end tag whose tag name is one of: "caption", "table",
6247: "tbody", "tfoot", "thead", "tr", "td", "th"</dt>
6248: <dd>
6249:
6250: <p><a href="#parse-error">Parse error</a>.</p>
6251:
6252: <p>If the <a href="#stack-of-open-elements">stack of open elements</a> <a href="#has-an-element-in-table-scope">has an
6253: element in table scope</a> with the same tag name as that
6254: of the token, then act as if an end tag with the tag name
6255: "select" had been seen, and reprocess the token. Otherwise,
6256: ignore the token.</p>
6257:
6258: </dd>
6259:
6260: <dt>Anything else</dt>
6261: <dd>
6262: <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
6263: mode</a>.</p>
6264: </dd>
6265:
1.168 mike 6266: </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 6267:
6268: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inforeign" title="insertion
6269: mode: in foreign content">in foreign content</a>", tokens must be
6270: handled as follows:</p>
6271:
6272: <dl class="switch"><dt>A character token</dt>
6273: <dd>
6274:
6275: <p><a href="#insert-a-character" title="insert a character">Insert the token's
6276: character</a> into the <a href="#current-node">current node</a>.</p>
6277:
6278: <p>If the token is not one of U+0009 CHARACTER TABULATION, U+000A
6279: LINE FEED (LF), U+000C FORM FEED (FF), <!--U+000D CARRIAGE RETURN
6280: (CR),--> or U+0020 SPACE, then set the <a href="#frameset-ok-flag">frameset-ok
6281: flag</a> to "not ok".</p>
6282:
6283: </dd>
6284:
6285: <dt>A comment token</dt>
6286: <dd>
6287: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6288: node</a> with the <code title="">data</code> attribute set to
6289: the data given in the comment token.</p>
6290: </dd>
6291:
6292: <dt>A DOCTYPE token</dt>
6293: <dd>
6294: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6295: </dd>
6296:
6297: <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>
6298: <dd>
6299:
6300: <p>Pop the <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
6301: elements</a>.</p>
6302:
6303: <p>Let the <var title="">old insertion point</var> have the
6304: same value as the current <a href="#insertion-point">insertion point</a>. Let
6305: the <a href="#insertion-point">insertion point</a> be just before the <a href="#next-input-character">next
6306: input character</a>.</p>
6307:
6308: <p>Increment the parser's <a href="#script-nesting-level">script nesting level</a> by
6309: one. Set the <a href="#parser-pause-flag">parser pause flag</a> to true.</p>
6310:
6311: <p><a href="http://www.w3.org/TR/SVGMobile12/script.html#ScriptContentProcessing">Process
6312: the <code title="">script</code> element</a> according to the SVG
1.104 mike 6313: rules. <a href="references.html#refsSVG">[SVG]</a></p>
1.1 mike 6314:
1.159 mike 6315: <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 6316: tokenizer</a>, the parser will not be executed reentrantly,
6317: since the <a href="#parser-pause-flag">parser pause flag</a> is true.</p>
6318:
6319: <p>Decrement the parser's <a href="#script-nesting-level">script nesting level</a> by
6320: one. If the parser's <a href="#script-nesting-level">script nesting level</a> is zero,
6321: then set the <a href="#parser-pause-flag">parser pause flag</a> to false.</p>
6322:
6323: <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
6324: <a href="#insertion-point">insertion point</a> to its previous value. This value
6325: might be the "undefined" value.)</p>
6326:
6327: </dd>
6328:
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="">mi</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="">mo</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="">mn</code> element in the <a href="#mathml-namespace">MathML namespace</a>.</dt>
6332: <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>
6333: <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>
6334: <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>
6335: <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>
6336: <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>
6337: <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>
6338: <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>
6339: <dt>An end tag</dt>
6340: <dd>
6341:
6342: <p>Process the token <a href="#using-the-rules-for">using the rules for</a> the
6343: <a href="#secondary-insertion-mode">secondary insertion mode</a>.</p>
6344:
6345: <p>If, after doing so, the <a href="#insertion-mode">insertion mode</a> is still
6346: "<a href="#parsing-main-inforeign" title="insertion mode: in foreign content">in foreign
6347: content</a>", but there is no element in scope that has a
6348: namespace other than the <a href="#html-namespace-0">HTML namespace</a><!-- XXX this
6349: isn't well-defined; it means check to see if the bottom-most HTML
6350: element on the stack is in scope -->, switch the <a href="#insertion-mode">insertion
6351: mode</a> to the <a href="#secondary-insertion-mode">secondary insertion mode</a>.</p>
6352:
6353: </dd>
6354:
6355: <dt>A start tag whose tag name is one of: <!--"a",--> "b", "big",
6356: "blockquote", "body"<!--by inspection-->, "br", "center", "code",
6357: "dd", "div", "dl", "dt"<!-- so that dd and dt can be handled
6358: uniformly throughout the parser -->, "em", "embed", "h1", "h2",
6359: "h3", "h4"<!--for completeness-->, "h5", "h6"<!--for
6360: completeness-->, "head"<!--by inspection-->, "hr", "i", "img",
6361: "li", "listing"<!-- so that pre and listing can be handled
6362: uniformly throughout the parser -->, "menu", "meta", "nobr",
6363: "ol"<!-- so that dl, ul, and ol can be handled uniformly throughout
6364: the parser -->, "p", "pre", "ruby", "s", <!--"script",--> "small",
6365: "span", "strong", "strike"<!-- so that s and strike can be handled
6366: uniformly throughout the parser -->, <!--"style",--> "sub", "sup",
6367: "table"<!--by inspection-->, "tt", "u", "ul", "var"</dt>
6368: <!-- this list was determined empirically by studying over
6369: 6,000,000,000 pages that were specifically not XML pages -->
6370: <dt>A start tag whose tag name is "font", if the token has
6371: any attributes named "color", "face", or "size"</dt>
6372: <!-- the attributes here are required so that SVG <font> will go
6373: through as SVG but legacy <font>s won't -->
6374: <dt>An end-of-file token</dt>
6375: <dd>
6376:
6377: <p><a href="#parse-error">Parse error</a>.</p>
6378:
6379: <p>Pop elements from the <a href="#stack-of-open-elements">stack of open elements</a> until
6380: the <a href="#current-node">current node</a> is in the <a href="#html-namespace-0">HTML
6381: namespace</a>.</p>
6382:
6383: <p>Switch the <a href="#insertion-mode">insertion mode</a> to the <a href="#secondary-insertion-mode">secondary
6384: insertion mode</a>, and reprocess the token.</p>
6385:
6386: </dd>
6387:
6388: <dt>Any other start tag</dt>
6389: <dd>
6390:
6391: <p>If the <a href="#current-node">current node</a> is an element in the
6392: <a href="#mathml-namespace">MathML namespace</a>, <a href="#adjust-mathml-attributes">adjust MathML
6393: attributes</a> for the token. (This fixes the case of MathML
6394: attributes that are not all lowercase.)</p>
6395:
6396: <p>If the <a href="#current-node">current node</a> is an element in the <a href="#svg-namespace">SVG
6397: namespace</a>, and the token's tag name is one of the ones in
6398: the first column of the following table, change the tag name to
6399: the name given in the corresponding cell in the second
6400: column. (This fixes the case of SVG elements that are not all
6401: lowercase.)</p>
6402:
6403: <table><thead><tr><th> Tag name </th><th> Element name
6404: </th></tr></thead><tbody><tr><td> <code title="">altglyph</code> </td><td> <code title="">altGlyph</code>
6405: </td></tr><tr><td> <code title="">altglyphdef</code> </td><td> <code title="">altGlyphDef</code>
6406: </td></tr><tr><td> <code title="">altglyphitem</code> </td><td> <code title="">altGlyphItem</code>
6407: </td></tr><tr><td> <code title="">animatecolor</code> </td><td> <code title="">animateColor</code>
6408: </td></tr><tr><td> <code title="">animatemotion</code> </td><td> <code title="">animateMotion</code>
6409: </td></tr><tr><td> <code title="">animatetransform</code> </td><td> <code title="">animateTransform</code>
6410: </td></tr><tr><td> <code title="">clippath</code> </td><td> <code title="">clipPath</code>
6411: </td></tr><tr><td> <code title="">feblend</code> </td><td> <code title="">feBlend</code>
6412: </td></tr><tr><td> <code title="">fecolormatrix</code> </td><td> <code title="">feColorMatrix</code>
6413: </td></tr><tr><td> <code title="">fecomponenttransfer</code> </td><td> <code title="">feComponentTransfer</code>
6414: </td></tr><tr><td> <code title="">fecomposite</code> </td><td> <code title="">feComposite</code>
6415: </td></tr><tr><td> <code title="">feconvolvematrix</code> </td><td> <code title="">feConvolveMatrix</code>
6416: </td></tr><tr><td> <code title="">fediffuselighting</code> </td><td> <code title="">feDiffuseLighting</code>
6417: </td></tr><tr><td> <code title="">fedisplacementmap</code> </td><td> <code title="">feDisplacementMap</code>
6418: </td></tr><tr><td> <code title="">fedistantlight</code> </td><td> <code title="">feDistantLight</code>
6419: </td></tr><tr><td> <code title="">feflood</code> </td><td> <code title="">feFlood</code>
6420: </td></tr><tr><td> <code title="">fefunca</code> </td><td> <code title="">feFuncA</code>
6421: </td></tr><tr><td> <code title="">fefuncb</code> </td><td> <code title="">feFuncB</code>
6422: </td></tr><tr><td> <code title="">fefuncg</code> </td><td> <code title="">feFuncG</code>
6423: </td></tr><tr><td> <code title="">fefuncr</code> </td><td> <code title="">feFuncR</code>
6424: </td></tr><tr><td> <code title="">fegaussianblur</code> </td><td> <code title="">feGaussianBlur</code>
6425: </td></tr><tr><td> <code title="">feimage</code> </td><td> <code title="">feImage</code>
6426: </td></tr><tr><td> <code title="">femerge</code> </td><td> <code title="">feMerge</code>
6427: </td></tr><tr><td> <code title="">femergenode</code> </td><td> <code title="">feMergeNode</code>
6428: </td></tr><tr><td> <code title="">femorphology</code> </td><td> <code title="">feMorphology</code>
6429: </td></tr><tr><td> <code title="">feoffset</code> </td><td> <code title="">feOffset</code>
6430: </td></tr><tr><td> <code title="">fepointlight</code> </td><td> <code title="">fePointLight</code>
6431: </td></tr><tr><td> <code title="">fespecularlighting</code> </td><td> <code title="">feSpecularLighting</code>
6432: </td></tr><tr><td> <code title="">fespotlight</code> </td><td> <code title="">feSpotLight</code>
6433: </td></tr><tr><td> <code title="">fetile</code> </td><td> <code title="">feTile</code>
6434: </td></tr><tr><td> <code title="">feturbulence</code> </td><td> <code title="">feTurbulence</code>
6435: </td></tr><tr><td> <code title="">foreignobject</code> </td><td> <code title="">foreignObject</code>
6436: </td></tr><tr><td> <code title="">glyphref</code> </td><td> <code title="">glyphRef</code>
6437: </td></tr><tr><td> <code title="">lineargradient</code> </td><td> <code title="">linearGradient</code>
6438: </td></tr><tr><td> <code title="">radialgradient</code> </td><td> <code title="">radialGradient</code>
6439: <!--<tr> <td> <code title="">solidcolor</code> <td> <code title="">solidColor</code> (SVG 1.2)-->
6440: </td></tr><tr><td> <code title="">textpath</code> </td><td> <code title="">textPath</code>
6441: </td></tr></tbody></table><p>If the <a href="#current-node">current node</a> is an element in the <a href="#svg-namespace">SVG
6442: namespace</a>, <a href="#adjust-svg-attributes">adjust SVG attributes</a> for the
6443: token. (This fixes the case of SVG attributes that are not all
6444: lowercase.)</p>
6445:
6446: <p><a href="#adjust-foreign-attributes">Adjust foreign attributes</a> for the token. (This
6447: fixes the use of namespaced attributes, in particular XLink in
6448: SVG.)</p>
6449:
6450: <p><a href="#insert-a-foreign-element">Insert a foreign element</a> for the token, in the
6451: same namespace as the <a href="#current-node">current node</a>.</p>
6452:
6453: <p>If the token has its <i>self-closing flag</i> set, pop the
6454: <a href="#current-node">current node</a> off the <a href="#stack-of-open-elements">stack of open
6455: elements</a> and <a href="#acknowledge-self-closing-flag" title="acknowledge self-closing
6456: flag">acknowledge the token's <i>self-closing flag</i></a>.</p>
6457:
6458: </dd>
6459:
6460: </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>
6461:
6462: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-afterbody" title="insertion
6463: mode: after body">after body</a>", tokens must be handled as follows:</p>
6464:
6465: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
6466: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6467: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6468: <dd>
6469: <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
6470: mode</a>.</p>
6471: </dd>
6472:
6473: <dt>A comment token</dt>
6474: <dd>
6475: <p>Append a <code>Comment</code> node to the first element in
1.159 mike 6476: 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 6477: element), with the <code title="">data</code> attribute set to
6478: the data given in the comment token.</p>
6479: </dd>
6480:
6481: <dt>A DOCTYPE token</dt>
6482: <dd>
6483: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6484: </dd>
6485:
6486: <dt>A start tag whose tag name is "html"</dt>
6487: <dd>
6488: <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
6489: mode</a>.</p>
6490: </dd>
6491:
6492: <dt>An end tag whose tag name is "html"</dt>
6493: <dd>
6494:
6495: <p>If the parser was originally created as part of the <a href="#html-fragment-parsing-algorithm">HTML
6496: fragment parsing algorithm</a>, this is a <a href="#parse-error">parse
6497: error</a>; ignore the token. (<a href="#fragment-case">fragment case</a>)</p>
6498:
6499: <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
6500: body</a>".</p>
6501:
6502: </dd>
6503:
6504: <dt>An end-of-file token</dt>
6505: <dd>
6506: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6507: </dd>
6508:
6509: <dt>Anything else</dt>
6510: <dd>
6511:
6512: <p><a href="#parse-error">Parse error</a>. Switch the <a href="#insertion-mode">insertion
6513: mode</a> to "<a href="#parsing-main-inbody" title="insertion mode: in body">in
6514: body</a>" and reprocess the token.</p>
6515:
6516: </dd>
6517:
6518: </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>
6519:
6520: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inframeset" title="insertion
6521: mode: in frameset">in frameset</a>", tokens must be handled as follows:</p>
6522:
6523: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
6524: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6525: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6526: <dd>
6527: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
6528: the <a href="#current-node">current node</a>.</p>
6529: </dd>
6530:
6531: <dt>A comment token</dt>
6532: <dd>
6533: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6534: node</a> with the <code title="">data</code> attribute set to
6535: the data given in the comment token.</p>
6536: </dd>
6537:
6538: <dt>A DOCTYPE token</dt>
6539: <dd>
6540: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6541: </dd>
6542:
6543: <dt>A start tag whose tag name is "html"</dt>
6544: <dd>
6545: <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
6546: mode</a>.</p>
6547: </dd>
6548:
6549: <dt>A start tag whose tag name is "frameset"</dt>
6550: <dd>
6551: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.</p>
6552: </dd>
6553:
6554: <dt>An end tag whose tag name is "frameset"</dt>
6555: <dd>
6556:
6557: <p>If the <a href="#current-node">current node</a> is the root
1.159 mike 6558: <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 6559: error</a>; ignore the token. (<a href="#fragment-case">fragment
6560: case</a>)</p>
6561:
6562: <p>Otherwise, pop the <a href="#current-node">current node</a> from the
6563: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
6564:
6565: <p>If the parser was <em>not</em> originally created as part
6566: of the <a href="#html-fragment-parsing-algorithm">HTML fragment parsing algorithm</a>
6567: (<a href="#fragment-case">fragment case</a>), and the <a href="#current-node">current
1.5 mike 6568: node</a> is no longer a <code><a href="obsolete.html#frameset">frameset</a></code> element, then
1.1 mike 6569: switch the <a href="#insertion-mode">insertion mode</a> to "<a href="#parsing-main-afterframeset" title="insertion mode: after frameset">after
6570: frameset</a>".</p>
6571:
6572: </dd>
6573:
6574: <dt>A start tag whose tag name is "frame"</dt>
6575: <dd>
6576:
6577: <p><a href="#insert-an-html-element">Insert an HTML element</a> for the token.
6578: Immediately pop the <a href="#current-node">current node</a> off the
6579: <a href="#stack-of-open-elements">stack of open elements</a>.</p>
6580:
6581: <p><a href="#acknowledge-self-closing-flag" title="acknowledge self-closing flag">Acknowledge the
6582: token's <i>self-closing flag</i></a>, if it is set.</p>
6583:
6584: </dd>
6585:
6586: <dt>A start tag whose tag name is "noframes"</dt>
6587: <dd>
6588: <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
6589: mode</a>.</p>
6590: </dd>
6591:
6592: <dt>An end-of-file token</dt>
6593: <dd>
6594:
6595: <p>If the <a href="#current-node">current node</a> is not the root
1.159 mike 6596: <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 6597: error</a>.</p>
6598:
6599: <p class="note">It can only be the <a href="#current-node">current node</a> in
6600: the <a href="#fragment-case">fragment case</a>.</p>
6601:
6602: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6603:
6604: </dd>
6605:
6606: <dt>Anything else</dt>
6607: <dd>
6608: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6609: </dd>
6610:
6611: </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>
6612:
6613: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-afterframeset" title="insertion
6614: mode: after frameset">after frameset</a>", tokens must be handled as follows:</p>
6615:
6616: <!-- due to rules in the "in frameset" mode, this can't be entered in the fragment case -->
6617: <dl class="switch"><dt>A character token that is one of U+0009 CHARACTER
6618: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6619: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6620: <dd>
6621: <p><a href="#insert-a-character" title="insert a character">Insert the character</a> into
6622: the <a href="#current-node">current node</a>.</p>
6623: </dd>
6624:
6625: <dt>A comment token</dt>
6626: <dd>
6627: <p>Append a <code>Comment</code> node to the <a href="#current-node">current
6628: node</a> with the <code title="">data</code> attribute set to
6629: the data given in the comment token.</p>
6630: </dd>
6631:
6632: <dt>A DOCTYPE token</dt>
6633: <dd>
6634: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6635: </dd>
6636:
6637: <dt>A start tag whose tag name is "html"</dt>
6638: <dd>
6639: <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
6640: mode</a>.</p>
6641: </dd>
6642:
6643: <dt>An end tag whose tag name is "html"</dt>
6644: <dd>
6645: <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
6646: frameset</a>".</p>
6647: </dd>
6648:
6649: <dt>A start tag whose tag name is "noframes"</dt>
6650: <dd>
6651: <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
6652: mode</a>.</p>
6653: </dd>
6654:
6655: <dt>An end-of-file token</dt>
6656: <dd>
6657: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6658: </dd>
6659:
6660: <dt>Anything else</dt>
6661: <dd>
6662: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6663: </dd>
6664:
6665: </dl><p class="XXX">This doesn't handle UAs that don't support
6666: frames, or that do support frames but want to show the NOFRAMES
6667: content. Supporting the former is easy; supporting the latter is
6668: harder.</p>
6669:
6670:
6671: <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>
6672:
6673: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-after-after-body-insertion-mode" title="insertion
6674: mode: after after body">after after body</a>", tokens must be handled as follows:</p>
6675:
6676: <dl class="switch"><dt>A comment token</dt>
6677: <dd>
6678: <p>Append a <code>Comment</code> node to the <code>Document</code>
6679: object with the <code title="">data</code> attribute set to the
6680: data given in the comment token.</p>
6681: </dd>
6682:
6683: <dt>A DOCTYPE token</dt>
6684: <dt>A character token that is one of U+0009 CHARACTER
6685: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6686: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6687: <dt>A start tag whose tag name is "html"</dt>
6688: <dd>
6689: <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
6690: mode</a>.</p>
6691: </dd>
6692:
6693: <dt>An end-of-file token</dt>
6694: <dd>
6695: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6696: </dd>
6697:
6698: <dt>Anything else</dt>
6699: <dd>
6700: <p><a href="#parse-error">Parse error</a>. Switch the <a href="#insertion-mode">insertion mode</a>
6701: to "<a href="#parsing-main-inbody" title="insertion mode: in body">in body</a>" and
6702: reprocess the token.</p>
6703: </dd>
6704:
6705: </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>
6706:
6707: <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#the-after-after-frameset-insertion-mode" title="insertion
6708: mode: after after frameset">after after frameset</a>", tokens must be handled as follows:</p>
6709:
6710: <dl class="switch"><dt>A comment token</dt>
6711: <dd>
6712: <p>Append a <code>Comment</code> node to the <code>Document</code>
6713: object with the <code title="">data</code> attribute set to the
6714: data given in the comment token.</p>
6715: </dd>
6716:
6717: <dt>A DOCTYPE token</dt>
6718: <dt>A character token that is one of U+0009 CHARACTER
6719: TABULATION, U+000A LINE FEED (LF), U+000C FORM FEED (FF),
6720: <!--U+000D CARRIAGE RETURN (CR),--> or U+0020 SPACE</dt>
6721: <dt>A start tag whose tag name is "html"</dt>
6722: <dd>
6723: <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
6724: mode</a>.</p>
6725: </dd>
6726:
6727: <dt>An end-of-file token</dt>
6728: <dd>
6729: <p><a href="#stop-parsing">Stop parsing</a>.</p>
6730: </dd>
6731:
6732: <dt>A start tag whose tag name is "noframes"</dt>
6733: <dd>
6734: <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
6735: mode</a>.</p>
6736: </dd>
6737:
6738: <dt>Anything else</dt>
6739: <dd>
6740: <p><a href="#parse-error">Parse error</a>. Ignore the token.</p>
6741: </dd>
6742:
6743: </dl><h4 id="the-end"><span class="secno">9.2.6 </span>The end</h4>
6744:
6745: <p>Once the user agent <dfn id="stop-parsing" title="stop parsing">stops parsing</dfn>
6746: the document, the user agent must follow the steps in this
6747: section.</p>
6748:
1.10 mike 6749: <!-- this happens as part of one of the tasks that runs the parser -->
1.1 mike 6750:
1.10 mike 6751: <p>First, the user agent must set the <a href="dom.html#current-document-readiness">current document
6752: readiness</a> to "interactive" and the <a href="#insertion-point">insertion
6753: point</a> to undefined.</p>
6754:
6755: <p>Then, the user agent must then make a list of all the scripts
6756: 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
6757: document has finished parsing</a>, the <a href="semantics.html#list-of-scripts-that-will-execute-asynchronously">list of scripts that
6758: will execute asynchronously</a>, and the <a href="semantics.html#list-of-scripts-that-will-execute-as-soon-as-possible">list of scripts
6759: that will execute as soon as possible</a>. This is the <dfn id="list-of-scripts-pending-after-the-parser-stopped">list
6760: of scripts pending after the parser stopped</dfn>.</p>
6761:
6762: <p>The rules for <a href="semantics.html#when-a-script-completes-loading">when a script completes loading</a> start
6763: applying (script execution is no longer managed by the parser).</p>
1.1 mike 6764:
6765: <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
6766: execute as soon as possible</a> have <a href="semantics.html#completed-loading">completed
6767: loading</a>, or if the <a href="semantics.html#list-of-scripts-that-will-execute-asynchronously">list of scripts that will execute
6768: asynchronously</a> is not empty and the first script in that list
6769: has <a href="semantics.html#completed-loading">completed loading</a>, then the user agent must act as
6770: if those scripts just completed loading, following the rules given
6771: for that in the <code><a href="semantics.html#script">script</a></code> element definition.</p>
6772:
1.10 mike 6773: <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
6774: has finished parsing</a> is not empty, and the first item in this
6775: list has already <a href="semantics.html#completed-loading">completed loading</a>, then the user agent
6776: must act as if that script just finished loading.</p>
6777:
6778: <p class="note">By this point, there will be no scripts that have
6779: loaded but have not yet been executed.</p>
6780:
6781: <hr><!-- async --><p>Once all the scripts on the <a href="#list-of-scripts-pending-after-the-parser-stopped">list of scripts pending after
6782: the parser stopped</a> have <a href="semantics.html#completed-loading">completed loading</a> and
6783: been <a href="semantics.html#executing-a-script-block" title="executing a script block">executed</a>, the
6784: 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
6785: event</a> called <code title="event-DOMContentLoaded">DOMContentLoaded</code> at the
6786: <code>Document</code>. (If the list is empty, this happens
6787: immediately.)</p>
1.1 mike 6788:
1.10 mike 6789: <hr><!-- async --><p>Once everything that <dfn id="delay-the-load-event" title="delay the load event">delays the
1.1 mike 6790: load event</dfn> of the document has completed, the user agent must
6791: run the following steps:</p>
6792:
6793: <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
6794: readiness</a> to "complete".</li>
6795:
6796: <li>If the <code>Document</code> is in a <a href="browsers.html#browsing-context">browsing
6797: 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
6798: simple event</a> called <code title="event-load"><a href="video.html#event-load">load</a></code> at
6799: the <code>Document</code>'s <code><a href="browsers.html#window">Window</a></code> object, but with
6800: its <code title="dom-event-target">target</code> set to the
6801: <code>Document</code> object (and the <code title="dom-event-currentTarget">currentTarget</code> set to the
6802: <code><a href="browsers.html#window">Window</a></code> object).</li>
6803:
6804: <li>If the <code>Document</code> has a <a href="history.html#pending-state-object">pending state
6805: 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
6806: <code>Document</code>'s <code><a href="browsers.html#window">Window</a></code> object using the
6807: <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
6808: current value of the <a href="history.html#pending-state-object">pending state object</a>. This event
6809: must bubble but not be cancelable and has no default action.</li>
6810:
6811: </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
6812: manipulation task source</a>.</p>
6813:
6814: <!-- XXX make sure things "delay the load event", e.g. applet and
6815: object element's frame contents -->
6816:
6817: <p class="XXX">delaying the load event for things like image
6818: loads allows for intranet port scans (even without
6819: javascript!). Should we really encode that into the spec?</p>
6820:
6821:
6822: <!--XXX need to handle
6823: http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#2354
6824: 2354 // Don't open transient styles if it makes the stack deep, bug 58917.
6825: -->
6826:
6827: <!--XXX
6828: http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/nsHTMLTokenizer.cpp#749
6829: -->
6830:
6831: <!--
6832: see also CTextToken::ConsumeCharacterData() for CDATA parsing?
6833:
6834: 1212 1 Here's a tricky case from bug 22596: <h5><li><h5>
6835: 1213 How do we know that the 2nd <h5> should close the <LI> rather than nest inside the <LI>?
6836: 1214 (Afterall, the <h5> is a legal child of the <LI>).
6837: 1215
6838: 1216 The way you know is that there is no root between the two, so the <h5> binds more
6839: 1217 tightly to the 1st <h5> than to the <LI>.
6840: 1218 2. Also, bug 6148 shows this case: <SPAN><DIV><SPAN>
6841: 1219 From this case we learned not to execute this logic if the parent is a block.
6842: 1220
6843: 1221 3. Fix for 26583
6844: 1222 Ex. <A href=foo.html><B>foo<A href-bar.html>bar</A></B></A> <- A legal HTML
6845: 1223 In the above example clicking on "foo" or "bar" should link to
6846: 1224 foo.html or bar.html respectively. That is, the inner <A> should be informed
6847: 1225 about the presence of an open <A> above <B>..so that the inner <A> can close out
6848: 1226 the outer <A>. The following code does it for us.
6849: 1227
6850: 1228 4. Fix for 27865 [ similer to 22596 ]. Ex: <DL><DD><LI>one<DD><LI>two
6851: - http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#1211
6852:
6853: 815 // Here's a problem. If theTag is legal in here, we don't move it
6854: 816 // out. So if we're moving stuff out of here, the parent of theTag
6855: 817 // gets closed at this point. But some things are legal
6856: 818 // _everywhere_ and hence would effectively close out misplaced
6857: 819 // content in tables. This is undesirable, so treat them as
6858: 820 // illegal here so they'll be shipped out with their parents and
6859: 821 // siblings. See bug 40855 for an explanation (that bug was for
6860: 822 // comments, but the same issues arise with whitespace, newlines,
6861: 823 // noscript, etc). Script is special, though. Shipping it out
6862: 824 // breaks document.write stuff. See bug 243064.
6863: - http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#825
6864:
6865:
6866: 1326 /**************************************************************************************
6867: 1327 *
6868: 1328 * Now a little code to deal with bug #49687 (crash when layout stack gets too deep)
6869: 1329 * I've also opened this up to any container (not just inlines): re bug 55095
6870: 1330 * Improved to handle bug 55980 (infinite loop caused when DEPTH is exceeded and
6871: 1331 * </P> is encountered by itself (<P>) is continuously produced.
6872: 1332 *
6873: 1333 **************************************************************************************/
6874:
6875: 1912 // Oh boy!! we found a "stray" tag. Nav4.x and IE introduce line break in
6876: 1913 // such cases. So, let's simulate that effect for compatibility.
6877: 1914 // Ex. <html><body>Hello</P>There</body></html>
6878: http://lxr.mozilla.org/mozilla/source/parser/htmlparser/src/CNavDTD.cpp#1912
6879:
6880: http://lxr.mozilla.org/seamonkey/search?string=nested
6881: /parser/htmlparser/src/CNavDTD.cpp, line 791 - * 2. <CENTER><DL><DT><A><CENTER> allow nested <CENTER>
6882: /parser/htmlparser/src/CNavDTD.cpp, line 792 - * 3. <TABLE><TR><TD><TABLE>... allow nested <TABLE>
6883: /parser/htmlparser/src/CNavDTD.cpp, line 2562 - // Discard nested forms - bug 72639
6884: /parser/htmlparser/src/nsElementTable.cpp, line 1453 - * 2. <CENTER><DL><DT><A><CENTER> allow nested <CENTER>
6885: /parser/htmlparser/src/nsElementTable.cpp, line 1454 - * 3. <TABLE><TR><TD><TABLE>... allow nested <TABLE>
6886: /parser/htmlparser/src/nsElementTable.cpp, line 1901 - // Ex: <H1><LI><H1><LI>. Inner LI has the potential of getting nested
6887: -->
6888:
6889:
6890: <h4 id="coercing-an-html-dom-into-an-infoset"><span class="secno">9.2.7 </span>Coercing an HTML DOM into an infoset</h4>
6891:
6892: <p>When an application uses an <a href="#html-parser">HTML parser</a> in
6893: conjunction with an XML pipeline, it is possible that the
6894: constructed DOM is not compatible with the XML tool chain in certain
6895: subtle ways. For example, an XML toolchain might not be able to
6896: represent attributes with the name <code title="">xmlns</code>,
6897: since they conflict with the Namespaces in XML syntax. There is also
6898: some data that the <a href="#html-parser">HTML parser</a> generates that isn't
6899: included in the DOM itself. This section specifies some rules for
6900: handling these issues.</p>
6901:
6902: <p>If the XML API being used doesn't support DOCTYPEs, the tool may
6903: drop DOCTYPEs altogether.</p>
6904:
6905: <p>If the XML API doesn't support attributes in no namespace that
6906: are named "<code title="">xmlns</code>", attributes whose names
6907: start with "<code title="">xmlns:</code>", or attributes in the
6908: <a href="#xmlns-namespace">XMLNS namespace</a>, then the tool may drop such
6909: attributes.</p>
6910:
6911: <p>The tool may annotate the output with any namespace declarations
6912: required for proper operation.</p>
6913:
6914: <p>If the XML API being used restricts the allowable characters in
6915: the local names of elements and attributes, then the tool may map
6916: all element and attribute local names that the API wouldn't support
6917: to a set of names that <em>are</em> allowed, by replacing any
6918: character that isn't supported with the uppercase letter U and the
6919: six digits of the character's Unicode code point when expressed in
6920: hexadecimal, using digits 0-9 and capital letters A-F as the
6921: symbols, in increasing numeric order.</p>
6922:
6923: <p class="example">For example, the element name <code title="">foo<bar</code>, which can be output by the <a href="#html-parser">HTML
6924: parser</a>, though it is neither a legal HTML element name nor a
6925: well-formed XML element name, would be converted into <code title="">fooU00003Cbar</code>, which <em>is</em> a well-formed XML
6926: element name (though it's still not legal in HTML by any means).</p>
6927:
6928: <p class="example">As another example, consider the attribute
6929: <code>xlink:href</code>. Used on a MathML element, it becomes, after
6930: being <a href="#adjust-foreign-attributes" title="adjust foreign attributes">adjusted</a>, an
6931: attribute with a prefix "<code title="">xlink</code>" and a local
6932: name "<code title="">href</code>". However, used on an HTML element,
6933: it becomes an attribute with no prefix and the local name "<code title="">xlink:href</code>", which is not a valid NCName, and thus
6934: might not be accepted by an XML API. It could thus get converted,
6935: becoming "<code title="">xlinkU00003Ahref</code>".</p>
6936:
6937: <p class="note">The resulting names from this conversion
6938: conveniently can't clash with any attribute generated by the
6939: <a href="#html-parser">HTML parser</a>, since those are all either lowercase or
6940: those listed in the <a href="#adjust-foreign-attributes">adjust foreign attributes</a>
6941: algorithm's table.</p>
6942:
6943: <p>If the XML API restricts comments from having two consecutive
6944: U+002D HYPHEN-MINUS characters (--), the tool may insert a single
6945: U+0020 SPACE character between any such offending characters.</p>
6946:
6947: <p>If the XML API restricts comments from ending in a
6948: U+002D HYPHEN-MINUS character (-), the tool may insert a single
6949: U+0020 SPACE character at the end of such comments.</p>
6950:
6951: <p>If the XML API restricts allowed characters in character data,
6952: the tool may replace any U+000C FORM FEED (FF) character with a
6953: U+0020 SPACE character, and any other literal non-XML character with
6954: a U+FFFD REPLACEMENT CHARACTER.</p>
6955:
6956: <p>If the tool has no way to convey out-of-band information, then
6957: the tool may drop the following information:</p>
6958:
6959: <ul><li>Whether the document is set to <i><a href="dom.html#no-quirks-mode">no quirks mode</a></i>,
6960: <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>
6961:
6962: <li>The association between form controls and forms that aren't
6963: their nearest <code><a href="forms.html#the-form-element">form</a></code> element ancestor (use of the
6964: <a href="#form-element-pointer"><code>form</code> element pointer</a> in the parser)</li>
6965:
6966: </ul><p class="note">The mutations allowed by this section apply
6967: <em>after</em> the <a href="#html-parser">HTML parser</a>'s rules have been
6968: applied. For example, a <code title=""><a::></code> start tag
6969: will be closed by a <code title=""></a::></code> end tag, and
6970: never by a <code title=""></aU00003AU00003A></code> end tag, even
6971: if the user agent is using the rules above to then generate an
6972: actual element in the DOM with the name <code title="">aU00003AU00003A</code> for that start tag.</p>
6973:
6974:
6975:
1.35 mike 6976: <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 6977:
6978: <p><i>This section is non-normative.</i></p>
6979:
6980: <p>This section examines some erroneous markup and discusses how
6981: the <a href="#html-parser">HTML parser</a> handles these cases.</p>
6982:
6983:
6984: <h5 id="misnested-tags:-b-i-b-i"><span class="secno">9.2.8.1 </span>Misnested tags: <b><i></b></i></h5>
6985:
6986: <p><i>This section is non-normative.</i></p>
6987:
6988: <p>The most-often discussed example of erroneous markup is as
6989: follows:</p>
6990:
6991: <pre><p>1<b>2<i>3</b>4</i>5</p></pre>
6992:
6993: <p>The parsing of this markup is straightforward up to the "3". At
6994: this point, the DOM looks like this:</p>
6995:
1.159 mike 6996: <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
6997: 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 6998: <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
6999: formatting elements</a> just has two: <code><a href="text-level-semantics.html#the-b-element">b</a></code> and
7000: <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>
7001:
7002: <p>Upon receiving the end tag token with the tag name "b", the "<a href="#adoptionAgency">adoption agency algorithm</a>" is
7003: invoked. This is a simple case, in that the <var title="">formatting
7004: element</var> is the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element, and there is no
7005: <var title="">furthest block</var>. Thus, the <a href="#stack-of-open-elements">stack of open
1.159 mike 7006: elements</a> ends up with just three elements: <code><a href="semantics.html#the-html-element-0">html</a></code>,
7007: <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 7008: active formatting elements</a> has just one: <code><a href="text-level-semantics.html#the-i-element">i</a></code>. The
7009: DOM tree is unmodified at this point.</p>
7010:
7011: <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
7012: the active formatting elements</a>, in this case just the
7013: <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
7014: for the "4" text node. After the end tag token for the "i" is also
7015: received, and the "5" text node is inserted, the DOM looks as
7016: follows:</p>
7017:
1.159 mike 7018: <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 7019:
7020: <p><i>This section is non-normative.</i></p>
7021:
7022: <p>A case similar to the previous one is the following:</p>
7023:
7024: <pre><b>1<p>2</b>3</p></pre>
7025:
7026: <p>Up to the "2" the parsing here is straightforward:</p>
7027:
1.159 mike 7028: <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 7029: "b" is parsed.</p>
7030:
7031: <p>Before that token is seen, the <a href="#stack-of-open-elements">stack of open
1.159 mike 7032: elements</a> has four elements on it: <code><a href="semantics.html#the-html-element-0">html</a></code>,
7033: <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 7034: <a href="#list-of-active-formatting-elements">list of active formatting elements</a> just has the one:
7035: <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>
7036:
7037: <p>Upon receiving the end tag token with the tag name "b", the "<a href="#adoptionAgency">adoption agency algorithm</a>" is invoked, as
7038: in the previous example. However, in this case, there <em>is</em> a
7039: <var title="">furthest block</var>, namely the <code><a href="semantics.html#the-p-element">p</a></code> element. Thus,
7040: this time the adoption agency algorithm isn't skipped over.</p>
7041:
1.159 mike 7042: <p>The <var title="">common ancestor</var> is the <code><a href="semantics.html#the-body-element-0">body</a></code>
1.1 mike 7043: element. A conceptual "bookmark" marks the position of the
7044: <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
7045: elements</a>, but since that list has only one element in it,
7046: it won't have much effect.</p>
7047:
7048: <p>As the algorithm progresses, <var title="">node</var> ends up set
7049: to the formatting element (<code><a href="text-level-semantics.html#the-b-element">b</a></code>), and <var title="">last
7050: node</var> ends up set to the <var title="">furthest block</var>
7051: (<code><a href="semantics.html#the-p-element">p</a></code>).</p>
7052:
7053: <p>The <var title="">last node</var> gets appended (moved) to the
7054: <var title="">common ancestor</var>, so that the DOM looks like:</p>
7055:
1.159 mike 7056: <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 7057: <code><a href="semantics.html#the-p-element">p</a></code> element are moved to it:</p>
7058:
1.159 mike 7059: <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 7060: <code><a href="semantics.html#the-p-element">p</a></code> element, so that the DOM looks like:</p>
7061:
1.159 mike 7062: <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 7063: active formatting elements</a> and the <a href="#stack-of-open-elements">stack of open
7064: elements</a>, so that when the "3" is parsed, it is appended to
7065: the <code><a href="semantics.html#the-p-element">p</a></code> element:</p>
7066:
1.159 mike 7067: <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 7068:
7069: <p><i>This section is non-normative.</i></p>
7070:
7071: <p>Error handling in tables is, for historical reasons, especially
7072: strange. For example, consider the following markup:</p>
7073:
7074: <pre><table><strong><b></strong><tr><td>aaa</td></tr><strong>bbb</strong></table>ccc</pre>
7075:
7076: <p>The highlighted <code><a href="text-level-semantics.html#the-b-element">b</a></code> element start tag is not allowed
7077: directly inside a table like that, and the parser handles this case
7078: 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
7079: examining the DOM tree as it stands just after the
7080: <code><a href="tabular-data.html#the-table-element">table</a></code> element's start tag has been seen:</p>
7081:
1.159 mike 7082: <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 7083: tag has been seen:</p>
7084:
1.159 mike 7085: <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
7086: 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 7087: <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
7088: resulting DOM tree); the <a href="#list-of-active-formatting-elements">list of active formatting
7089: elements</a> just has the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in it; and the
7090: <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intable" title="insertion mode: in
7091: table">in table</a>".</p>
7092:
7093: <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
7094: to be popped off the stack and a <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> start tag to be
7095: 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
7096: then handled in a rather straight-forward manner, taking the parser
7097: through the "<a href="#parsing-main-intbody" title="insertion mode: in table body">in table
7098: body</a>" and "<a href="#parsing-main-intr" title="insertion mode: in row">in
7099: row</a>" insertion modes, after which the DOM looks as
7100: follows:</p>
7101:
1.159 mike 7102: <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
7103: 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 7104: <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
7105: formatting elements</a> still has the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in
7106: it; and the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intr" title="insertion
7107: mode: in row">in row</a>".</p>
7108:
7109: <p>The <code><a href="tabular-data.html#the-td-element">td</a></code> element start tag token, after putting a
7110: <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
7111: 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
7112: mode</a>).</p>
7113:
1.159 mike 7114: <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 7115: no <code><a href="text-level-semantics.html#the-b-element">b</a></code> element is created to hold the resulting text
7116: node:</p>
7117:
1.159 mike 7118: <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 7119: handling them, the <a href="#stack-of-open-elements">stack of open elements</a> has on it the
1.159 mike 7120: 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 7121: 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
7122: elements</a> still has the <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in it (the
7123: marker having been removed by the "td" end tag token); and the
7124: <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-intbody" title="insertion mode: in
7125: table body">in table body</a>".</p>
7126:
7127: <p>Thus it is that the "bbb" character tokens are found. These
7128: trigger the "<a href="#parsing-main-intabletext" title="insertion mode: in table text">in table
7129: text</a>" insertion mode to be used (with the <a href="#original-insertion-mode">original
7130: insertion mode</a> set to "<a href="#parsing-main-intbody" title="insertion mode: in table
7131: body">in table body</a>"). The character tokens are collected,
7132: and when the next token (the <code><a href="tabular-data.html#the-table-element">table</a></code> element end tag) is
7133: seen, they are processed as a group. Since they are not all spaces,
7134: 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,
7135: which defer to the "<a href="#parsing-main-inbody" title="insertion mode: in body">in
7136: body</a>" insertion mode but with <a href="#foster-parent" title="foster
7137: parent">foster parenting</a>.</p>
7138:
7139: <p>When <a href="#reconstruct-the-active-formatting-elements" title="reconstruct the active formatting elements">the
7140: active formatting elements are reconstructed</a>, a
7141: <code><a href="text-level-semantics.html#the-b-element">b</a></code> element is created and <a href="#foster-parent" title="foster
7142: parent">foster parented</a>, and then the "bbb" text node is
7143: appended to it:</p>
7144:
1.159 mike 7145: <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
7146: <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 7147: <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
7148: this doesn't match the resulting tree!); the <a href="#list-of-active-formatting-elements">list of active
7149: formatting elements</a> has the new <code><a href="text-level-semantics.html#the-b-element">b</a></code> element in it;
7150: and the <a href="#insertion-mode">insertion mode</a> is still "<a href="#parsing-main-intbody" title="insertion
7151: mode: in table body">in table body</a>".</p>
7152:
7153: <p>Had the character tokens been only <a href="infrastructure.html#space-character" title="space
7154: character">space characters</a> instead of "bbb", then those
7155: <a href="infrastructure.html#space-character" title="space character">space characters</a> would just be
7156: appended to the <code><a href="tabular-data.html#the-tbody-element">tbody</a></code> element.</p>
7157:
7158: <p>Finally, the <code><a href="tabular-data.html#the-table-element">table</a></code> is closed by a "table" end
7159: tag. This pops all the nodes from the <a href="#stack-of-open-elements">stack of open
7160: elements</a> up to and including the <code><a href="tabular-data.html#the-table-element">table</a></code> element,
7161: but it doesn't affect the <a href="#list-of-active-formatting-elements">list of active formatting
7162: elements</a>, so the "ccc" character tokens after the table
7163: result in yet another <code><a href="text-level-semantics.html#the-b-element">b</a></code> element being created, this
7164: time after the table:</p>
7165:
1.159 mike 7166: <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 7167:
7168: <p><i>This section is non-normative.</i></p>
7169:
7170: <p>Consider the following markup, which for this example we will
7171: 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 7172: content of an <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code> in another document with the
1.1 mike 7173: <a href="infrastructure.html#url">URL</a> <code title="">http://example.com/outer</code>:</p>
7174:
7175: <pre><div id=a>
7176: <script>
7177: var div = document.getElementById('a');
7178: parent.document.body.appendChild(div);
7179: </script>
7180: <script>
7181: alert(document.URL);
7182: </script>
7183: </div>
7184: <script>
7185: alert(document.URL);
7186: </script></pre>
7187:
7188: <p>Up to the first "script" end tag, before the script is parsed,
7189: the result is relatively straightforward:</p>
7190:
1.159 mike 7191: <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 7192: </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
7193: and its child <code><a href="semantics.html#script">script</a></code> element are gone:</p>
7194:
1.159 mike 7195: <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 7196: aforementioned outer <a href="browsers.html#browsing-context">browsing context</a>. However, the
7197: <a href="#stack-of-open-elements">stack of open elements</a> <em>still contains the
7198: <code><a href="interactive-elements.html#the-div-element">div</a></code> element</em>.</p>
7199:
7200: <p>Thus, when the second <code><a href="semantics.html#script">script</a></code> element is parsed, it
7201: is inserted <em>into the outer <code>Document</code>
7202: object</em>.</p>
7203:
7204: <p>This also means that the <a href="browsers.html#script-s-global-object">script's global object</a> is
7205: the outer <a href="browsers.html#browsing-context">browsing context</a>'s <code><a href="browsers.html#window">Window</a></code>
7206: object, <em>not</em> the <code><a href="browsers.html#window">Window</a></code> object inside the
1.159 mike 7207: <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code>.</p>
1.1 mike 7208:
7209: <p class="note">This isn't a security problem since the script that
7210: moves the <code><a href="interactive-elements.html#the-div-element">div</a></code> into the outer <code>Document</code> can
7211: only do so because they have the two <code>Document</code> object
1.159 mike 7212: have the same <a href="browsers.html#origin">origin</a>.</p>
1.1 mike 7213:
7214: <p>Thus, the first alert says "http://example.com/outer".</p>
7215:
7216: <p>Once the <code><a href="interactive-elements.html#the-div-element">div</a></code> element's end tag is parsed, the
7217: <code><a href="interactive-elements.html#the-div-element">div</a></code> element is popped off the stack, and so the next
7218: <code><a href="semantics.html#script">script</a></code> element is in the inner <code>Document</code>:</p>
7219:
1.159 mike 7220: <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 7221:
7222:
7223:
1.159 mike 7224: <h3 id="namespaces"><span class="secno">9.3 </span>Namespaces</h3><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/60">ISSUE-60</a> (html5-xhtml-namespace) blocks progress to Last Call</span></p>
1.1 mike 7225:
7226: <p>The <dfn id="html-namespace-0">HTML namespace</dfn> is: <code>http://www.w3.org/1999/xhtml</code></p>
7227:
7228: <p>The <dfn id="mathml-namespace">MathML namespace</dfn> is: <code>http://www.w3.org/1998/Math/MathML</code></p>
7229:
7230: <p>The <dfn id="svg-namespace">SVG namespace</dfn> is: <code>http://www.w3.org/2000/svg</code></p>
7231:
7232: <p>The <dfn id="xlink-namespace">XLink namespace</dfn> is: <code>http://www.w3.org/1999/xlink</code></p>
7233:
7234: <p>The <dfn id="xml-namespace">XML namespace</dfn> is: <code>http://www.w3.org/XML/1998/namespace</code></p>
7235:
7236: <p>The <dfn id="xmlns-namespace">XMLNS namespace</dfn> is: <code>http://www.w3.org/2000/xmlns/</code></p>
7237:
7238: <hr><p>Data mining tools and other user agents that perform operations
1.83 mike 7239: on <code><a href="iana-considerations.html#text-html">text/html</a></code> content without running scripts,
1.1 mike 7240: evaluating CSS or XPath expressions, or otherwise exposing the
7241: resulting DOM to arbitrary content, may "support namespaces" by just
7242: asserting that their DOM node analogues are in certain namespaces,
7243: without actually exposing the above strings.</p>
7244:
7245:
7246:
7247:
7248: <h3 id="serializing-html-fragments"><span class="secno">9.4 </span>Serializing HTML fragments</h3>
7249:
7250: <p>The following steps form the <dfn id="html-fragment-serialization-algorithm">HTML fragment serialization
7251: algorithm</dfn>. The algorithm takes as input a DOM
7252: <code>Element</code> or <code>Document</code>, referred to as <var title="">the node</var>, and either returns a string or raises an
7253: exception.</p>
7254:
7255: <p class="note">This algorithm serializes the <em>children</em> of
7256: the node being serialized, not the node itself.</p>
7257:
7258: <ol><li><p>Let <var title="">s</var> be a string, and initialize it to
7259: the empty string.</p></li>
7260:
7261: <li>
7262:
7263: <p>For each child node of <var title="">the node</var>, in
7264: <a href="infrastructure.html#tree-order">tree order</a>, run the following steps:
7265:
7266: </p><ol><li><p>Let <var title="">current node</var> be the child node
7267: being processed.</p></li>
7268:
7269: <li>
7270:
7271: <p>Append the appropriate string from the following list to
7272: <var title="">s</var>:</p>
7273:
7274: <dl class="switch"><dt>If <var title="">current node</var> is an <code title="">Element</code></dt>
7275:
7276: <dd>
7277:
7278: <p>Append a U+003C LESS-THAN SIGN (<code title=""><</code>)
7279: character, followed by the element's tag name. (For nodes
7280: created by the <a href="#html-parser">HTML parser</a> or <code title="">Document.createElement()</code>, the tag name will be
7281: lowercase.)</p>
7282:
7283: <p>For each attribute that the element has, append a U+0020
7284: SPACE character, the attribute's name (which, for attributes
7285: 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
7286: U+003D EQUALS SIGN (<code title="">=</code>) character, a
7287: U+0022 QUOTATION MARK (<code title="">"</code>)
7288: character, the attribute's value, <a href="#escapingString" title="escaping a
7289: string">escaped as described below</a> in <i>attribute
7290: mode</i>, and a second U+0022 QUOTATION MARK (<code title="">"</code>) character.</p>
7291:
7292: <p>While the exact order of attributes is UA-defined, and may
7293: depend on factors such as the order that the attributes were
7294: given in the original markup, the sort order must be stable,
7295: such that consecutive invocations of this algorithm serialize an
7296: element's attributes in the same order.</p>
7297:
7298: <p>Append a U+003E GREATER-THAN SIGN (<code title="">></code>)
7299: character.</p>
7300:
7301: <p>If <var title="">current node</var> is an
1.5 mike 7302: <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 7303: <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 7304: <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>,
7305: <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>,
7306: <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 7307: <code><a href="obsolete.html#spacer">spacer</a></code>, or <code>wbr</code> element, then
1.1 mike 7308: continue on to the next child node at this point.</p> <!--
7309: also, i guess: image and isindex, but we don't list those
7310: because we don't consider those "elements", more "macros", and
7311: thus we should never serialize them -->
7312:
7313: <p>If <var title="">current node</var> is a <code><a href="semantics.html#the-pre-element">pre</a></code>,
1.42 mike 7314: <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 7315: a U+000A LINE FEED (LF) character.</p>
7316:
7317: <p>Append the value of running the <a href="#html-fragment-serialization-algorithm">HTML fragment
7318: serialization algorithm</a> on the <var title="">current
7319: node</var> element (thus recursing into this algorithm for
7320: 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,
7321: and finally a U+003E GREATER-THAN SIGN (<code title="">></code>) character.</p>
7322:
7323: </dd>
7324:
7325:
7326: <dt>If <var title="">current node</var> is a <code title="">Text</code> or <code title="">CDATASection</code>
7327: node</dt>
7328:
7329: <dd>
7330:
1.19 mike 7331: <p>If the parent of <var title="">current node</var> is a
1.42 mike 7332: <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 7333: <code><a href="text-level-semantics.html#the-iframe-element">iframe</a></code>, <code><a href="obsolete.html#noembed">noembed</a></code>,
1.5 mike 7334: <code><a href="obsolete.html#noframes">noframes</a></code>, <code><a href="semantics.html#the-noscript-element">noscript</a></code>, or
1.42 mike 7335: <code><a href="obsolete.html#plaintext">plaintext</a></code> element, then append the value of <var title="">current node</var>'s <code title="">data</code> DOM
1.1 mike 7336: attribute literally.</p> <!-- note about noscript: we're
7337: assuming here that scripting is enabled. If this algorithm is
1.19 mike 7338: used with scripting disabled, this won't work
7339: right. (e.g. This might affect calling innerHTML on nodes in a
7340: document that is being designMode'd) -->
1.1 mike 7341:
7342: <p>Otherwise, append the value of <var title="">current
7343: node</var>'s <code title="">data</code> DOM attribute, <a href="#escapingString" title="escaping a string">escaped as described
7344: below</a>.</p>
7345:
7346: </dd>
7347:
7348:
7349: <dt>If <var title="">current node</var> is a <code title="">Comment</code></dt>
7350:
7351: <dd>
7352:
7353: <p>Append the literal string <code><!--</code> (U+003C
7354: LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+002D HYPHEN-MINUS,
7355: U+002D HYPHEN-MINUS), followed by the value of <var title="">current node</var>'s <code title="">data</code> DOM
7356: attribute, followed by the literal string <code>--></code>
7357: (U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS, U+003E GREATER-THAN
7358: SIGN).</p>
7359:
7360: </dd>
7361:
7362:
7363: <dt>If <var title="">current node</var> is a <code title="">ProcessingInstruction</code></dt>
7364:
7365: <dd>
7366:
7367: <p>Append the literal string <code><?</code> (U+003C
7368: LESS-THAN SIGN, U+003F QUESTION MARK), followed by the value
7369: of <var title="">current node</var>'s <code title="">target</code> DOM attribute, followed by a single
7370: U+0020 SPACE character, followed by the value of <var title="">current node</var>'s <code title="">data</code> DOM
7371: attribute, followed by a single U+003E GREATER-THAN SIGN
7372: character ('>').</p>
7373:
7374: </dd>
7375:
7376:
7377: <dt>If <var title="">current node</var> is a <code title="">DocumentType</code></dt>
7378:
7379: <dd>
7380:
7381: <p>Append the literal string <code><!DOCTYPE</code> (U+003C
7382: LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+0044 LATIN CAPITAL
7383: LETTER D, U+004F LATIN CAPITAL LETTER O, U+0043 LATIN CAPITAL
7384: LETTER C, U+0054 LATIN CAPITAL LETTER T, U+0059 LATIN CAPITAL
7385: LETTER Y, U+0050 LATIN CAPITAL LETTER P, U+0045 LATIN CAPITAL
7386: LETTER E), followed by a space (U+0020 SPACE), followed by the
7387: value of <var title="">current node</var>'s <code title="">name</code> DOM attribute, followed by the literal
7388: string <code>></code> (U+003E GREATER-THAN SIGN).</p>
7389:
7390: </dd>
7391:
7392:
7393: </dl><p>Other node types (e.g. <code title="">Attr</code>) cannot
7394: occur as children of elements. If, despite this, they somehow do
7395: occur, this algorithm must raise an
7396: <code><a href="infrastructure.html#invalid_state_err">INVALID_STATE_ERR</a></code> exception.</p>
7397:
7398: </li>
7399:
7400: </ol></li>
7401:
7402: <li><p>The result of the algorithm is the string <var title="">s</var>.</p></li>
7403:
7404: </ol><p><dfn id="escapingString">Escaping a string</dfn> (for the
7405: purposes of the algorithm above) consists of replacing any
7406: occurrences of the "<code title="">&</code>" character by the
7407: string "<code title="">&amp;</code>", any occurrences of the
7408: U+00A0 NO-BREAK SPACE character by the string "<code title="">&nbsp;</code>", and, if the algorithm was invoked in
7409: 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
7410: 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>
7411:
7412: <p class="note">Entity reference nodes are <a href="infrastructure.html#entity-references">assumed to be expanded</a> by the user
7413: agent, and are therefore not covered in the algorithm above.</p>
7414:
7415: <p class="note">It is possible that the output of this algorithm, if
7416: parsed with an <a href="#html-parser">HTML parser</a>, will not return the
7417: original tree structure. For instance, if a <code><a href="forms.html#the-textarea-element">textarea</a></code>
7418: element to which a <code title="">Comment</code> node has been
7419: appended is serialized and the output is then reparsed, the comment
7420: will end up being displayed in the text field. Similarly, if, as a
7421: result of DOM manipulation, an element contains a comment that
7422: contains the literal string "<code title="">--></code>", then
7423: when the result of serializing the element is parsed, the comment
7424: will be truncated at that point and the rest of the comment will be
7425: interpreted as markup. More examples would be making a
7426: <code><a href="semantics.html#script">script</a></code> element contain a text node with the text string
7427: "<code></script></code>", or having a <code><a href="semantics.html#the-p-element">p</a></code> element that
7428: 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
7429: <a href="#syntax-start-tag" title="syntax-start-tag">start tag</a> would imply the end
7430: tag for the <code><a href="semantics.html#the-p-element">p</a></code>).</p>
7431:
7432:
7433: <h3 id="parsing-html-fragments"><span class="secno">9.5 </span>Parsing HTML fragments</h3>
7434:
7435: <p>The following steps form the <dfn id="html-fragment-parsing-algorithm">HTML fragment parsing
7436: algorithm</dfn>. The algorithm optionally takes as input an
7437: <code>Element</code> node, referred to as the <var title="">context</var> element, which gives the context for the
7438: parser, as well as <var title="">input</var>, a string to parse, and
7439: returns a list of zero or more nodes.</p>
7440:
7441: <p class="note">Parts marked <dfn id="fragment-case">fragment case</dfn> in algorithms
7442: in the parser section are parts that only occur if the parser was
7443: created for the purposes of this algorithm (and with a <var title="">context</var> element). The algorithms have been annotated
7444: with such markings for informational purposes only; such markings
7445: have no normative weight. If it is possible for a condition
7446: described as a <a href="#fragment-case">fragment case</a> to occur even when the
7447: parser wasn't created for the purposes of handling this algorithm,
7448: then that is an error in the specification.</p>
7449:
7450: <ol><li>
7451:
7452: <p>Create a new <code>Document</code> node, and mark it as being
7453: an <a href="dom.html#html-documents" title="HTML documents">HTML document</a>.</p>
7454:
7455: </li>
7456:
7457: <li>
7458:
7459: <p>If there is a <var title="">context</var> element, and the
7460: <code>Document</code> of the <var title="">context</var> element
7461: is in <a href="dom.html#quirks-mode">quirks mode</a>, then let the <code>Document</code>
7462: 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
7463: the <var title="">context</var> element is in <a href="dom.html#limited-quirks-mode">limited quirks
7464: mode</a>, then let the <code>Document</code> be in
7465: <a href="dom.html#limited-quirks-mode">limited quirks mode</a>. Otherwise, leave the
7466: <code>Document</code> in <a href="dom.html#no-quirks-mode">no quirks mode</a>.</p>
7467:
7468: </li>
7469:
7470: <li>
7471:
7472: <p>Create a new <a href="#html-parser">HTML parser</a>, and associate it with
7473: the just created <code>Document</code> node.</p>
7474:
7475: </li>
7476:
7477: <li>
7478:
7479: <p>If there is a <var title="">context</var> element, run these
7480: substeps:</p>
7481:
7482: <ol><li>
7483:
7484: <p>Set the <a href="#html-parser">HTML parser</a>'s <a href="#tokenization">tokenization</a>
7485: stage's <a href="#content-model-flag">content model flag</a> according to the <var title="">context</var> element, as follows:</p>
7486:
1.159 mike 7487: <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 7488: element</dt>
7489:
7490: <dd>Set the <a href="#content-model-flag">content model flag</a> to
7491: the RCDATA state.</dd>
7492:
7493:
7494: <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 7495: <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 7496: <code><a href="obsolete.html#noframes">noframes</a></code> element</dt>
1.1 mike 7497:
7498: <dd>Set the <a href="#content-model-flag">content model flag</a> to
1.91 mike 7499: the RAWTEXT state.</dd>
1.1 mike 7500:
7501:
7502: <dt>If it is a <code><a href="semantics.html#the-noscript-element">noscript</a></code> element</dt>
7503:
7504: <dd>If the <a href="#scripting-flag">scripting flag</a> is enabled, set the
1.91 mike 7505: <a href="#content-model-flag">content model flag</a> to the RAWTEXT
1.1 mike 7506: state. Otherwise, set the <a href="#content-model-flag">content model flag</a> to the
7507: PCDATA state.</dd>
7508:
7509:
1.42 mike 7510: <dt>If it is a <code><a href="obsolete.html#plaintext">plaintext</a></code> element</dt>
1.1 mike 7511:
7512: <dd>Set the <a href="#content-model-flag">content model flag</a> to
7513: PLAINTEXT.</dd>
7514:
7515:
7516: <dt>Otherwise</dt>
7517:
7518: <dd>Leave the <a href="#content-model-flag">content model flag</a> in the PCDATA
7519: state.</dd>
7520:
7521: </dl></li>
7522:
7523: <li>
7524:
1.159 mike 7525: <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 7526: with no attributes.</p>
7527:
7528: </li>
7529:
7530: <li>
7531:
7532: <p>Append the element <var title="">root</var> to the
7533: <code>Document</code> node created above.</p>
7534:
7535: </li>
7536:
7537: <li>
7538:
7539: <p>Set up the parser's <a href="#stack-of-open-elements">stack of open elements</a> so that
7540: it contains just the single element <var title="">root</var>.</p>
7541:
7542: </li>
7543:
7544: <li>
7545:
7546: <p><a href="#reset-the-insertion-mode-appropriately" title="reset the insertion mode appropriately">Reset the
7547: parser's insertion mode appropriately</a>.</p>
7548:
7549: <p class="note">The parser will reference the <var title="">context</var> element as part of that algorithm.</p>
7550:
7551: </li>
7552:
7553: <li>
7554:
7555: <p>Set the parser's <a href="#form-element-pointer"><code>form</code> element pointer</a>
7556: to the nearest node to the <var title="">context</var> element
7557: that is a <code><a href="forms.html#the-form-element">form</a></code> element (going straight up the
7558: ancestor chain, and including the element itself, if it is a
7559: <code><a href="forms.html#the-form-element">form</a></code> element), or, if there is no such
7560: <code><a href="forms.html#the-form-element">form</a></code> element, to null.</p>
7561:
7562: </li>
7563:
7564: </ol></li>
7565:
7566: <li>
7567:
7568: <p>Place into the <a href="#the-input-stream">input stream</a> for the <a href="#html-parser">HTML
7569: parser</a> just created the <var title="">input</var>. The
7570: encoding <a href="#concept-encoding-confidence" title="concept-encoding-confidence">confidence</a> is
7571: <i>irrelevant</i>.</p>
7572:
7573: </li>
7574:
7575: <li>
7576:
7577: <p>Start the parser and let it run until it has consumed all the
7578: characters just inserted into the input stream.</p>
7579:
7580: </li>
7581:
7582: <li>
7583:
7584: <p>If there is a <var title="">context</var> element, return the
7585: child nodes of <var title="">root</var>, in <a href="infrastructure.html#tree-order">tree
7586: order</a>.</p>
7587:
7588: <p>Otherwise, return the children of the <code>Document</code>
7589: object, in <a href="infrastructure.html#tree-order">tree order</a>.</p>
7590:
7591: </li>
7592:
1.123 mike 7593: </ol></div></body></html>
Webmaster