158 |
no effect in HTML.</p> |
no effect in HTML.</p> |
159 |
</div> |
</div> |
160 |
|
|
161 |
|
|
162 |
|
<div class="section tokenize-error" id="pio"><h3>Processing instruction |
163 |
|
(<code><?<var>...</var>?></code>) cannot be used.</h3> |
164 |
|
<p>Processing instructions (<code><?<var>...</var>?></code>), |
165 |
|
including XML declaration (<code><?xml <var>...</var>?></code>) |
166 |
|
and XML style sheet <abbr title="processing instruction">PI</abbr> |
167 |
|
(<code><xml-stylesheet <var>...</var>?></code>), are not allowed |
168 |
|
in the HTML syntax. The document is non-conforming.</p> |
169 |
|
|
170 |
|
<p>If it is necessary to embed a processing instruction |
171 |
|
in the HTML document, you must use the XML syntax instead.</p> |
172 |
|
|
173 |
|
<p>In the HTML syntax, XML declaration is not necessary.</p> |
174 |
|
|
175 |
|
<p>Instead of XML style sheet, |
176 |
|
<abbr title="processing instruction">PI</abbr>s, you must |
177 |
|
use the HTML <code>link</code> element whose <code>rel</code> |
178 |
|
attribute is set to <code>stylesheet</code> (or <code>alternate |
179 |
|
stylesheet</code> for an aleternate style sheet).</p> |
180 |
|
|
181 |
|
<p>Web browsers will parse processing instructions as bogus |
182 |
|
comments. Some legacy Web browsers, such as IE:mac and |
183 |
|
some mobile browsers, will display processing instructions |
184 |
|
as string.</p> |
185 |
|
</div> |
186 |
|
|
187 |
</section> |
</section> |
188 |
|
|
189 |
<section id="html5-parse-errors"> |
<section id="html5-parse-errors"> |
206 |
and comments can be inserted before the <code>DOCTYPE</code>.</p> |
and comments can be inserted before the <code>DOCTYPE</code>.</p> |
207 |
</div> |
</div> |
208 |
|
|
209 |
|
<div class="section parse-error" id="in-a:a"><h3>Anchor cannot be nested.</h3> |
210 |
|
<p>HTML <code>a</code> elements cannot be nested. |
211 |
|
The document is non-conforming.</p> |
212 |
|
|
213 |
|
<p>In the HTML syntax, a start tag of the <code>a</code> |
214 |
|
implies the end tag of any opening <code>a</code> element.</p> |
215 |
|
</div> |
216 |
|
|
217 |
<div class="section parse-error" id="in-body"><h3>Tag <code><<var>$0</var>></code> |
<div class="section parse-error" id="in-body"><h3>Tag <code><<var>$0</var>></code> |
218 |
is not allowed in <code>body</code>.</h3> |
is not allowed in <code>body</code>.</h3> |
219 |
<p>The start or end tag of an element, which |
<p>The start or end tag of an element, which |
546 |
<section id="uri-errors"> |
<section id="uri-errors"> |
547 |
<h2>URI (or IRI) Errors</h2> |
<h2>URI (or IRI) Errors</h2> |
548 |
|
|
549 |
<div class="section must" id="m:URI::syntax-error"><h3>This string is not an IRI syntactically.</h3></div> |
<div class="section must" id="m:URI::syntax-error"><h3>This string is syntactically not an IRI.</h3></div> |
550 |
|
|
551 |
</section> |
</section> |
552 |
|
|
570 |
|
|
571 |
<div class="section should" id="s:URI::lowercase-hexadecimal-digit"><h3>Hexadecimal digit in percent-encoding |
<div class="section should" id="s:URI::lowercase-hexadecimal-digit"><h3>Hexadecimal digit in percent-encoding |
572 |
should be in lowercase.</h3> |
should be in lowercase.</h3> |
573 |
<p>Hexadecimal digit in percent-encoding string in the IRI |
<p>The hexadecimal digit in percent-encoding string in the IRI |
574 |
is in lowercase. Though the IRI <em>is</em> conforming, |
is in lowercase. Though the IRI <em>is</em> conforming, |
575 |
it should be in uppercase.</p> |
it should be in uppercase.</p> |
576 |
</div> |
</div> |