[html5] r8105 - [e] (0) Cleanup Affected topics: DOM APIs, HTML, HTML Syntax and Parsing
whatwg at whatwg.org
whatwg at whatwg.org
Wed Jul 31 12:11:26 PDT 2013
Author: ianh
Date: 2013-07-31 12:11:24 -0700 (Wed, 31 Jul 2013)
New Revision: 8105
Modified:
complete.html
index
source
Log:
[e] (0) Cleanup
Affected topics: DOM APIs, HTML, HTML Syntax and Parsing
Modified: complete.html
===================================================================
--- complete.html 2013-07-30 21:45:54 UTC (rev 8104)
+++ complete.html 2013-07-31 19:11:24 UTC (rev 8105)
@@ -256,7 +256,7 @@
<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 30 July 2013</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 31 July 2013</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -9822,12 +9822,13 @@
elements">HTML element</a>) is either '<dfn id=concept-ltr title=concept-ltr>ltr</dfn>' or '<dfn id=concept-rtl title=concept-rtl>rtl</dfn>', and is determined as per the first appropriate set of steps from
the following list:</p>
- <dl class=switch><!--CLEANUP--><dt>If the element's <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-ltr-state title=attr-dir-ltr-state>ltr</a> state</dt>
+ <dl class=switch><dt>If the element's <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-ltr-state title=attr-dir-ltr-state>ltr</a> state</dt>
<dt>If the element is a <a href=#root-element>root element</a> and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code>
attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
- <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
+ <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code>
+ attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
<dd><p><a href=#the-directionality>The directionality</a> of the element is '<a href=#concept-ltr title=concept-ltr>ltr</a>'.</dd>
@@ -9836,7 +9837,10 @@
<dd><p><a href=#the-directionality>The directionality</a> of the element is '<a href=#concept-rtl title=concept-rtl>rtl</a>'.</dd>
- <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-text>Text</a>, <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-search>Search</a>, <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a>, <a href="#url-state-(type=url)" title=attr-input-type-url>URL</a>, or <a href="#e-mail-state-(type=email)" title=attr-input-type-email>E-mail</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-auto-state title=attr-dir-auto-state>auto</a> state</dt>
+ <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-text>Text</a>, <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-search>Search</a>,
+ <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a>, <a href="#url-state-(type=url)" title=attr-input-type-url>URL</a>,
+ or <a href="#e-mail-state-(type=email)" title=attr-input-type-email>E-mail</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-auto-state title=attr-dir-auto-state>auto</a>
+ state</dt>
<dt>If the element is a <code><a href=#the-textarea-element>textarea</a></code> element and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code>
attribute is in the <a href=#attr-dir-auto-state title=attr-dir-auto-state>auto</a> state</dt>
@@ -9846,8 +9850,7 @@
<p>If the element's <a href=#concept-fe-value title=concept-fe-value>value</a> contains a character of
bidirectional character type AL or R, and there is no character of bidirectional character type
L anywhere before it in the element's <a href=#concept-fe-value title=concept-fe-value>value</a>, then
- <a href=#the-directionality>the directionality</a> of the element is '<a href=#concept-rtl title=concept-rtl>rtl</a>'.
- <a href=#refsBIDI>[BIDI]</a></p>
+ <a href=#the-directionality>the directionality</a> of the element is '<a href=#concept-rtl title=concept-rtl>rtl</a>'. <a href=#refsBIDI>[BIDI]</a></p>
<p>Otherwise, if the element's <a href=#concept-fe-value title=concept-fe-value>value</a> is not the empty
string, or if the element is a <a href=#root-element>root element</a>, <a href=#the-directionality>the directionality</a> of the
@@ -9939,7 +9942,8 @@
<dd>The <a href=#directionality-of-the-attribute>directionality of the attribute</a> is the same as <a href=#the-directionality title="the
directionality">the element's directionality</a>.</dd>
- </dl><p>The following attributes are <dfn id=directionality-capable-attribute title="directionality-capable attribute">directionality-capable attributes</dfn>:</p>
+ </dl><p>The following attributes are <dfn id=directionality-capable-attribute title="directionality-capable
+ attribute">directionality-capable attributes</dfn>:</p>
<ul class=brief><li><code title=attr-th-abbr><a href=#attr-th-abbr>abbr</a></code> on <code><a href=#the-th-element>th</a></code> elements</li>
<li><code title="">alt</code> on <code title=attr-area-alt><a href=#attr-area-alt>area</a></code>,
@@ -10348,11 +10352,12 @@
<h4 id=content-models><span class=secno>3.2.5 </span><dfn>Content models</dfn></h4>
<p>Each element defined in this specification has a content model: a description of the element's
- expected <a href=#concept-html-contents title=concept-html-contents>contents</a>. An <a href=#html-elements title="HTML elements">HTML element</a> must have contents that
- match the requirements described in the element's content model. The <dfn id=concept-html-contents title=concept-html-contents>contents</dfn> of an element are
- its children in the DOM, except for <code><a href=#the-template-element>template</a></code> elements, where the children are those
- in the <a href=#template-contents>template contents</a> (a separate <code><a href=#documentfragment>DocumentFragment</a></code> assigned to the
- element when the element is created).</p>
+ expected <a href=#concept-html-contents title=concept-html-contents>contents</a>. An <a href=#html-elements title="HTML elements">HTML
+ element</a> must have contents that match the requirements described in the element's content
+ model. The <dfn id=concept-html-contents title=concept-html-contents>contents</dfn> of an element are its children in the
+ DOM, except for <code><a href=#the-template-element>template</a></code> elements, where the children are those in the <a href=#template-contents>template
+ contents</a> (a separate <code><a href=#documentfragment>DocumentFragment</a></code> assigned to the element when the element
+ is created).</p>
<p>The <a href=#space-character title="space character">space characters</a> are always allowed between elements.
User agents represent these characters between elements in the source markup as <code><a href=#text>Text</a></code>
@@ -12229,7 +12234,6 @@
<h4 id=document.writeln()><span class=secno>3.4.4 </span><code title=dom-document-writeln><a href=#dom-document-writeln>document.writeln()</a></code></h4>
-<!--CLEANUP-->
<dl class=domintro><dt><var title="">document</var> . <code title=dom-document-writeln><a href=#dom-document-writeln>writeln</a></code>(<var title="">text</var>...)</dt>
<dd>
@@ -12396,7 +12400,6 @@
<h4 id=the-title-element><span class=secno>4.2.2 </span>The <dfn><code>title</code></dfn> element</h4>
-<!--CLEANUP-->
<dl class=element><dt><a href=#element-dfn-categories title=element-dfn-categories>Categories</a>:</dt>
<dd><a href=#metadata-content>Metadata content</a>.</dd>
@@ -12414,16 +12417,13 @@
attribute DOMString <a href=#dom-title-text title=dom-title-text>text</a>;
};</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-title-element>title</a></code> element <a href=#represents>represents</a> the
- document's title or name. Authors should use titles that identify
- their documents even when they are used out of context, for example
- in a user's history or bookmarks, or in search results. The
- document's title is often different from its first heading, since the
- first heading does not have to stand alone when taken out of
- context.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-title-element>title</a></code> element <a href=#represents>represents</a> the document's title or name. Authors
+ should use titles that identify their documents even when they are used out of context, for
+ example in a user's history or bookmarks, or in search results. The document's title is often
+ different from its first heading, since the first heading does not have to stand alone when taken
+ out of context.</p>
- <p>There must be no more than one <code><a href=#the-title-element>title</a></code> element per
- document.</p>
+ <p>There must be no more than one <code><a href=#the-title-element>title</a></code> element per document.</p>
<p>The <code><a href=#the-title-element>title</a></code> element must not be empty.</p>
@@ -12436,30 +12436,27 @@
<dd>
- <p>Returns the contents of the element, ignoring child nodes that
- aren't <code><a href=#text>Text</a></code> nodes.</p>
+ <p>Returns the contents of the element, ignoring child nodes that aren't <code><a href=#text>Text</a></code>
+ nodes.</p>
- <p>Can be set, to replace the element's children with the given
- value.</p>
+ <p>Can be set, to replace the element's children with the given value.</p>
</dd>
</dl><div class=impl>
<p>The IDL attribute <dfn id=dom-title-text title=dom-title-text><code>text</code></dfn> must return a
- concatenation of the contents of all the <code><a href=#text>Text</a></code> nodes
- that are children of the <code><a href=#the-title-element>title</a></code> element (ignoring any
- other nodes such as comments or elements), in tree order. On
- setting, it must act the same way as the <code><a href=#textcontent>textContent</a></code>
- IDL attribute.</p>
+ concatenation of the contents of all the <code><a href=#text>Text</a></code> nodes that are children of the
+ <code><a href=#the-title-element>title</a></code> element (ignoring any other nodes such as comments or elements), in tree order.
+ On setting, it must act the same way as the <code><a href=#textcontent>textContent</a></code> IDL attribute.</p>
</div>
<!--TOPIC:HTML-->
<div class=example>
- <p>Here are some examples of appropriate titles, contrasted with
- the top-level headings that might be used on those same pages.</p>
+ <p>Here are some examples of appropriate titles, contrasted with the top-level headings that
+ might be used on those same pages.</p>
<pre> <title>Introduction to The Mating Rituals of Bees</title>
...
@@ -12467,10 +12464,9 @@
<p>This companion guide to the highly successful
<cite>Introduction to Medieval Bee-Keeping</cite> book is...</pre>
- <p>The next page might be a part of the same site. Note how the
- title describes the subject matter unambiguously, while the first
- heading assumes the reader knows what the context is and therefore
- won't wonder if the dances are Salsa or Waltz:</p>
+ <p>The next page might be a part of the same site. Note how the title describes the subject
+ matter unambiguously, while the first heading assumes the reader knows what the context is and
+ therefore won't wonder if the dances are Salsa or Waltz:</p>
<pre> <title>Dances used during bee mating rituals</title>
...
@@ -12482,12 +12478,10 @@
<div class=impl>
- <p>User agents should use the document's title when referring to the
- document in their user interface. When the contents of a
- <code><a href=#the-title-element>title</a></code> element are used in this way, <a href=#the-directionality>the
- directionality</a> of that <code><a href=#the-title-element>title</a></code> element should be
- used to set the directionality of the document's title in the user
- interface.</p>
+ <p>User agents should use the document's title when referring to the document in their user
+ interface. When the contents of a <code><a href=#the-title-element>title</a></code> element are used in this way, <a href=#the-directionality>the
+ directionality</a> of that <code><a href=#the-title-element>title</a></code> element should be used to set the directionality
+ of the document's title in the user interface.</p>
</div>
@@ -12513,48 +12507,41 @@
attribute DOMString <a href=#dom-base-target title=dom-base-target>target</a>;
};</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-base-element>base</a></code> element allows authors to specify the
- <a href=#document-base-url>document base URL</a> for the purposes of <a href=#resolve-a-url title="resolve a url">resolving relative URLs</a>, and the name
- of the default <a href=#browsing-context>browsing context</a> for the purposes of
- <a href=#following-hyperlinks>following hyperlinks</a>. The element does not <a href=#represents title=represents>represent</a> any content beyond this
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-base-element>base</a></code> element allows authors to specify the <a href=#document-base-url>document base URL</a> for
+ the purposes of <a href=#resolve-a-url title="resolve a url">resolving relative URLs</a>, and the name of the
+ default <a href=#browsing-context>browsing context</a> for the purposes of <a href=#following-hyperlinks>following hyperlinks</a>. The
+ element does not <a href=#represents title=represents>represent</a> any content beyond this
information.</p>
- <p>There must be no more than one <code><a href=#the-base-element>base</a></code> element per
- document.</p>
+ <p>There must be no more than one <code><a href=#the-base-element>base</a></code> element per document.</p>
- <p>A <code><a href=#the-base-element>base</a></code> element must have either an <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute, a <code title=attr-base-target><a href=#attr-base-target>target</a></code> attribute, or both.</p>
+ <p>A <code><a href=#the-base-element>base</a></code> element must have either an <code title=attr-base-href><a href=#attr-base-href>href</a></code>
+ attribute, a <code title=attr-base-target><a href=#attr-base-target>target</a></code> attribute, or both.</p>
- <p>The <dfn id=attr-base-href title=attr-base-href><code>href</code></dfn> content
- attribute, if specified, must contain a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially
- surrounded by spaces</a>.</p>
+ <p>The <dfn id=attr-base-href title=attr-base-href><code>href</code></dfn> content attribute, if specified, must
+ contain a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially surrounded by spaces</a>.</p>
- <p>A <code><a href=#the-base-element>base</a></code> element, if it has an <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute, must come before any
- other elements in the tree that have attributes defined as taking
- <a href=#url title=URL>URLs</a>, except the <code><a href=#the-html-element>html</a></code> element
- (its <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute
- isn't affected by <code><a href=#the-base-element>base</a></code> elements).</p>
+ <p>A <code><a href=#the-base-element>base</a></code> element, if it has an <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute,
+ must come before any other elements in the tree that have attributes defined as taking <a href=#url title=URL>URLs</a>, except the <code><a href=#the-html-element>html</a></code> element (its <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute isn't affected by <code><a href=#the-base-element>base</a></code>
+ elements).</p>
<div class=impl>
- <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements
- with <code title=attr-base-href><a href=#attr-base-href>href</a></code> attributes, all but the
- first are ignored.</p>
+ <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements with <code title=attr-base-href><a href=#attr-base-href>href</a></code> attributes, all but the first are ignored.</p>
</div>
- <p>The <dfn id=attr-base-target title=attr-base-target><code>target</code></dfn>
- attribute, if specified, must contain a <a href=#valid-browsing-context-name-or-keyword>valid browsing context
- name or keyword</a>, which specifies which <a href=#browsing-context>browsing
- context</a> is to be used as the default when <a href=#hyperlink title=hyperlink>hyperlinks</a> and <a href=#the-form-element title=form>forms</a> in the <code><a href=#document>Document</a></code> cause <a href=#navigate title=navigate>navigation</a>.</p>
+ <p>The <dfn id=attr-base-target title=attr-base-target><code>target</code></dfn> attribute, if specified, must
+ contain a <a href=#valid-browsing-context-name-or-keyword>valid browsing context name or keyword</a>, which specifies which
+ <a href=#browsing-context>browsing context</a> is to be used as the default when <a href=#hyperlink title=hyperlink>hyperlinks</a> and <a href=#the-form-element title=form>forms</a> in the
+ <code><a href=#document>Document</a></code> cause <a href=#navigate title=navigate>navigation</a>.</p>
- <p>A <code><a href=#the-base-element>base</a></code> element, if it has a <code title=attr-base-target><a href=#attr-base-target>target</a></code> attribute, must come before
- any elements in the tree that represent <a href=#hyperlink title=hyperlink>hyperlinks</a>.</p>
+ <p>A <code><a href=#the-base-element>base</a></code> element, if it has a <code title=attr-base-target><a href=#attr-base-target>target</a></code>
+ attribute, must come before any elements in the tree that represent <a href=#hyperlink title=hyperlink>hyperlinks</a>.</p>
<div class=impl>
- <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements
- with <code title=attr-base-target><a href=#attr-base-target>target</a></code> attributes, all but
- the first are ignored.</p>
+ <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements with <code title=attr-base-target><a href=#attr-base-target>target</a></code> attributes, all but the first are ignored.</p>
<p>A <code><a href=#the-base-element>base</a></code> element that is the first <code><a href=#the-base-element>base</a></code> element with an <code title=attr-base-href><a href=#attr-base-href>href</a></code> content attribute in a particular <code><a href=#document>Document</a></code> has a
<dfn id=frozen-base-url>frozen base URL</dfn>. The <a href=#frozen-base-url>frozen base URL</a> must be <a href=#set-the-frozen-base-url title="set the frozen
@@ -12575,43 +12562,36 @@
<a href=#frozen-base-url>frozen base URL</a> to the <a href=#resulting-absolute-url>resulting absolute URL</a>, otherwise, set the
<a href=#frozen-base-url>frozen base URL</a> to the <a href=#fallback-base-url>fallback base URL</a>.</p>
- <p>The <dfn id=dom-base-href title=dom-base-href><code>href</code></dfn> IDL
- attribute, on getting, must return the result of running the
- following algorithm:
+ <p>The <dfn id=dom-base-href title=dom-base-href><code>href</code></dfn> IDL attribute, on getting, must return
+ the result of running the following algorithm:
- <ol><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1715 --><li><p>If the <code><a href=#the-base-element>base</a></code> element has no <code title=attr-base-href><a href=#attr-base-href>href</a></code> content attribute, then return
- the <a href=#document-base-url>document base URL</a> and abort these steps.</li>
+ <ol><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1715 --><li><p>If the <code><a href=#the-base-element>base</a></code> element has no <code title=attr-base-href><a href=#attr-base-href>href</a></code> content
+ attribute, then return the <a href=#document-base-url>document base URL</a> and abort these steps.</li>
- <li><p>Let <var title="">fallback base url</var> be the
- <code><a href=#document>Document</a></code>'s <a href=#fallback-base-url>fallback base URL</a>.</li>
+ <li><p>Let <var title="">fallback base url</var> be the <code><a href=#document>Document</a></code>'s <a href=#fallback-base-url>fallback
+ base URL</a>.</li>
- <li><p>Let <var title="">url</var> be the value of the <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute of the
- <code><a href=#the-base-element>base</a></code> element.</li>
+ <li><p>Let <var title="">url</var> be the value of the <code title=attr-base-href><a href=#attr-base-href>href</a></code>
+ attribute of the <code><a href=#the-base-element>base</a></code> element.</li>
- <li><p><a href=#resolve-a-url title="resolve a URL">Resolve</a> <var title="">url</var> relative to <var title="">fallback base
- url</var> (thus, the <code><a href=#the-base-element>base</a></code> <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute isn't affected by
- <code title=attr-xml-base><a href=#the-xml:base-attribute-(xml-only)>xml:base</a></code> attributes or
- <code><a href=#the-base-element>base</a></code> elements).</li>
+ <li><p><a href=#resolve-a-url title="resolve a URL">Resolve</a> <var title="">url</var> relative to <var title="">fallback base url</var> (thus, the <code><a href=#the-base-element>base</a></code> <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute isn't affected by <code title=attr-xml-base><a href=#the-xml:base-attribute-(xml-only)>xml:base</a></code> attributes or <code><a href=#the-base-element>base</a></code> elements).</li>
- <li><p>If the previous step was successful, return the resulting
- <a href=#absolute-url>absolute URL</a> and abort these steps.</li>
+ <li><p>If the previous step was successful, return the resulting <a href=#absolute-url>absolute URL</a> and
+ abort these steps.</li>
<li><p>Otherwise, return the empty string.</li>
- </ol><p>The <code title=dom-base-href><a href=#dom-base-href>href</a></code> IDL attribute, on
- setting, must set the <code title=attr-base-href><a href=#attr-base-href>href</a></code>
- content attribute to the given new value.</p>
+ </ol><p>The <code title=dom-base-href><a href=#dom-base-href>href</a></code> IDL attribute, on setting, must set the <code title=attr-base-href><a href=#attr-base-href>href</a></code> content attribute to the given new value.</p>
- <p>The <dfn id=dom-base-target title=dom-base-target><code>target</code></dfn> IDL
- attribute must <a href=#reflect>reflect</a> the content attribute of the
- same name.</p>
+ <p>The <dfn id=dom-base-target title=dom-base-target><code>target</code></dfn> IDL attribute must
+ <a href=#reflect>reflect</a> the content attribute of the same name.</p>
</div>
<div class=example>
- <p>In this example, a <code><a href=#the-base-element>base</a></code> element is used to set the
- <a href=#document-base-url>document base URL</a>:</p>
+ <p>In this example, a <code><a href=#the-base-element>base</a></code> element is used to set the <a href=#document-base-url>document base
+ URL</a>:</p>
<pre><!DOCTYPE html>
<html>
@@ -13393,49 +13373,40 @@
These numbers are low; further study is required to establish what
people expect to have work and what is necessary.
--><div class=impl>
-<!--CLEANUP-->
- <p>When a <code><a href=#the-meta-element>meta</a></code> element is <a href=#insert-an-element-into-a-document title="insert an
- element into a document">inserted into the document</a>, if its
- <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute is
- present and represents one of the above states, then the user agent
- must run the algorithm appropriate for that state, as described in
- the following list:</p>
+ <p>When a <code><a href=#the-meta-element>meta</a></code> element is <a href=#insert-an-element-into-a-document title="insert an element into a document">inserted
+ into the document</a>, if its <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute is
+ present and represents one of the above states, then the user agent must run the algorithm
+ appropriate for that state, as described in the following list:</p>
+
</div>
<dl><dt class=impl><dfn id=attr-meta-http-equiv-content-language title=attr-meta-http-equiv-content-language>Content language state</dfn> (<code title="">http-equiv="content-language"</code>)
<dd class=impl>
- <p class=note>This feature is non-conforming. Authors are
- encouraged to use the <code title=attr-lang><a href=#attr-lang>lang</a></code>
- attribute instead.</p>
+ <p class=note>This feature is non-conforming. Authors are encouraged to use the <code title=attr-lang><a href=#attr-lang>lang</a></code> attribute instead.</p>
- <p>This pragma sets the <dfn id=pragma-set-default-language>pragma-set default language</dfn>.
- Until such a pragma is successfully processed, there is no
- <a href=#pragma-set-default-language>pragma-set default language</a>.</p>
+ <p>This pragma sets the <dfn id=pragma-set-default-language>pragma-set default language</dfn>. Until such a pragma is
+ successfully processed, there is no <a href=#pragma-set-default-language>pragma-set default language</a>.</p>
<!-- http://www.hixie.ch/tests/adhoc/html/meta/content-language/ -->
- <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute, then abort these
- steps.</li>
+ <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code>
+ attribute, then abort these steps.</li>
<li><p>If the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute contains a
- U+002C COMMA character (,) then abort these steps.</li><!--
- if you remove this, un-comment-out the corresponding bits in the
- step below. -->
+ U+002C COMMA character (,) then abort these steps.</li><!-- if you remove this,
+ un-comment-out the corresponding bits in the step below. -->
- <li><p>Let <var title="">input</var> be the value of the
- element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code>
- attribute.</li>
+ <li><p>Let <var title="">input</var> be the value of the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute.</li>
- <li><p>Let <var title="">position</var> point at the first
- character of <var title="">input</var>.</li>
+ <li><p>Let <var title="">position</var> point at the first character of <var title="">input</var>.</li>
<li><p><a href=#skip-whitespace>Skip whitespace</a>.</li>
- <li><p><a href=#collect-a-sequence-of-characters>Collect a sequence of characters</a> that are not<!--neither--> <a href=#space-character title="space character">space characters</a><!-- nor a U+002C
- COMMA character (,)-->.</li>
+ <li><p><a href=#collect-a-sequence-of-characters>Collect a sequence of characters</a> that are not<!--neither--> <a href=#space-character title="space character">space characters</a><!-- nor a U+002C COMMA character
+ (,)-->.</li>
<li><p>Let <var title="">candidate</var> be the string that resulted from the previous
step.</li>
@@ -13444,8 +13415,8 @@
<li><p>Set the <a href=#pragma-set-default-language>pragma-set default language</a> to <var title="">candidate</var>.</li>
- </ol><p class=note>This pragma is not exactly equivalent to the HTTP
- <code>Content-Language</code> header. <a href=#refsHTTP>[HTTP]</a></p>
+ </ol><p class=note>This pragma is not exactly equivalent to the HTTP <code>Content-Language</code>
+ header. <a href=#refsHTTP>[HTTP]</a></p>
</dd>
@@ -13479,17 +13450,15 @@
<dd>
- <p>This pragma sets the name of the default <a href=#alternative-style-sheet-sets title="alternative style sheet sets">alternative style sheet
- set</a>.</p>
+ <p>This pragma sets the name of the default <a href=#alternative-style-sheet-sets title="alternative style sheet
+ sets">alternative style sheet set</a>.</p>
<div class=impl>
- <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute, or if that
- attribute's value is the empty string, then abort these
- steps.</li>
+ <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code>
+ attribute, or if that attribute's value is the empty string, then abort these steps.</li>
- <li><p>Set the <a href=#preferred-style-sheet-set>preferred style sheet set</a> to the
- value of the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute. <a href=#refsCSSOM>[CSSOM]</a></li>
+ <li><p>Set the <a href=#preferred-style-sheet-set>preferred style sheet set</a> to the value of the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute. <a href=#refsCSSOM>[CSSOM]</a></li>
</ol></div>
@@ -13608,8 +13577,8 @@
</ul></li>
<li><p>Provide the user with an interface that, when selected, <a href=#navigate title=navigate>navigates</a><!--DONAV meta refresh--> a <a href=#browsing-context>browsing context</a> to
- <var title="">url</var>, with the <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a> as the <a href=#source-browsing-context>source browsing
- context</a>.</li>
+ <var title="">url</var>, with the <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a> as
+ the <a href=#source-browsing-context>source browsing context</a>.</li>
<li><p>Do nothing.</li>
@@ -13684,56 +13653,46 @@
<h5 id=other-pragma-directives><span class=secno>4.2.5.4 </span>Other pragma directives</h5>
- <p><dfn id=concept-http-equiv-extensions title=concept-http-equiv-extensions>Extensions to the
- predefined set of pragma directives</dfn> may, under certain
- conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki
- PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
+ <p><dfn id=concept-http-equiv-extensions title=concept-http-equiv-extensions>Extensions to the predefined set of pragma
+ directives</dfn> may, under certain conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
- <p>Such extensions must use a name that is identical to an HTTP
- header registered in the Permanent Message Header Field Registry,
- and must have behavior identical to that described for the HTTP
+ <p>Such extensions must use a name that is identical to an HTTP header registered in the Permanent
+ Message Header Field Registry, and must have behavior identical to that described for the HTTP
header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
- <p>Pragma directives corresponding to headers describing metadata,
- or not requiring specific user agent processing, must not be
- registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma
- directives corresponding to headers that affect the HTTP processing
- model (e.g. caching) must not be registered, as they would result in
- HTTP-level behavior being different for user agents that implement
- HTML than for user agents that do not.</p>
+ <p>Pragma directives corresponding to headers describing metadata, or not requiring specific user
+ agent processing, must not be registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma directives corresponding to headers
+ that affect the HTTP processing model (e.g. caching) must not be registered, as they would result
+ in HTTP-level behavior being different for user agents that implement HTML than for user agents
+ that do not.</p>
- <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
- any time to add a pragma directive satisfying these conditions. Such
- registrations must specify the following information:</p>
+ <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at any time to add a pragma
+ directive satisfying these conditions. Such registrations must specify the following
+ information:</p>
<dl><dt>Keyword</dt>
- <dd><p>The actual name being defined. The name must match a
- previously-registered HTTP name with the same
- requirements.</dd>
+ <dd><p>The actual name being defined. The name must match a previously-registered HTTP name with
+ the same requirements.</dd>
<dt>Brief description</dt>
- <dd><p>A short non-normative description of the purpose of the
- pragma directive.</dd>
+ <dd><p>A short non-normative description of the purpose of the pragma directive.</dd>
<dt>Specification</dt>
- <dd>A link to the specification defining the corresponding HTTP
- header.</dd>
+ <dd>A link to the specification defining the corresponding HTTP header.</dd>
</dl><div class=impl>
- <p>Conformance checkers must use the information given on the WHATWG
- Wiki PragmaExtensions page to establish if a value is allowed or
- not: values defined in this specification or listed on the
- aforementioned page must be accepted, whereas values not listed in
- either this specification or on the aforementioned page must be
- rejected as invalid. Conformance checkers may cache this information
- (e.g. for performance reasons or to avoid the use of unreliable
- network connectivity).</p>
+ <p>Conformance checkers must use the information given on the WHATWG Wiki PragmaExtensions page to
+ establish if a value is allowed or not: values defined in this specification or listed on the
+ aforementioned page must be accepted, whereas values not listed in either this specification or on
+ the aforementioned page must be rejected as invalid. Conformance checkers may cache this
+ information (e.g. for performance reasons or to avoid the use of unreliable network
+ connectivity).</p>
</div>
@@ -13882,26 +13841,23 @@
};
<a href=#htmlstyleelement>HTMLStyleElement</a> implements <a href=#linkstyle>LinkStyle</a>;</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-style-element>style</a></code> element allows authors to embed style
- information in their documents. The <code><a href=#the-style-element>style</a></code> element is
- one of several inputs to the <a href=#styling>styling processing
- model</a>. The element does not <a href=#represents title=represents>represent</a> content for the user.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-style-element>style</a></code> element allows authors to embed style information in their documents.
+ The <code><a href=#the-style-element>style</a></code> element is one of several inputs to the <a href=#styling>styling processing
+ model</a>. The element does not <a href=#represents title=represents>represent</a> content for the
+ user.</p>
- <p>The <dfn id=attr-style-type title=attr-style-type><code>type</code></dfn>
- attribute gives the styling language. If the attribute is present,
- its value must be a <a href=#valid-mime-type>valid MIME type</a> that designates a
- styling language. The <code title="">charset</code> parameter must
- not be specified. The default value for the <code title=attr-style-type><a href=#attr-style-type>type</a></code> attribute, which is used if the
- attribute is absent, is "<code title="">text/css</code>". <a href=#refsRFC2318>[RFC2318]</a></p>
+ <p>The <dfn id=attr-style-type title=attr-style-type><code>type</code></dfn> attribute gives the styling language.
+ If the attribute is present, its value must be a <a href=#valid-mime-type>valid MIME type</a> that designates a
+ styling language. The <code title="">charset</code> parameter must not be specified. The default
+ value for the <code title=attr-style-type><a href=#attr-style-type>type</a></code> attribute, which is used if the attribute
+ is absent, is "<code title="">text/css</code>". <a href=#refsRFC2318>[RFC2318]</a></p>
<div class=impl>
- <!-- similar paragraph is also present in the <script> section -->
- <p>When examining types to determine if they support the language,
- user agents must not ignore unknown MIME parameters — types
- with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown
- parameter for the purpose of comparing <a href=#mime-type title="MIME type">MIME
- types</a> here.</p>
+ <!-- similar paragraph is also present in the <script> section --> <p>When examining types to
+ determine if they support the language, user agents must not ignore unknown MIME parameters
+ — types with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown parameter for the purpose of
+ comparing <a href=#mime-type title="MIME type">MIME types</a> here.</p>
</div>
@@ -13927,15 +13883,15 @@
rooted at the <code><a href=#the-style-element>style</a></code> element's parent element, as opposed to the whole
<code><a href=#document>Document</a></code>.</p>
-<!--CLEANUP-->
<p>If the <code title=attr-style-scoped><a href=#attr-style-scoped>scoped</a></code> attribute is present and the element has a
- parent element, then the <code><a href=#the-style-element>style</a></code> element must precede any <a href=#flow-content>flow
- content</a> in its parent element other than <a href=#inter-element-whitespace>inter-element whitespace</a> and other <code><a href=#the-style-element>style</a></code> elements, and the
- parent element's content model must not have a <a href=#transparent>transparent</a> component.</p>
+ parent element, then the <code><a href=#the-style-element>style</a></code> element must precede any <a href=#flow-content>flow content</a> in
+ its parent element other than <a href=#inter-element-whitespace>inter-element whitespace</a> and other <code><a href=#the-style-element>style</a></code>
+ elements, and the parent element's content model must not have a <a href=#transparent>transparent</a>
+ component.</p>
- <p class=note>This implies that scoped <code><a href=#the-style-element>style</a></code> elements
- cannot be children of, e.g., <code><a href=#the-a-element>a</a></code> or <code><a href=#the-ins-element>ins</a></code> elements,
- even when those are used as <a href=#flow-content>flow content</a> containers.</p>
+ <p class=note>This implies that scoped <code><a href=#the-style-element>style</a></code> elements cannot be children of, e.g.,
+ <code><a href=#the-a-element>a</a></code> or <code><a href=#the-ins-element>ins</a></code> elements, even when those are used as <a href=#flow-content>flow content</a>
+ containers.</p>
<p class=note>A <code><a href=#the-style-element>style</a></code> element <em>without</em> a <code title=attr-style-scoped><a href=#attr-style-scoped>scoped</a></code> attribute is restricted to appearing in the
<code><a href=#the-head-element>head</a></code> of the document.</p>
@@ -13964,22 +13920,18 @@
<pre>B b|\\0{0,4}(42|62)(\r\n|[ \t\r\n\f])?
@{G}{L}{O}{B}{A}{L} {return GLOBAL_SYM;}</pre>
- <p>Simple selectors in rule sets prefixed by the <code title="">@global</code> @-rule in scoped CSS resources must be
- processed in the same way as normal rule sets in non-scoped CSS
+ <p>Simple selectors in rule sets prefixed by the <code title="">@global</code> @-rule in scoped
+ CSS resources must be processed in the same way as normal rule sets in non-scoped CSS
resources.</p>
- <p>Simple selectors in scoped CSS resources that are not prefixed by
- an <code title="">@global</code> @-rule must only match the
- <code><a href=#the-style-element>style</a></code> element's parent element (if any), and that
- element's descendants.</p>
+ <p>Simple selectors in scoped CSS resources that are not prefixed by an <code title="">@global</code> @-rule must only match the <code><a href=#the-style-element>style</a></code> element's parent element (if
+ any), and that element's descendants.</p>
- <p>For scoped CSS resources, the effect of other @-rules must be
- scoped to either the scoped sheet and its subresources or to the
- subtree rooted at the <code><a href=#the-style-element>style</a></code> element's parent (if any),
- even if the @-rule in question would ordinarily apply to all style
- sheets that affect the <code><a href=#document>Document</a></code>, or to all nodes in the
- <code><a href=#document>Document</a></code>. Any '@page' rules in scoped CSS resources
- must be ignored.</p>
+ <p>For scoped CSS resources, the effect of other @-rules must be scoped to either the scoped sheet
+ and its subresources or to the subtree rooted at the <code><a href=#the-style-element>style</a></code> element's parent (if any),
+ even if the @-rule in question would ordinarily apply to all style sheets that affect the
+ <code><a href=#document>Document</a></code>, or to all nodes in the <code><a href=#document>Document</a></code>. Any '@page' rules in scoped
+ CSS resources must be ignored.</p>
<p class=example>For example, an '@font-face' rule defined in a scoped style sheet would only
define the font for the purposes of elements in the scoped section; the font would not be used for
@@ -13990,20 +13942,18 @@
<hr></div>
<p id=title-on-style>The <dfn id=attr-style-title title=attr-style-title><code>title</code></dfn> attribute on
- <code><a href=#the-style-element>style</a></code> elements defines <a href=#alternative-style-sheet-sets>alternative style sheet
- sets</a>. If the <code><a href=#the-style-element>style</a></code> element has no <code title=attr-style-title><a href=#attr-style-title>title</a></code> attribute, then it has no
- title; the <code title=attr-title><a href=#attr-title>title</a></code> attribute of
- ancestors does not apply to the <code><a href=#the-style-element>style</a></code> element. <a href=#refsCSSOM>[CSSOM]</a></p>
+ <code><a href=#the-style-element>style</a></code> elements defines <a href=#alternative-style-sheet-sets>alternative style sheet sets</a>. If the
+ <code><a href=#the-style-element>style</a></code> element has no <code title=attr-style-title><a href=#attr-style-title>title</a></code> attribute, then it
+ has no title; the <code title=attr-title><a href=#attr-title>title</a></code> attribute of ancestors does not apply to
+ the <code><a href=#the-style-element>style</a></code> element. <a href=#refsCSSOM>[CSSOM]</a></p>
- <p class=note>The <code title=attr-style-title><a href=#attr-style-title>title</a></code>
- attribute on <code><a href=#the-style-element>style</a></code> elements, like the <code title=attr-link-title><a href=#attr-link-title>title</a></code> attribute on <code><a href=#the-link-element>link</a></code>
+ <p class=note>The <code title=attr-style-title><a href=#attr-style-title>title</a></code> attribute on <code><a href=#the-style-element>style</a></code>
+ elements, like the <code title=attr-link-title><a href=#attr-link-title>title</a></code> attribute on <code><a href=#the-link-element>link</a></code>
elements, differs from the global <code title=attr-title><a href=#attr-title>title</a></code> attribute in that a
- <code><a href=#the-style-element>style</a></code> block without a title does not inherit the title
- of the parent element: it merely has no title.</p>
+ <code><a href=#the-style-element>style</a></code> block without a title does not inherit the title of the parent element: it
+ merely has no title.</p>
- <p>The <code><a href=#textcontent>textContent</a></code> of a <code><a href=#the-style-element>style</a></code> element must
- match the <code title="">style</code> production in the following
- ABNF, the character set for which is Unicode. <a href=#refsABNF>[ABNF]</a></p>
+ <p>The <code><a href=#textcontent>textContent</a></code> of a <code><a href=#the-style-element>style</a></code> element must match the <code title="">style</code> production in the following ABNF, the character set for which is Unicode. <a href=#refsABNF>[ABNF]</a></p>
<pre>style = no-c-start *( c-start no-c-end c-end no-c-start )
no-c-start = < any string that doesn't contain a substring that matches c-start >
@@ -14022,73 +13972,58 @@
<div class=impl>
- <p>All descendant elements must be processed, according to their
- semantics, before the <code><a href=#the-style-element>style</a></code> element itself is
- evaluated. For styling languages that consist of pure text (as
- opposed to XML), user agents must evaluate <code><a href=#the-style-element>style</a></code>
- elements by passing the concatenation of the contents of all the
- <code><a href=#text>Text</a></code> nodes that are children of the
- <code><a href=#the-style-element>style</a></code> element (not any other nodes such as comments or
- elements), in <a href=#tree-order>tree order</a>, to the style system. For
- XML-based styling languages, user agents must pass all the child
- nodes of the <code><a href=#the-style-element>style</a></code> element to the style system.</p>
+ <p>All descendant elements must be processed, according to their semantics, before the
+ <code><a href=#the-style-element>style</a></code> element itself is evaluated. For styling languages that consist of pure text
+ (as opposed to XML), user agents must evaluate <code><a href=#the-style-element>style</a></code> elements by passing the
+ concatenation of the contents of all the <code><a href=#text>Text</a></code> nodes that are children of the
+ <code><a href=#the-style-element>style</a></code> element (not any other nodes such as comments or elements), in <a href=#tree-order>tree
+ order</a>, to the style system. For XML-based styling languages, user agents must pass all the
+ child nodes of the <code><a href=#the-style-element>style</a></code> element to the style system.</p>
- <p>All <a href=#url title=URL>URLs</a> found by the styling language's
- processor must be <a href=#resolve-a-url title="resolve a url">resolved</a>,
- relative to the element (or as defined by the styling language),
- when the processor is invoked.<!-- so dynamic changes to the base
- URL don't affect the CSS --></p>
+ <p>All <a href=#url title=URL>URLs</a> found by the styling language's processor must be <a href=#resolve-a-url title="resolve a url">resolved</a>, relative to the element (or as defined by the styling
+ language), when the processor is invoked.<!-- so dynamic changes to the base URL don't affect the
+ CSS --></p>
<!-- the next few paragraph are similar to text in the <style> section -->
- <p>Once the attempts to obtain the style sheet's <a href=#critical-subresources>critical
- subresources</a>, if any, are complete, or, if the style sheet
- has no <a href=#critical-subresources>critical subresources</a>, once the style sheet has
- been parsed and processed, the user agent must, if the loads were
- successful or there were none, <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-load>load</code> at the <code><a href=#the-style-element>style</a></code> element,
- or, if one of the style sheet's <a href=#critical-subresources>critical subresources</a>
- failed to completely load for any reason (e.g. DNS error, HTTP 404
- response, a connection being prematurely closed, unsupported
- Content-Type), <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> named <code title=event-error>error</code> at the
- <code><a href=#the-style-element>style</a></code> element. Non-network errors in processing the
- style sheet or its subresources (e.g. CSS parse errors, PNG decoding
- errors) are not failures for the purposes of this paragraph.</p>
+ <p>Once the attempts to obtain the style sheet's <a href=#critical-subresources>critical subresources</a>, if any, are
+ complete, or, if the style sheet has no <a href=#critical-subresources>critical subresources</a>, once the style sheet
+ has been parsed and processed, the user agent must, if the loads were successful or there were
+ none, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-load>load</code> at the <code><a href=#the-style-element>style</a></code> element, or, if one of the style sheet's
+ <a href=#critical-subresources>critical subresources</a> failed to completely load for any reason (e.g. DNS error, HTTP
+ 404 response, a connection being prematurely closed, unsupported Content-Type), <a href=#queue-a-task>queue a
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-error>error</code> at
+ the <code><a href=#the-style-element>style</a></code> element. Non-network errors in processing the style sheet or its
+ subresources (e.g. CSS parse errors, PNG decoding errors) are not failures for the purposes of
+ this paragraph.</p>
- <p>The <a href=#task-source>task source</a> for these <a href=#concept-task title=concept-task>tasks</a> is the <a href=#dom-manipulation-task-source>DOM manipulation task
- source</a>.</p>
+ <p>The <a href=#task-source>task source</a> for these <a href=#concept-task title=concept-task>tasks</a> is the <a href=#dom-manipulation-task-source>DOM
+ manipulation task source</a>.</p>
- <p>The element must <a href=#delay-the-load-event>delay the load event</a> of the
- element's document until all the attempts to obtain the style
- sheet's <a href=#critical-subresources>critical subresources</a>, if any, are
- complete.</p>
+ <p>The element must <a href=#delay-the-load-event>delay the load event</a> of the element's document until all the
+ attempts to obtain the style sheet's <a href=#critical-subresources>critical subresources</a>, if any, are complete.</p>
</div>
- <p class=note>This specification does not specify a style system,
- but CSS is expected to be supported by most Web browsers. <a href=#refsCSS>[CSS]</a></p>
+ <p class=note>This specification does not specify a style system, but CSS is expected to be
+ supported by most Web browsers. <a href=#refsCSS>[CSS]</a></p>
<div class=impl>
- <p>The <dfn id=dom-style-media title=dom-style-media><code>media</code></dfn>, <dfn id=dom-style-type title=dom-style-type><code>type</code></dfn> and <dfn id=dom-style-scoped title=dom-style-scoped><code>scoped</code></dfn> IDL attributes
- must <a href=#reflect>reflect</a> the respective content attributes of the
- same name.</p>
+ <p>The <dfn id=dom-style-media title=dom-style-media><code>media</code></dfn>, <dfn id=dom-style-type title=dom-style-type><code>type</code></dfn> and <dfn id=dom-style-scoped title=dom-style-scoped><code>scoped</code></dfn> IDL attributes must <a href=#reflect>reflect</a> the
+ respective content attributes of the same name.</p>
</div>
- <p>The <dfn id=dom-style-disabled title=dom-style-disabled><code>disabled</code></dfn>
- IDL attribute behaves as defined <a href=#dom-linkstyle-disabled title=dom-linkstyle-disabled>for the alternative style sheets
- DOM</a>.</p>
+ <p>The <dfn id=dom-style-disabled title=dom-style-disabled><code>disabled</code></dfn> IDL attribute behaves as
+ defined <a href=#dom-linkstyle-disabled title=dom-linkstyle-disabled>for the alternative style sheets DOM</a>.</p>
- <p>The <code><a href=#linkstyle>LinkStyle</a></code> interface is also implemented by
- this element; the <a href=#styling>styling processing model</a> defines
- how. <a href=#refsCSSOM>[CSSOM]</a></p>
+ <p>The <code><a href=#linkstyle>LinkStyle</a></code> interface is also implemented by this element; the <a href=#styling>styling
+ processing model</a> defines how. <a href=#refsCSSOM>[CSSOM]</a></p>
<div class=example>
- <p>The following document has its stress emphasis styled as bright
- red text rather than italics text, while leaving titles of works
- and Latin words in their default italics. It shows how using
+ <p>The following document has its stress emphasis styled as bright red text rather than italics
+ text, while leaving titles of works and Latin words in their default italics. It shows how using
appropriate elements enables easier restyling of documents.</p>
<pre><!DOCTYPE html>
@@ -14243,24 +14178,25 @@
<p>Scripts allow authors to add interactivity to their documents.</p>
- <p>Authors are encouraged to use declarative alternatives to
- scripting where possible, as declarative mechanisms are often more
- maintainable, and many users disable scripting.</p>
+ <p>Authors are encouraged to use declarative alternatives to scripting where possible, as
+ declarative mechanisms are often more maintainable, and many users disable scripting.</p>
<div class=example>
- <p>For example, instead of using script to show or hide a section
- to show more details, the <code><a href=#the-details-element>details</a></code> element could be
- used.</p>
+
+ <p>For example, instead of using script to show or hide a section to show more details, the
+ <code><a href=#the-details-element>details</a></code> element could be used.</p>
+
</div>
- <p>Authors are also encouraged to make their applications degrade
- gracefully in the absence of scripting support.</p>
+ <p>Authors are also encouraged to make their applications degrade gracefully in the absence of
+ scripting support.</p>
<div class=example>
- <p>For example, if an author provides a link in a table header to
- dynamically resort the table, the link could also be made to
- function without scripts by requesting the sorted table from the
+
+ <p>For example, if an author provides a link in a table header to dynamically resort the table,
+ the link could also be made to function without scripts by requesting the sorted table from the
server.</p>
+
</div>
@@ -15252,40 +15188,31 @@
<p><i>This section is non-normative.</i></p>
- <p>This specification does not define how XSLT interacts with the
- <code><a href=#the-script-element>script</a></code> element. However, in the absence of another
- specification actually defining this, here are some guidelines for
- implementors, based on existing implementations:</p>
+ <p>This specification does not define how XSLT interacts with the <code><a href=#the-script-element>script</a></code> element.
+ However, in the absence of another specification actually defining this, here are some guidelines
+ for implementors, based on existing implementations:</p>
- <ul><li><p>When an XSLT transformation program is triggered by an <code title=""><?xml-stylesheet?></code> processing instruction and
- the browser implements a direct-to-DOM transformation,
- <code><a href=#the-script-element>script</a></code> elements created by the XSLT processor need to
- be marked <a href=#parser-inserted>"parser-inserted"</a> and run in document order
- (modulo scripts marked <code title=attr-script-defer><a href=#attr-script-defer>defer</a></code>
- or <code title=attr-script-async><a href=#attr-script-async>async</a></code>), asynchronously
- while the transformation is occurring.</li>
+ <ul><li><p>When an XSLT transformation program is triggered by an <code title=""><?xml-stylesheet?></code> processing instruction and the browser implements a
+ direct-to-DOM transformation, <code><a href=#the-script-element>script</a></code> elements created by the XSLT processor need to
+ be marked <a href=#parser-inserted>"parser-inserted"</a> and run in document order (modulo scripts marked <code title=attr-script-defer><a href=#attr-script-defer>defer</a></code> or <code title=attr-script-async><a href=#attr-script-async>async</a></code>),
+ asynchronously while the transformation is occurring.</li>
- <li><p>The <code title=dom-XSLTProcessor-transformToDocument>XSLTProcessor.transformToDocument()</code>
- method adds elements to a <code><a href=#document>Document</a></code> that is not in a
- <a href=#browsing-context>browsing context</a>, and, accordingly, any
- <code><a href=#the-script-element>script</a></code> elements they create need to have their
- <a href=#already-started>"already started"</a> flag set in the <a href=#prepare-a-script>prepare a
- script</a> algorithm and never get executed (<a href=#concept-bc-noscript title=concept-bc-noscript>scripting is disabled</a>). Such
- <code><a href=#the-script-element>script</a></code> elements still need to be marked
- <a href=#parser-inserted>"parser-inserted"</a>, though, such that their <code title=dom-script-async><a href=#dom-script-async>async</a></code> IDL attribute will return
- false in the absence of an <code title=attr-script-async><a href=#attr-script-async>async</a></code> content attribute.</li>
+ <li><p>The <code title=dom-XSLTProcessor-transformToDocument>XSLTProcessor.transformToDocument()</code> method
+ adds elements to a <code><a href=#document>Document</a></code> that is not in a <a href=#browsing-context>browsing context</a>, and,
+ accordingly, any <code><a href=#the-script-element>script</a></code> elements they create need to have their <a href=#already-started>"already
+ started"</a> flag set in the <a href=#prepare-a-script>prepare a script</a> algorithm and never get executed
+ (<a href=#concept-bc-noscript title=concept-bc-noscript>scripting is disabled</a>). Such <code><a href=#the-script-element>script</a></code>
+ elements still need to be marked <a href=#parser-inserted>"parser-inserted"</a>, though, such that their <code title=dom-script-async><a href=#dom-script-async>async</a></code> IDL attribute will return false in the absence of an <code title=attr-script-async><a href=#attr-script-async>async</a></code> content attribute.</li>
- <li><p>The <code title=dom-XSLTProcessor-transformToFragment>XSLTProcessor.transformToFragment()</code>
- method needs to create a fragment that is equivalent to one built
- manually by creating the elements using <code title=dom-document-createElementNS><a href=#dom-document-createelementns>document.createElementNS()</a></code>.
- For instance, it needs to create <code><a href=#the-script-element>script</a></code> elements that
- aren't <a href=#parser-inserted>"parser-inserted"</a> and that don't have their
- <a href=#already-started>"already started"</a> flag set, so that they will execute
- when the fragment is inserted into a document.</li>
+ <li><p>The <code title=dom-XSLTProcessor-transformToFragment>XSLTProcessor.transformToFragment()</code> method
+ needs to create a fragment that is equivalent to one built manually by creating the elements
+ using <code title=dom-document-createElementNS><a href=#dom-document-createelementns>document.createElementNS()</a></code>. For instance,
+ it needs to create <code><a href=#the-script-element>script</a></code> elements that aren't <a href=#parser-inserted>"parser-inserted"</a> and
+ that don't have their <a href=#already-started>"already started"</a> flag set, so that they will execute when the
+ fragment is inserted into a document.</li>
- </ul><p>The main distinction between the first two cases and the last
- case is that the first two operate on <code><a href=#document>Document</a></code>s and the
- last operates on a fragment.</p>
+ </ul><p>The main distinction between the first two cases and the last case is that the first two
+ operate on <code><a href=#document>Document</a></code>s and the last operates on a fragment.</p>
</div>
@@ -15310,120 +15237,96 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-noscript-element>noscript</a></code> element <a href=#represents>represents</a> nothing
- if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>, and
- <a href=#represents>represents</a> its children if <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a>. It is used
- to present different markup to user agents that support scripting
- and those that don't support scripting, by affecting how the
- document is parsed.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-noscript-element>noscript</a></code> element <a href=#represents>represents</a> nothing if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>, and <a href=#represents>represents</a> its children if
+ <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a>. It is used to present different
+ markup to user agents that support scripting and those that don't support scripting, by affecting
+ how the document is parsed.</p>
- <p>When used in <a href=#html-documents>HTML documents</a>, the allowed content
- model is as follows:</p>
+ <p>When used in <a href=#html-documents>HTML documents</a>, the allowed content model is as follows:</p>
- <dl><dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dl><dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is
+ disabled</a> for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
- <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only
- <code><a href=#the-link-element>link</a></code>, <code><a href=#the-style-element>style</a></code>, and <code><a href=#the-meta-element>meta</a></code>
- elements.</dd>
+ <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only <code><a href=#the-link-element>link</a></code>, <code><a href=#the-style-element>style</a></code>,
+ and <code><a href=#the-meta-element>meta</a></code> elements.</dd>
- <dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>
+ for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
- <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text,
- except that invoking the <a href=#html-fragment-parsing-algorithm>HTML fragment parsing
- algorithm</a> <!-- (which disables <script> execution) --> with
- the <code><a href=#the-noscript-element>noscript</a></code> element as the <var title=concept-frag-parse-context><a href=#concept-frag-parse-context>context</a></var> element and the
- text contents as the <var title="">input</var> must result in a
- list of nodes that consists only of <code><a href=#the-link-element>link</a></code>,
- <code><a href=#the-style-element>style</a></code>, and <code><a href=#the-meta-element>meta</a></code> elements that would be
- conforming if they were children of the <code><a href=#the-noscript-element>noscript</a></code>
- element, and no <a href=#parse-error title="parse error">parse
- errors</a>.</dd>
+ <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text, except that invoking the
+ <a href=#html-fragment-parsing-algorithm>HTML fragment parsing algorithm</a> <!-- (which disables <script> execution) --> with
+ the <code><a href=#the-noscript-element>noscript</a></code> element as the <var title=concept-frag-parse-context><a href=#concept-frag-parse-context>context</a></var>
+ element and the text contents as the <var title="">input</var> must result in a list of nodes
+ that consists only of <code><a href=#the-link-element>link</a></code>, <code><a href=#the-style-element>style</a></code>, and <code><a href=#the-meta-element>meta</a></code> elements that
+ would be conforming if they were children of the <code><a href=#the-noscript-element>noscript</a></code> element, and no <a href=#parse-error title="parse error">parse errors</a>.</dd>
- <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is
+ disabled</a> for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
- <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element's content model is
- <a href=#transparent>transparent</a>, with the additional restriction that a
- <code><a href=#the-noscript-element>noscript</a></code> element must not have a <code><a href=#the-noscript-element>noscript</a></code>
- element as an ancestor (that is, <code><a href=#the-noscript-element>noscript</a></code> can't be
- nested).</dd>
+ <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element's content model is <a href=#transparent>transparent</a>, with the
+ additional restriction that a <code><a href=#the-noscript-element>noscript</a></code> element must not have a <code><a href=#the-noscript-element>noscript</a></code>
+ element as an ancestor (that is, <code><a href=#the-noscript-element>noscript</a></code> can't be nested).</dd>
- <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-script title=concept-n-script>scripting is
+ enabled</a> for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
<dd>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text,
- except that the text must be such that running the following
- algorithm results in a conforming document with no
- <code><a href=#the-noscript-element>noscript</a></code> elements and no <code><a href=#the-script-element>script</a></code>
- elements, and such that no step in the algorithm causes an
- <a href=#html-parser>HTML parser</a> to flag a <a href=#parse-error>parse error</a>:</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text, except that the text must be such
+ that running the following algorithm results in a conforming document with no
+ <code><a href=#the-noscript-element>noscript</a></code> elements and no <code><a href=#the-script-element>script</a></code> elements, and such that no step in the
+ algorithm causes an <a href=#html-parser>HTML parser</a> to flag a <a href=#parse-error>parse error</a>:</p>
- <ol><li>Remove every <code><a href=#the-script-element>script</a></code> element from the
- document.</li>
+ <ol><li>Remove every <code><a href=#the-script-element>script</a></code> element from the document.</li>
- <li>Make a list of every <code><a href=#the-noscript-element>noscript</a></code> element in the
- document. For every <code><a href=#the-noscript-element>noscript</a></code> element in that list,
- perform the following steps:
+ <li>Make a list of every <code><a href=#the-noscript-element>noscript</a></code> element in the document. For every
+ <code><a href=#the-noscript-element>noscript</a></code> element in that list, perform the following steps:
- <ol><li>Let the <var title="">parent element</var> be the parent
- element of the <code><a href=#the-noscript-element>noscript</a></code> element.</li>
+ <ol><li>Let the <var title="">parent element</var> be the parent element of the
+ <code><a href=#the-noscript-element>noscript</a></code> element.</li>
- <li>Take all the children of the <var title="">parent element</var>
- that come before the <code><a href=#the-noscript-element>noscript</a></code> element, and call these
- elements <var title="">the before children</var>.</li>
+ <li>Take all the children of the <var title="">parent element</var> that come before the
+ <code><a href=#the-noscript-element>noscript</a></code> element, and call these elements <var title="">the before
+ children</var>.</li>
- <li>Take all the children of the <var title="">parent element</var>
- that come <em>after</em> the <code><a href=#the-noscript-element>noscript</a></code> element, and
- call these elements <var title="">the after children</var>.</li>
+ <li>Take all the children of the <var title="">parent element</var> that come <em>after</em>
+ the <code><a href=#the-noscript-element>noscript</a></code> element, and call these elements <var title="">the after
+ children</var>.</li>
- <li>Let <var title="">s</var> be the concatenation of all the
- <code><a href=#text>Text</a></code> node children of the <code><a href=#the-noscript-element>noscript</a></code>
- element.</li>
+ <li>Let <var title="">s</var> be the concatenation of all the <code><a href=#text>Text</a></code> node children
+ of the <code><a href=#the-noscript-element>noscript</a></code> element.</li>
- <li>Set the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code>
- attribute of the <var title="">parent element</var> to the value
- of <var title="">s</var>. (This, as a side-effect, causes the
- <code><a href=#the-noscript-element>noscript</a></code> element to be removed from the
- document.)</li>
+ <li>Set the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> attribute of the <var title="">parent element</var> to the value of <var title="">s</var>. (This, as a side-effect,
+ causes the <code><a href=#the-noscript-element>noscript</a></code> element to be removed from the document.)</li>
- <li>Insert <var title="">the before children</var> at the start of
- the <var title="">parent element</var>, preserving their original
- relative order.</li>
+ <li>Insert <var title="">the before children</var> at the start of the <var title="">parent
+ element</var>, preserving their original relative order.</li>
- <li>Insert <var title="">the after children</var> at the end of the
- <var title="">parent element</var>, preserving their original
- relative order.</li>
+ <li>Insert <var title="">the after children</var> at the end of the <var title="">parent
+ element</var>, preserving their original relative order.</li>
</ol></li>
</ol></dd>
- </dl><p class=note>All these contortions are required because, for
- historical reasons, the <code><a href=#the-noscript-element>noscript</a></code> element is handled
- differently by the <a href=#html-parser>HTML parser</a> based on whether <a href=#scripting-flag title="scripting flag">scripting was enabled or not</a> when the
- parser was invoked.</p>
+ </dl><p class=note>All these contortions are required because, for historical reasons, the
+ <code><a href=#the-noscript-element>noscript</a></code> element is handled differently by the <a href=#html-parser>HTML parser</a> based on
+ whether <a href=#scripting-flag title="scripting flag">scripting was enabled or not</a> when the parser was
+ invoked.</p>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element must not be used in <a href=#xml-documents>XML
- documents</a>.</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element must not be used in <a href=#xml-documents>XML documents</a>.</p>
- <p class=note>The <code><a href=#the-noscript-element>noscript</a></code> element is only effective
- in <a href=#syntax>the HTML syntax</a>, it has no effect in <a href=#the-xhtml-syntax>the XHTML
- syntax</a>. This is because the way it works is by essentially
- "turning off" the parser when scripts are enabled, so that the
- contents of the element are treated as pure text and not as real
- elements. XML does not define a mechanism by which to do this.</p>
+ <p class=note>The <code><a href=#the-noscript-element>noscript</a></code> element is only effective in <a href=#syntax>the HTML
+ syntax</a>, it has no effect in <a href=#the-xhtml-syntax>the XHTML syntax</a>. This is because the way it works
+ is by essentially "turning off" the parser when scripts are enabled, so that the contents of the
+ element are treated as pure text and not as real elements. XML does not define a mechanism by
+ which to do this.</p>
<div class=impl>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element has no other requirements. In
- particular, children of the <code><a href=#the-noscript-element>noscript</a></code> element are not
- exempt from <a href=#form-submission>form submission</a>, scripting, and so forth,
- even when <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>
- for the element.</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element has no other requirements. In particular, children of the
+ <code><a href=#the-noscript-element>noscript</a></code> element are not exempt from <a href=#form-submission>form submission</a>, scripting, and so
+ forth, even when <a href=#concept-n-script title=concept-n-script>scripting is enabled</a> for the element.</p>
</div>
@@ -15453,17 +15356,13 @@
</noscript>
</form></pre>
- <p>When script is disabled, a button appears to do the calculation
- on the server side. When script is enabled, the value is computed
- on-the-fly instead.</p>
+ <p>When script is disabled, a button appears to do the calculation on the server side. When
+ script is enabled, the value is computed on-the-fly instead.</p>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element is a blunt
- instrument. Sometimes, scripts might be enabled, but for some
- reason the page's script might fail. For this reason, it's
- generally better to avoid using <code><a href=#the-noscript-element>noscript</a></code>, and to
- instead design the script to change the page from being a
- scriptless page to a scripted page on the fly, as in the next
- example:</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element is a blunt instrument. Sometimes, scripts might be enabled,
+ but for some reason the page's script might fail. For this reason, it's generally better to avoid
+ using <code><a href=#the-noscript-element>noscript</a></code>, and to instead design the script to change the page from being a
+ scriptless page to a scripted page on the fly, as in the next example:</p>
<pre><form action="calcSquare.php">
<p>
@@ -15486,9 +15385,8 @@
</script>
</form></pre>
- <p>The above technique is also useful in XHTML, since
- <code><a href=#the-noscript-element>noscript</a></code> is not supported in <a href=#the-xhtml-syntax>the XHTML
- syntax</a>.</p>
+ <p>The above technique is also useful in XHTML, since <code><a href=#the-noscript-element>noscript</a></code> is not supported in
+ <a href=#the-xhtml-syntax>the XHTML syntax</a>.</p>
</div>
@@ -19360,7 +19258,6 @@
<div class=impl>
-<!--CLEANUP-->
<p>The <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code>, <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code>, <code title=attr-hyperlink-download><a href=#attr-hyperlink-download>download</a></code>, and <code title=attr-hyperlink-ping><a href=#ping>ping</a></code>
attributes affect what happens when users <a href=#following-hyperlinks title="following hyperlinks">follow
hyperlinks</a> or <a href=#downloading-hyperlinks title="downloading hyperlinks">download hyperlinks</a> created using
@@ -19499,56 +19396,49 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-em-element>em</a></code> element <a href=#represents>represents</a> stress
- emphasis of its contents.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-em-element>em</a></code> element <a href=#represents>represents</a> stress emphasis of its contents.</p>
- <p>The level of stress that a particular piece of content has is
- given by its number of ancestor <code><a href=#the-em-element>em</a></code> elements.</p>
+ <p>The level of stress that a particular piece of content has is given by its number of ancestor
+ <code><a href=#the-em-element>em</a></code> elements.</p>
- <p>The placement of stress emphasis changes the meaning of the
- sentence. The element thus forms an integral part of the content.
- The precise way in which stress is used in this way depends on the
+ <p>The placement of stress emphasis changes the meaning of the sentence. The element thus forms an
+ integral part of the content. The precise way in which stress is used in this way depends on the
language.</p>
<div class=example>
- <p>These examples show how changing the stress emphasis changes the
- meaning. First, a general statement of fact, with no stress:</p>
+ <p>These examples show how changing the stress emphasis changes the meaning. First, a general
+ statement of fact, with no stress:</p>
<pre><p>Cats are cute animals.</p></pre>
- <p>By emphasizing the first word, the statement implies that the
- kind of animal under discussion is in question (maybe someone is
- asserting that dogs are cute):</p>
+ <p>By emphasizing the first word, the statement implies that the kind of animal under discussion
+ is in question (maybe someone is asserting that dogs are cute):</p>
<pre><p><em>Cats</em> are cute animals.</p></pre>
- <p>Moving the stress to the verb, one highlights that the truth of
- the entire sentence is in question (maybe someone is saying cats
- are not cute):</p>
+ <p>Moving the stress to the verb, one highlights that the truth of the entire sentence is in
+ question (maybe someone is saying cats are not cute):</p>
<pre><p>Cats <em>are</em> cute animals.</p></pre>
- <p>By moving it to the adjective, the exact nature of the cats
- is reasserted (maybe someone suggested cats were <em>mean</em>
- animals):</p>
+ <p>By moving it to the adjective, the exact nature of the cats is reasserted (maybe someone
+ suggested cats were <em>mean</em> animals):</p>
<pre><p>Cats are <em>cute</em> animals.</p></pre>
- <p>Similarly, if someone asserted that cats were vegetables,
- someone correcting this might emphasize the last word:</p>
+ <p>Similarly, if someone asserted that cats were vegetables, someone correcting this might
+ emphasize the last word:</p>
<pre><p>Cats are cute <em>animals</em>.</p></pre>
- <p>By emphasizing the entire sentence, it becomes clear that the
- speaker is fighting hard to get the point across. This kind of
- stress emphasis also typically affects the punctuation, hence the
+ <p>By emphasizing the entire sentence, it becomes clear that the speaker is fighting hard to get
+ the point across. This kind of stress emphasis also typically affects the punctuation, hence the
exclamation mark here.</p>
<pre><p><em>Cats are cute animals!</em></p></pre>
- <p>Anger mixed with emphasizing the cuteness could lead to markup
- such as:</p>
+ <p>Anger mixed with emphasizing the cuteness could lead to markup such as:</p>
<pre><p><em>Cats are <em>cute</em> animals!</em></p></pre>
@@ -19556,14 +19446,12 @@
<div class=note>
- <p>The <code><a href=#the-em-element>em</a></code> element isn't a generic "italics"
- element. Sometimes, text is intended to stand out from the rest of
- the paragraph, as if it was in a different mood or voice. For this,
+ <p>The <code><a href=#the-em-element>em</a></code> element isn't a generic "italics" element. Sometimes, text is intended to
+ stand out from the rest of the paragraph, as if it was in a different mood or voice. For this,
the <code><a href=#the-i-element>i</a></code> element is more appropriate.</p>
- <p>The <code><a href=#the-em-element>em</a></code> element also isn't intended to convey
- importance; for that purpose, the <code><a href=#the-strong-element>strong</a></code> element is
- more appropriate.</p>
+ <p>The <code><a href=#the-em-element>em</a></code> element also isn't intended to convey importance; for that purpose, the
+ <code><a href=#the-strong-element>strong</a></code> element is more appropriate.</p>
<!--
@@ -91272,7 +91160,7 @@
</dd>
- <dt id=adoptionAgency>An end tag whose tag name is one of: "a",
+ <dt>An end tag whose tag name is one of: "a",
"b", "big", "code", "em", "font", "i", "nobr", "s", "small",
"strike", "strong", "tt", "u"</dt>
<dd>
@@ -91771,7 +91659,7 @@
<li><p>Pop elements from the <a href=#stack-of-open-elements>stack of open elements</a> until a <code><a href=#the-p-element>p</a></code> element
has been popped from the stack.</li>
- </ol><p>The <dfn id=adoption-agency-algorithm>adoption agency algorithm</dfn>, which takes as its only argument a tag name <var title="">subject</var> for which the algorithm is being run, consists of the following steps:</p>
+ </ol><p id=adoptionAgency>The <dfn id=adoption-agency-algorithm>adoption agency algorithm</dfn>, which takes as its only argument a tag name <var title="">subject</var> for which the algorithm is being run, consists of the following steps:</p>
<!--CLEANUP-->
<ol><li><p>Let <var title="">outer loop counter</var> be
Modified: index
===================================================================
--- index 2013-07-30 21:45:54 UTC (rev 8104)
+++ index 2013-07-31 19:11:24 UTC (rev 8105)
@@ -256,7 +256,7 @@
<header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 30 July 2013</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 31 July 2013</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -9822,12 +9822,13 @@
elements">HTML element</a>) is either '<dfn id=concept-ltr title=concept-ltr>ltr</dfn>' or '<dfn id=concept-rtl title=concept-rtl>rtl</dfn>', and is determined as per the first appropriate set of steps from
the following list:</p>
- <dl class=switch><!--CLEANUP--><dt>If the element's <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-ltr-state title=attr-dir-ltr-state>ltr</a> state</dt>
+ <dl class=switch><dt>If the element's <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-ltr-state title=attr-dir-ltr-state>ltr</a> state</dt>
<dt>If the element is a <a href=#root-element>root element</a> and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code>
attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
- <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
+ <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code>
+ attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
<dd><p><a href=#the-directionality>The directionality</a> of the element is '<a href=#concept-ltr title=concept-ltr>ltr</a>'.</dd>
@@ -9836,7 +9837,10 @@
<dd><p><a href=#the-directionality>The directionality</a> of the element is '<a href=#concept-rtl title=concept-rtl>rtl</a>'.</dd>
- <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-text>Text</a>, <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-search>Search</a>, <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a>, <a href="#url-state-(type=url)" title=attr-input-type-url>URL</a>, or <a href="#e-mail-state-(type=email)" title=attr-input-type-email>E-mail</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-auto-state title=attr-dir-auto-state>auto</a> state</dt>
+ <dt>If the element is an <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-text>Text</a>, <a href="#text-(type=text)-state-and-search-state-(type=search)" title=attr-input-type-search>Search</a>,
+ <a href="#telephone-state-(type=tel)" title=attr-input-type-tel>Telephone</a>, <a href="#url-state-(type=url)" title=attr-input-type-url>URL</a>,
+ or <a href="#e-mail-state-(type=email)" title=attr-input-type-email>E-mail</a> state, and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute is in the <a href=#attr-dir-auto-state title=attr-dir-auto-state>auto</a>
+ state</dt>
<dt>If the element is a <code><a href=#the-textarea-element>textarea</a></code> element and the <code title=attr-dir><a href=#the-dir-attribute>dir</a></code>
attribute is in the <a href=#attr-dir-auto-state title=attr-dir-auto-state>auto</a> state</dt>
@@ -9846,8 +9850,7 @@
<p>If the element's <a href=#concept-fe-value title=concept-fe-value>value</a> contains a character of
bidirectional character type AL or R, and there is no character of bidirectional character type
L anywhere before it in the element's <a href=#concept-fe-value title=concept-fe-value>value</a>, then
- <a href=#the-directionality>the directionality</a> of the element is '<a href=#concept-rtl title=concept-rtl>rtl</a>'.
- <a href=#refsBIDI>[BIDI]</a></p>
+ <a href=#the-directionality>the directionality</a> of the element is '<a href=#concept-rtl title=concept-rtl>rtl</a>'. <a href=#refsBIDI>[BIDI]</a></p>
<p>Otherwise, if the element's <a href=#concept-fe-value title=concept-fe-value>value</a> is not the empty
string, or if the element is a <a href=#root-element>root element</a>, <a href=#the-directionality>the directionality</a> of the
@@ -9939,7 +9942,8 @@
<dd>The <a href=#directionality-of-the-attribute>directionality of the attribute</a> is the same as <a href=#the-directionality title="the
directionality">the element's directionality</a>.</dd>
- </dl><p>The following attributes are <dfn id=directionality-capable-attribute title="directionality-capable attribute">directionality-capable attributes</dfn>:</p>
+ </dl><p>The following attributes are <dfn id=directionality-capable-attribute title="directionality-capable
+ attribute">directionality-capable attributes</dfn>:</p>
<ul class=brief><li><code title=attr-th-abbr><a href=#attr-th-abbr>abbr</a></code> on <code><a href=#the-th-element>th</a></code> elements</li>
<li><code title="">alt</code> on <code title=attr-area-alt><a href=#attr-area-alt>area</a></code>,
@@ -10348,11 +10352,12 @@
<h4 id=content-models><span class=secno>3.2.5 </span><dfn>Content models</dfn></h4>
<p>Each element defined in this specification has a content model: a description of the element's
- expected <a href=#concept-html-contents title=concept-html-contents>contents</a>. An <a href=#html-elements title="HTML elements">HTML element</a> must have contents that
- match the requirements described in the element's content model. The <dfn id=concept-html-contents title=concept-html-contents>contents</dfn> of an element are
- its children in the DOM, except for <code><a href=#the-template-element>template</a></code> elements, where the children are those
- in the <a href=#template-contents>template contents</a> (a separate <code><a href=#documentfragment>DocumentFragment</a></code> assigned to the
- element when the element is created).</p>
+ expected <a href=#concept-html-contents title=concept-html-contents>contents</a>. An <a href=#html-elements title="HTML elements">HTML
+ element</a> must have contents that match the requirements described in the element's content
+ model. The <dfn id=concept-html-contents title=concept-html-contents>contents</dfn> of an element are its children in the
+ DOM, except for <code><a href=#the-template-element>template</a></code> elements, where the children are those in the <a href=#template-contents>template
+ contents</a> (a separate <code><a href=#documentfragment>DocumentFragment</a></code> assigned to the element when the element
+ is created).</p>
<p>The <a href=#space-character title="space character">space characters</a> are always allowed between elements.
User agents represent these characters between elements in the source markup as <code><a href=#text>Text</a></code>
@@ -12229,7 +12234,6 @@
<h4 id=document.writeln()><span class=secno>3.4.4 </span><code title=dom-document-writeln><a href=#dom-document-writeln>document.writeln()</a></code></h4>
-<!--CLEANUP-->
<dl class=domintro><dt><var title="">document</var> . <code title=dom-document-writeln><a href=#dom-document-writeln>writeln</a></code>(<var title="">text</var>...)</dt>
<dd>
@@ -12396,7 +12400,6 @@
<h4 id=the-title-element><span class=secno>4.2.2 </span>The <dfn><code>title</code></dfn> element</h4>
-<!--CLEANUP-->
<dl class=element><dt><a href=#element-dfn-categories title=element-dfn-categories>Categories</a>:</dt>
<dd><a href=#metadata-content>Metadata content</a>.</dd>
@@ -12414,16 +12417,13 @@
attribute DOMString <a href=#dom-title-text title=dom-title-text>text</a>;
};</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-title-element>title</a></code> element <a href=#represents>represents</a> the
- document's title or name. Authors should use titles that identify
- their documents even when they are used out of context, for example
- in a user's history or bookmarks, or in search results. The
- document's title is often different from its first heading, since the
- first heading does not have to stand alone when taken out of
- context.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-title-element>title</a></code> element <a href=#represents>represents</a> the document's title or name. Authors
+ should use titles that identify their documents even when they are used out of context, for
+ example in a user's history or bookmarks, or in search results. The document's title is often
+ different from its first heading, since the first heading does not have to stand alone when taken
+ out of context.</p>
- <p>There must be no more than one <code><a href=#the-title-element>title</a></code> element per
- document.</p>
+ <p>There must be no more than one <code><a href=#the-title-element>title</a></code> element per document.</p>
<p>The <code><a href=#the-title-element>title</a></code> element must not be empty.</p>
@@ -12436,30 +12436,27 @@
<dd>
- <p>Returns the contents of the element, ignoring child nodes that
- aren't <code><a href=#text>Text</a></code> nodes.</p>
+ <p>Returns the contents of the element, ignoring child nodes that aren't <code><a href=#text>Text</a></code>
+ nodes.</p>
- <p>Can be set, to replace the element's children with the given
- value.</p>
+ <p>Can be set, to replace the element's children with the given value.</p>
</dd>
</dl><div class=impl>
<p>The IDL attribute <dfn id=dom-title-text title=dom-title-text><code>text</code></dfn> must return a
- concatenation of the contents of all the <code><a href=#text>Text</a></code> nodes
- that are children of the <code><a href=#the-title-element>title</a></code> element (ignoring any
- other nodes such as comments or elements), in tree order. On
- setting, it must act the same way as the <code><a href=#textcontent>textContent</a></code>
- IDL attribute.</p>
+ concatenation of the contents of all the <code><a href=#text>Text</a></code> nodes that are children of the
+ <code><a href=#the-title-element>title</a></code> element (ignoring any other nodes such as comments or elements), in tree order.
+ On setting, it must act the same way as the <code><a href=#textcontent>textContent</a></code> IDL attribute.</p>
</div>
<!--TOPIC:HTML-->
<div class=example>
- <p>Here are some examples of appropriate titles, contrasted with
- the top-level headings that might be used on those same pages.</p>
+ <p>Here are some examples of appropriate titles, contrasted with the top-level headings that
+ might be used on those same pages.</p>
<pre> <title>Introduction to The Mating Rituals of Bees</title>
...
@@ -12467,10 +12464,9 @@
<p>This companion guide to the highly successful
<cite>Introduction to Medieval Bee-Keeping</cite> book is...</pre>
- <p>The next page might be a part of the same site. Note how the
- title describes the subject matter unambiguously, while the first
- heading assumes the reader knows what the context is and therefore
- won't wonder if the dances are Salsa or Waltz:</p>
+ <p>The next page might be a part of the same site. Note how the title describes the subject
+ matter unambiguously, while the first heading assumes the reader knows what the context is and
+ therefore won't wonder if the dances are Salsa or Waltz:</p>
<pre> <title>Dances used during bee mating rituals</title>
...
@@ -12482,12 +12478,10 @@
<div class=impl>
- <p>User agents should use the document's title when referring to the
- document in their user interface. When the contents of a
- <code><a href=#the-title-element>title</a></code> element are used in this way, <a href=#the-directionality>the
- directionality</a> of that <code><a href=#the-title-element>title</a></code> element should be
- used to set the directionality of the document's title in the user
- interface.</p>
+ <p>User agents should use the document's title when referring to the document in their user
+ interface. When the contents of a <code><a href=#the-title-element>title</a></code> element are used in this way, <a href=#the-directionality>the
+ directionality</a> of that <code><a href=#the-title-element>title</a></code> element should be used to set the directionality
+ of the document's title in the user interface.</p>
</div>
@@ -12513,48 +12507,41 @@
attribute DOMString <a href=#dom-base-target title=dom-base-target>target</a>;
};</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-base-element>base</a></code> element allows authors to specify the
- <a href=#document-base-url>document base URL</a> for the purposes of <a href=#resolve-a-url title="resolve a url">resolving relative URLs</a>, and the name
- of the default <a href=#browsing-context>browsing context</a> for the purposes of
- <a href=#following-hyperlinks>following hyperlinks</a>. The element does not <a href=#represents title=represents>represent</a> any content beyond this
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-base-element>base</a></code> element allows authors to specify the <a href=#document-base-url>document base URL</a> for
+ the purposes of <a href=#resolve-a-url title="resolve a url">resolving relative URLs</a>, and the name of the
+ default <a href=#browsing-context>browsing context</a> for the purposes of <a href=#following-hyperlinks>following hyperlinks</a>. The
+ element does not <a href=#represents title=represents>represent</a> any content beyond this
information.</p>
- <p>There must be no more than one <code><a href=#the-base-element>base</a></code> element per
- document.</p>
+ <p>There must be no more than one <code><a href=#the-base-element>base</a></code> element per document.</p>
- <p>A <code><a href=#the-base-element>base</a></code> element must have either an <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute, a <code title=attr-base-target><a href=#attr-base-target>target</a></code> attribute, or both.</p>
+ <p>A <code><a href=#the-base-element>base</a></code> element must have either an <code title=attr-base-href><a href=#attr-base-href>href</a></code>
+ attribute, a <code title=attr-base-target><a href=#attr-base-target>target</a></code> attribute, or both.</p>
- <p>The <dfn id=attr-base-href title=attr-base-href><code>href</code></dfn> content
- attribute, if specified, must contain a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially
- surrounded by spaces</a>.</p>
+ <p>The <dfn id=attr-base-href title=attr-base-href><code>href</code></dfn> content attribute, if specified, must
+ contain a <a href=#valid-url-potentially-surrounded-by-spaces>valid URL potentially surrounded by spaces</a>.</p>
- <p>A <code><a href=#the-base-element>base</a></code> element, if it has an <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute, must come before any
- other elements in the tree that have attributes defined as taking
- <a href=#url title=URL>URLs</a>, except the <code><a href=#the-html-element>html</a></code> element
- (its <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute
- isn't affected by <code><a href=#the-base-element>base</a></code> elements).</p>
+ <p>A <code><a href=#the-base-element>base</a></code> element, if it has an <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute,
+ must come before any other elements in the tree that have attributes defined as taking <a href=#url title=URL>URLs</a>, except the <code><a href=#the-html-element>html</a></code> element (its <code title=attr-html-manifest><a href=#attr-html-manifest>manifest</a></code> attribute isn't affected by <code><a href=#the-base-element>base</a></code>
+ elements).</p>
<div class=impl>
- <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements
- with <code title=attr-base-href><a href=#attr-base-href>href</a></code> attributes, all but the
- first are ignored.</p>
+ <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements with <code title=attr-base-href><a href=#attr-base-href>href</a></code> attributes, all but the first are ignored.</p>
</div>
- <p>The <dfn id=attr-base-target title=attr-base-target><code>target</code></dfn>
- attribute, if specified, must contain a <a href=#valid-browsing-context-name-or-keyword>valid browsing context
- name or keyword</a>, which specifies which <a href=#browsing-context>browsing
- context</a> is to be used as the default when <a href=#hyperlink title=hyperlink>hyperlinks</a> and <a href=#the-form-element title=form>forms</a> in the <code><a href=#document>Document</a></code> cause <a href=#navigate title=navigate>navigation</a>.</p>
+ <p>The <dfn id=attr-base-target title=attr-base-target><code>target</code></dfn> attribute, if specified, must
+ contain a <a href=#valid-browsing-context-name-or-keyword>valid browsing context name or keyword</a>, which specifies which
+ <a href=#browsing-context>browsing context</a> is to be used as the default when <a href=#hyperlink title=hyperlink>hyperlinks</a> and <a href=#the-form-element title=form>forms</a> in the
+ <code><a href=#document>Document</a></code> cause <a href=#navigate title=navigate>navigation</a>.</p>
- <p>A <code><a href=#the-base-element>base</a></code> element, if it has a <code title=attr-base-target><a href=#attr-base-target>target</a></code> attribute, must come before
- any elements in the tree that represent <a href=#hyperlink title=hyperlink>hyperlinks</a>.</p>
+ <p>A <code><a href=#the-base-element>base</a></code> element, if it has a <code title=attr-base-target><a href=#attr-base-target>target</a></code>
+ attribute, must come before any elements in the tree that represent <a href=#hyperlink title=hyperlink>hyperlinks</a>.</p>
<div class=impl>
- <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements
- with <code title=attr-base-target><a href=#attr-base-target>target</a></code> attributes, all but
- the first are ignored.</p>
+ <p class=note>If there are multiple <code><a href=#the-base-element>base</a></code> elements with <code title=attr-base-target><a href=#attr-base-target>target</a></code> attributes, all but the first are ignored.</p>
<p>A <code><a href=#the-base-element>base</a></code> element that is the first <code><a href=#the-base-element>base</a></code> element with an <code title=attr-base-href><a href=#attr-base-href>href</a></code> content attribute in a particular <code><a href=#document>Document</a></code> has a
<dfn id=frozen-base-url>frozen base URL</dfn>. The <a href=#frozen-base-url>frozen base URL</a> must be <a href=#set-the-frozen-base-url title="set the frozen
@@ -12575,43 +12562,36 @@
<a href=#frozen-base-url>frozen base URL</a> to the <a href=#resulting-absolute-url>resulting absolute URL</a>, otherwise, set the
<a href=#frozen-base-url>frozen base URL</a> to the <a href=#fallback-base-url>fallback base URL</a>.</p>
- <p>The <dfn id=dom-base-href title=dom-base-href><code>href</code></dfn> IDL
- attribute, on getting, must return the result of running the
- following algorithm:
+ <p>The <dfn id=dom-base-href title=dom-base-href><code>href</code></dfn> IDL attribute, on getting, must return
+ the result of running the following algorithm:
- <ol><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1715 --><li><p>If the <code><a href=#the-base-element>base</a></code> element has no <code title=attr-base-href><a href=#attr-base-href>href</a></code> content attribute, then return
- the <a href=#document-base-url>document base URL</a> and abort these steps.</li>
+ <ol><!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1715 --><li><p>If the <code><a href=#the-base-element>base</a></code> element has no <code title=attr-base-href><a href=#attr-base-href>href</a></code> content
+ attribute, then return the <a href=#document-base-url>document base URL</a> and abort these steps.</li>
- <li><p>Let <var title="">fallback base url</var> be the
- <code><a href=#document>Document</a></code>'s <a href=#fallback-base-url>fallback base URL</a>.</li>
+ <li><p>Let <var title="">fallback base url</var> be the <code><a href=#document>Document</a></code>'s <a href=#fallback-base-url>fallback
+ base URL</a>.</li>
- <li><p>Let <var title="">url</var> be the value of the <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute of the
- <code><a href=#the-base-element>base</a></code> element.</li>
+ <li><p>Let <var title="">url</var> be the value of the <code title=attr-base-href><a href=#attr-base-href>href</a></code>
+ attribute of the <code><a href=#the-base-element>base</a></code> element.</li>
- <li><p><a href=#resolve-a-url title="resolve a URL">Resolve</a> <var title="">url</var> relative to <var title="">fallback base
- url</var> (thus, the <code><a href=#the-base-element>base</a></code> <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute isn't affected by
- <code title=attr-xml-base><a href=#the-xml:base-attribute-(xml-only)>xml:base</a></code> attributes or
- <code><a href=#the-base-element>base</a></code> elements).</li>
+ <li><p><a href=#resolve-a-url title="resolve a URL">Resolve</a> <var title="">url</var> relative to <var title="">fallback base url</var> (thus, the <code><a href=#the-base-element>base</a></code> <code title=attr-base-href><a href=#attr-base-href>href</a></code> attribute isn't affected by <code title=attr-xml-base><a href=#the-xml:base-attribute-(xml-only)>xml:base</a></code> attributes or <code><a href=#the-base-element>base</a></code> elements).</li>
- <li><p>If the previous step was successful, return the resulting
- <a href=#absolute-url>absolute URL</a> and abort these steps.</li>
+ <li><p>If the previous step was successful, return the resulting <a href=#absolute-url>absolute URL</a> and
+ abort these steps.</li>
<li><p>Otherwise, return the empty string.</li>
- </ol><p>The <code title=dom-base-href><a href=#dom-base-href>href</a></code> IDL attribute, on
- setting, must set the <code title=attr-base-href><a href=#attr-base-href>href</a></code>
- content attribute to the given new value.</p>
+ </ol><p>The <code title=dom-base-href><a href=#dom-base-href>href</a></code> IDL attribute, on setting, must set the <code title=attr-base-href><a href=#attr-base-href>href</a></code> content attribute to the given new value.</p>
- <p>The <dfn id=dom-base-target title=dom-base-target><code>target</code></dfn> IDL
- attribute must <a href=#reflect>reflect</a> the content attribute of the
- same name.</p>
+ <p>The <dfn id=dom-base-target title=dom-base-target><code>target</code></dfn> IDL attribute must
+ <a href=#reflect>reflect</a> the content attribute of the same name.</p>
</div>
<div class=example>
- <p>In this example, a <code><a href=#the-base-element>base</a></code> element is used to set the
- <a href=#document-base-url>document base URL</a>:</p>
+ <p>In this example, a <code><a href=#the-base-element>base</a></code> element is used to set the <a href=#document-base-url>document base
+ URL</a>:</p>
<pre><!DOCTYPE html>
<html>
@@ -13393,49 +13373,40 @@
These numbers are low; further study is required to establish what
people expect to have work and what is necessary.
--><div class=impl>
-<!--CLEANUP-->
- <p>When a <code><a href=#the-meta-element>meta</a></code> element is <a href=#insert-an-element-into-a-document title="insert an
- element into a document">inserted into the document</a>, if its
- <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute is
- present and represents one of the above states, then the user agent
- must run the algorithm appropriate for that state, as described in
- the following list:</p>
+ <p>When a <code><a href=#the-meta-element>meta</a></code> element is <a href=#insert-an-element-into-a-document title="insert an element into a document">inserted
+ into the document</a>, if its <code title=attr-meta-http-equiv><a href=#attr-meta-http-equiv>http-equiv</a></code> attribute is
+ present and represents one of the above states, then the user agent must run the algorithm
+ appropriate for that state, as described in the following list:</p>
+
</div>
<dl><dt class=impl><dfn id=attr-meta-http-equiv-content-language title=attr-meta-http-equiv-content-language>Content language state</dfn> (<code title="">http-equiv="content-language"</code>)
<dd class=impl>
- <p class=note>This feature is non-conforming. Authors are
- encouraged to use the <code title=attr-lang><a href=#attr-lang>lang</a></code>
- attribute instead.</p>
+ <p class=note>This feature is non-conforming. Authors are encouraged to use the <code title=attr-lang><a href=#attr-lang>lang</a></code> attribute instead.</p>
- <p>This pragma sets the <dfn id=pragma-set-default-language>pragma-set default language</dfn>.
- Until such a pragma is successfully processed, there is no
- <a href=#pragma-set-default-language>pragma-set default language</a>.</p>
+ <p>This pragma sets the <dfn id=pragma-set-default-language>pragma-set default language</dfn>. Until such a pragma is
+ successfully processed, there is no <a href=#pragma-set-default-language>pragma-set default language</a>.</p>
<!-- http://www.hixie.ch/tests/adhoc/html/meta/content-language/ -->
- <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute, then abort these
- steps.</li>
+ <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code>
+ attribute, then abort these steps.</li>
<li><p>If the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute contains a
- U+002C COMMA character (,) then abort these steps.</li><!--
- if you remove this, un-comment-out the corresponding bits in the
- step below. -->
+ U+002C COMMA character (,) then abort these steps.</li><!-- if you remove this,
+ un-comment-out the corresponding bits in the step below. -->
- <li><p>Let <var title="">input</var> be the value of the
- element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code>
- attribute.</li>
+ <li><p>Let <var title="">input</var> be the value of the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute.</li>
- <li><p>Let <var title="">position</var> point at the first
- character of <var title="">input</var>.</li>
+ <li><p>Let <var title="">position</var> point at the first character of <var title="">input</var>.</li>
<li><p><a href=#skip-whitespace>Skip whitespace</a>.</li>
- <li><p><a href=#collect-a-sequence-of-characters>Collect a sequence of characters</a> that are not<!--neither--> <a href=#space-character title="space character">space characters</a><!-- nor a U+002C
- COMMA character (,)-->.</li>
+ <li><p><a href=#collect-a-sequence-of-characters>Collect a sequence of characters</a> that are not<!--neither--> <a href=#space-character title="space character">space characters</a><!-- nor a U+002C COMMA character
+ (,)-->.</li>
<li><p>Let <var title="">candidate</var> be the string that resulted from the previous
step.</li>
@@ -13444,8 +13415,8 @@
<li><p>Set the <a href=#pragma-set-default-language>pragma-set default language</a> to <var title="">candidate</var>.</li>
- </ol><p class=note>This pragma is not exactly equivalent to the HTTP
- <code>Content-Language</code> header. <a href=#refsHTTP>[HTTP]</a></p>
+ </ol><p class=note>This pragma is not exactly equivalent to the HTTP <code>Content-Language</code>
+ header. <a href=#refsHTTP>[HTTP]</a></p>
</dd>
@@ -13479,17 +13450,15 @@
<dd>
- <p>This pragma sets the name of the default <a href=#alternative-style-sheet-sets title="alternative style sheet sets">alternative style sheet
- set</a>.</p>
+ <p>This pragma sets the name of the default <a href=#alternative-style-sheet-sets title="alternative style sheet
+ sets">alternative style sheet set</a>.</p>
<div class=impl>
- <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute, or if that
- attribute's value is the empty string, then abort these
- steps.</li>
+ <ol><li><p>If the <code><a href=#the-meta-element>meta</a></code> element has no <code title=attr-meta-content><a href=#attr-meta-content>content</a></code>
+ attribute, or if that attribute's value is the empty string, then abort these steps.</li>
- <li><p>Set the <a href=#preferred-style-sheet-set>preferred style sheet set</a> to the
- value of the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute. <a href=#refsCSSOM>[CSSOM]</a></li>
+ <li><p>Set the <a href=#preferred-style-sheet-set>preferred style sheet set</a> to the value of the element's <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute. <a href=#refsCSSOM>[CSSOM]</a></li>
</ol></div>
@@ -13608,8 +13577,8 @@
</ul></li>
<li><p>Provide the user with an interface that, when selected, <a href=#navigate title=navigate>navigates</a><!--DONAV meta refresh--> a <a href=#browsing-context>browsing context</a> to
- <var title="">url</var>, with the <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a> as the <a href=#source-browsing-context>source browsing
- context</a>.</li>
+ <var title="">url</var>, with the <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a> as
+ the <a href=#source-browsing-context>source browsing context</a>.</li>
<li><p>Do nothing.</li>
@@ -13684,56 +13653,46 @@
<h5 id=other-pragma-directives><span class=secno>4.2.5.4 </span>Other pragma directives</h5>
- <p><dfn id=concept-http-equiv-extensions title=concept-http-equiv-extensions>Extensions to the
- predefined set of pragma directives</dfn> may, under certain
- conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki
- PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
+ <p><dfn id=concept-http-equiv-extensions title=concept-http-equiv-extensions>Extensions to the predefined set of pragma
+ directives</dfn> may, under certain conditions, be registered in the <a href=http://wiki.whatwg.org/wiki/PragmaExtensions>WHATWG Wiki PragmaExtensions page</a>. <a href=#refsWHATWGWIKI>[WHATWGWIKI]</a></p>
- <p>Such extensions must use a name that is identical to an HTTP
- header registered in the Permanent Message Header Field Registry,
- and must have behavior identical to that described for the HTTP
+ <p>Such extensions must use a name that is identical to an HTTP header registered in the Permanent
+ Message Header Field Registry, and must have behavior identical to that described for the HTTP
header. <a href=#refsIANAPERMHEADERS>[IANAPERMHEADERS]</a></p>
- <p>Pragma directives corresponding to headers describing metadata,
- or not requiring specific user agent processing, must not be
- registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma
- directives corresponding to headers that affect the HTTP processing
- model (e.g. caching) must not be registered, as they would result in
- HTTP-level behavior being different for user agents that implement
- HTML than for user agents that do not.</p>
+ <p>Pragma directives corresponding to headers describing metadata, or not requiring specific user
+ agent processing, must not be registered; instead, use <a href=#concept-meta-extensions title=concept-meta-extensions>metadata names</a>. Pragma directives corresponding to headers
+ that affect the HTTP processing model (e.g. caching) must not be registered, as they would result
+ in HTTP-level behavior being different for user agents that implement HTML than for user agents
+ that do not.</p>
- <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
- any time to add a pragma directive satisfying these conditions. Such
- registrations must specify the following information:</p>
+ <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at any time to add a pragma
+ directive satisfying these conditions. Such registrations must specify the following
+ information:</p>
<dl><dt>Keyword</dt>
- <dd><p>The actual name being defined. The name must match a
- previously-registered HTTP name with the same
- requirements.</dd>
+ <dd><p>The actual name being defined. The name must match a previously-registered HTTP name with
+ the same requirements.</dd>
<dt>Brief description</dt>
- <dd><p>A short non-normative description of the purpose of the
- pragma directive.</dd>
+ <dd><p>A short non-normative description of the purpose of the pragma directive.</dd>
<dt>Specification</dt>
- <dd>A link to the specification defining the corresponding HTTP
- header.</dd>
+ <dd>A link to the specification defining the corresponding HTTP header.</dd>
</dl><div class=impl>
- <p>Conformance checkers must use the information given on the WHATWG
- Wiki PragmaExtensions page to establish if a value is allowed or
- not: values defined in this specification or listed on the
- aforementioned page must be accepted, whereas values not listed in
- either this specification or on the aforementioned page must be
- rejected as invalid. Conformance checkers may cache this information
- (e.g. for performance reasons or to avoid the use of unreliable
- network connectivity).</p>
+ <p>Conformance checkers must use the information given on the WHATWG Wiki PragmaExtensions page to
+ establish if a value is allowed or not: values defined in this specification or listed on the
+ aforementioned page must be accepted, whereas values not listed in either this specification or on
+ the aforementioned page must be rejected as invalid. Conformance checkers may cache this
+ information (e.g. for performance reasons or to avoid the use of unreliable network
+ connectivity).</p>
</div>
@@ -13882,26 +13841,23 @@
};
<a href=#htmlstyleelement>HTMLStyleElement</a> implements <a href=#linkstyle>LinkStyle</a>;</pre>
</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-style-element>style</a></code> element allows authors to embed style
- information in their documents. The <code><a href=#the-style-element>style</a></code> element is
- one of several inputs to the <a href=#styling>styling processing
- model</a>. The element does not <a href=#represents title=represents>represent</a> content for the user.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-style-element>style</a></code> element allows authors to embed style information in their documents.
+ The <code><a href=#the-style-element>style</a></code> element is one of several inputs to the <a href=#styling>styling processing
+ model</a>. The element does not <a href=#represents title=represents>represent</a> content for the
+ user.</p>
- <p>The <dfn id=attr-style-type title=attr-style-type><code>type</code></dfn>
- attribute gives the styling language. If the attribute is present,
- its value must be a <a href=#valid-mime-type>valid MIME type</a> that designates a
- styling language. The <code title="">charset</code> parameter must
- not be specified. The default value for the <code title=attr-style-type><a href=#attr-style-type>type</a></code> attribute, which is used if the
- attribute is absent, is "<code title="">text/css</code>". <a href=#refsRFC2318>[RFC2318]</a></p>
+ <p>The <dfn id=attr-style-type title=attr-style-type><code>type</code></dfn> attribute gives the styling language.
+ If the attribute is present, its value must be a <a href=#valid-mime-type>valid MIME type</a> that designates a
+ styling language. The <code title="">charset</code> parameter must not be specified. The default
+ value for the <code title=attr-style-type><a href=#attr-style-type>type</a></code> attribute, which is used if the attribute
+ is absent, is "<code title="">text/css</code>". <a href=#refsRFC2318>[RFC2318]</a></p>
<div class=impl>
- <!-- similar paragraph is also present in the <script> section -->
- <p>When examining types to determine if they support the language,
- user agents must not ignore unknown MIME parameters — types
- with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown
- parameter for the purpose of comparing <a href=#mime-type title="MIME type">MIME
- types</a> here.</p>
+ <!-- similar paragraph is also present in the <script> section --> <p>When examining types to
+ determine if they support the language, user agents must not ignore unknown MIME parameters
+ — types with unknown parameters must be assumed to be unsupported. The <code title="">charset</code> parameter must be treated as an unknown parameter for the purpose of
+ comparing <a href=#mime-type title="MIME type">MIME types</a> here.</p>
</div>
@@ -13927,15 +13883,15 @@
rooted at the <code><a href=#the-style-element>style</a></code> element's parent element, as opposed to the whole
<code><a href=#document>Document</a></code>.</p>
-<!--CLEANUP-->
<p>If the <code title=attr-style-scoped><a href=#attr-style-scoped>scoped</a></code> attribute is present and the element has a
- parent element, then the <code><a href=#the-style-element>style</a></code> element must precede any <a href=#flow-content>flow
- content</a> in its parent element other than <a href=#inter-element-whitespace>inter-element whitespace</a> and other <code><a href=#the-style-element>style</a></code> elements, and the
- parent element's content model must not have a <a href=#transparent>transparent</a> component.</p>
+ parent element, then the <code><a href=#the-style-element>style</a></code> element must precede any <a href=#flow-content>flow content</a> in
+ its parent element other than <a href=#inter-element-whitespace>inter-element whitespace</a> and other <code><a href=#the-style-element>style</a></code>
+ elements, and the parent element's content model must not have a <a href=#transparent>transparent</a>
+ component.</p>
- <p class=note>This implies that scoped <code><a href=#the-style-element>style</a></code> elements
- cannot be children of, e.g., <code><a href=#the-a-element>a</a></code> or <code><a href=#the-ins-element>ins</a></code> elements,
- even when those are used as <a href=#flow-content>flow content</a> containers.</p>
+ <p class=note>This implies that scoped <code><a href=#the-style-element>style</a></code> elements cannot be children of, e.g.,
+ <code><a href=#the-a-element>a</a></code> or <code><a href=#the-ins-element>ins</a></code> elements, even when those are used as <a href=#flow-content>flow content</a>
+ containers.</p>
<p class=note>A <code><a href=#the-style-element>style</a></code> element <em>without</em> a <code title=attr-style-scoped><a href=#attr-style-scoped>scoped</a></code> attribute is restricted to appearing in the
<code><a href=#the-head-element>head</a></code> of the document.</p>
@@ -13964,22 +13920,18 @@
<pre>B b|\\0{0,4}(42|62)(\r\n|[ \t\r\n\f])?
@{G}{L}{O}{B}{A}{L} {return GLOBAL_SYM;}</pre>
- <p>Simple selectors in rule sets prefixed by the <code title="">@global</code> @-rule in scoped CSS resources must be
- processed in the same way as normal rule sets in non-scoped CSS
+ <p>Simple selectors in rule sets prefixed by the <code title="">@global</code> @-rule in scoped
+ CSS resources must be processed in the same way as normal rule sets in non-scoped CSS
resources.</p>
- <p>Simple selectors in scoped CSS resources that are not prefixed by
- an <code title="">@global</code> @-rule must only match the
- <code><a href=#the-style-element>style</a></code> element's parent element (if any), and that
- element's descendants.</p>
+ <p>Simple selectors in scoped CSS resources that are not prefixed by an <code title="">@global</code> @-rule must only match the <code><a href=#the-style-element>style</a></code> element's parent element (if
+ any), and that element's descendants.</p>
- <p>For scoped CSS resources, the effect of other @-rules must be
- scoped to either the scoped sheet and its subresources or to the
- subtree rooted at the <code><a href=#the-style-element>style</a></code> element's parent (if any),
- even if the @-rule in question would ordinarily apply to all style
- sheets that affect the <code><a href=#document>Document</a></code>, or to all nodes in the
- <code><a href=#document>Document</a></code>. Any '@page' rules in scoped CSS resources
- must be ignored.</p>
+ <p>For scoped CSS resources, the effect of other @-rules must be scoped to either the scoped sheet
+ and its subresources or to the subtree rooted at the <code><a href=#the-style-element>style</a></code> element's parent (if any),
+ even if the @-rule in question would ordinarily apply to all style sheets that affect the
+ <code><a href=#document>Document</a></code>, or to all nodes in the <code><a href=#document>Document</a></code>. Any '@page' rules in scoped
+ CSS resources must be ignored.</p>
<p class=example>For example, an '@font-face' rule defined in a scoped style sheet would only
define the font for the purposes of elements in the scoped section; the font would not be used for
@@ -13990,20 +13942,18 @@
<hr></div>
<p id=title-on-style>The <dfn id=attr-style-title title=attr-style-title><code>title</code></dfn> attribute on
- <code><a href=#the-style-element>style</a></code> elements defines <a href=#alternative-style-sheet-sets>alternative style sheet
- sets</a>. If the <code><a href=#the-style-element>style</a></code> element has no <code title=attr-style-title><a href=#attr-style-title>title</a></code> attribute, then it has no
- title; the <code title=attr-title><a href=#attr-title>title</a></code> attribute of
- ancestors does not apply to the <code><a href=#the-style-element>style</a></code> element. <a href=#refsCSSOM>[CSSOM]</a></p>
+ <code><a href=#the-style-element>style</a></code> elements defines <a href=#alternative-style-sheet-sets>alternative style sheet sets</a>. If the
+ <code><a href=#the-style-element>style</a></code> element has no <code title=attr-style-title><a href=#attr-style-title>title</a></code> attribute, then it
+ has no title; the <code title=attr-title><a href=#attr-title>title</a></code> attribute of ancestors does not apply to
+ the <code><a href=#the-style-element>style</a></code> element. <a href=#refsCSSOM>[CSSOM]</a></p>
- <p class=note>The <code title=attr-style-title><a href=#attr-style-title>title</a></code>
- attribute on <code><a href=#the-style-element>style</a></code> elements, like the <code title=attr-link-title><a href=#attr-link-title>title</a></code> attribute on <code><a href=#the-link-element>link</a></code>
+ <p class=note>The <code title=attr-style-title><a href=#attr-style-title>title</a></code> attribute on <code><a href=#the-style-element>style</a></code>
+ elements, like the <code title=attr-link-title><a href=#attr-link-title>title</a></code> attribute on <code><a href=#the-link-element>link</a></code>
elements, differs from the global <code title=attr-title><a href=#attr-title>title</a></code> attribute in that a
- <code><a href=#the-style-element>style</a></code> block without a title does not inherit the title
- of the parent element: it merely has no title.</p>
+ <code><a href=#the-style-element>style</a></code> block without a title does not inherit the title of the parent element: it
+ merely has no title.</p>
- <p>The <code><a href=#textcontent>textContent</a></code> of a <code><a href=#the-style-element>style</a></code> element must
- match the <code title="">style</code> production in the following
- ABNF, the character set for which is Unicode. <a href=#refsABNF>[ABNF]</a></p>
+ <p>The <code><a href=#textcontent>textContent</a></code> of a <code><a href=#the-style-element>style</a></code> element must match the <code title="">style</code> production in the following ABNF, the character set for which is Unicode. <a href=#refsABNF>[ABNF]</a></p>
<pre>style = no-c-start *( c-start no-c-end c-end no-c-start )
no-c-start = < any string that doesn't contain a substring that matches c-start >
@@ -14022,73 +13972,58 @@
<div class=impl>
- <p>All descendant elements must be processed, according to their
- semantics, before the <code><a href=#the-style-element>style</a></code> element itself is
- evaluated. For styling languages that consist of pure text (as
- opposed to XML), user agents must evaluate <code><a href=#the-style-element>style</a></code>
- elements by passing the concatenation of the contents of all the
- <code><a href=#text>Text</a></code> nodes that are children of the
- <code><a href=#the-style-element>style</a></code> element (not any other nodes such as comments or
- elements), in <a href=#tree-order>tree order</a>, to the style system. For
- XML-based styling languages, user agents must pass all the child
- nodes of the <code><a href=#the-style-element>style</a></code> element to the style system.</p>
+ <p>All descendant elements must be processed, according to their semantics, before the
+ <code><a href=#the-style-element>style</a></code> element itself is evaluated. For styling languages that consist of pure text
+ (as opposed to XML), user agents must evaluate <code><a href=#the-style-element>style</a></code> elements by passing the
+ concatenation of the contents of all the <code><a href=#text>Text</a></code> nodes that are children of the
+ <code><a href=#the-style-element>style</a></code> element (not any other nodes such as comments or elements), in <a href=#tree-order>tree
+ order</a>, to the style system. For XML-based styling languages, user agents must pass all the
+ child nodes of the <code><a href=#the-style-element>style</a></code> element to the style system.</p>
- <p>All <a href=#url title=URL>URLs</a> found by the styling language's
- processor must be <a href=#resolve-a-url title="resolve a url">resolved</a>,
- relative to the element (or as defined by the styling language),
- when the processor is invoked.<!-- so dynamic changes to the base
- URL don't affect the CSS --></p>
+ <p>All <a href=#url title=URL>URLs</a> found by the styling language's processor must be <a href=#resolve-a-url title="resolve a url">resolved</a>, relative to the element (or as defined by the styling
+ language), when the processor is invoked.<!-- so dynamic changes to the base URL don't affect the
+ CSS --></p>
<!-- the next few paragraph are similar to text in the <style> section -->
- <p>Once the attempts to obtain the style sheet's <a href=#critical-subresources>critical
- subresources</a>, if any, are complete, or, if the style sheet
- has no <a href=#critical-subresources>critical subresources</a>, once the style sheet has
- been parsed and processed, the user agent must, if the loads were
- successful or there were none, <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-load>load</code> at the <code><a href=#the-style-element>style</a></code> element,
- or, if one of the style sheet's <a href=#critical-subresources>critical subresources</a>
- failed to completely load for any reason (e.g. DNS error, HTTP 404
- response, a connection being prematurely closed, unsupported
- Content-Type), <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> named <code title=event-error>error</code> at the
- <code><a href=#the-style-element>style</a></code> element. Non-network errors in processing the
- style sheet or its subresources (e.g. CSS parse errors, PNG decoding
- errors) are not failures for the purposes of this paragraph.</p>
+ <p>Once the attempts to obtain the style sheet's <a href=#critical-subresources>critical subresources</a>, if any, are
+ complete, or, if the style sheet has no <a href=#critical-subresources>critical subresources</a>, once the style sheet
+ has been parsed and processed, the user agent must, if the loads were successful or there were
+ none, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-load>load</code> at the <code><a href=#the-style-element>style</a></code> element, or, if one of the style sheet's
+ <a href=#critical-subresources>critical subresources</a> failed to completely load for any reason (e.g. DNS error, HTTP
+ 404 response, a connection being prematurely closed, unsupported Content-Type), <a href=#queue-a-task>queue a
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-error>error</code> at
+ the <code><a href=#the-style-element>style</a></code> element. Non-network errors in processing the style sheet or its
+ subresources (e.g. CSS parse errors, PNG decoding errors) are not failures for the purposes of
+ this paragraph.</p>
- <p>The <a href=#task-source>task source</a> for these <a href=#concept-task title=concept-task>tasks</a> is the <a href=#dom-manipulation-task-source>DOM manipulation task
- source</a>.</p>
+ <p>The <a href=#task-source>task source</a> for these <a href=#concept-task title=concept-task>tasks</a> is the <a href=#dom-manipulation-task-source>DOM
+ manipulation task source</a>.</p>
- <p>The element must <a href=#delay-the-load-event>delay the load event</a> of the
- element's document until all the attempts to obtain the style
- sheet's <a href=#critical-subresources>critical subresources</a>, if any, are
- complete.</p>
+ <p>The element must <a href=#delay-the-load-event>delay the load event</a> of the element's document until all the
+ attempts to obtain the style sheet's <a href=#critical-subresources>critical subresources</a>, if any, are complete.</p>
</div>
- <p class=note>This specification does not specify a style system,
- but CSS is expected to be supported by most Web browsers. <a href=#refsCSS>[CSS]</a></p>
+ <p class=note>This specification does not specify a style system, but CSS is expected to be
+ supported by most Web browsers. <a href=#refsCSS>[CSS]</a></p>
<div class=impl>
- <p>The <dfn id=dom-style-media title=dom-style-media><code>media</code></dfn>, <dfn id=dom-style-type title=dom-style-type><code>type</code></dfn> and <dfn id=dom-style-scoped title=dom-style-scoped><code>scoped</code></dfn> IDL attributes
- must <a href=#reflect>reflect</a> the respective content attributes of the
- same name.</p>
+ <p>The <dfn id=dom-style-media title=dom-style-media><code>media</code></dfn>, <dfn id=dom-style-type title=dom-style-type><code>type</code></dfn> and <dfn id=dom-style-scoped title=dom-style-scoped><code>scoped</code></dfn> IDL attributes must <a href=#reflect>reflect</a> the
+ respective content attributes of the same name.</p>
</div>
- <p>The <dfn id=dom-style-disabled title=dom-style-disabled><code>disabled</code></dfn>
- IDL attribute behaves as defined <a href=#dom-linkstyle-disabled title=dom-linkstyle-disabled>for the alternative style sheets
- DOM</a>.</p>
+ <p>The <dfn id=dom-style-disabled title=dom-style-disabled><code>disabled</code></dfn> IDL attribute behaves as
+ defined <a href=#dom-linkstyle-disabled title=dom-linkstyle-disabled>for the alternative style sheets DOM</a>.</p>
- <p>The <code><a href=#linkstyle>LinkStyle</a></code> interface is also implemented by
- this element; the <a href=#styling>styling processing model</a> defines
- how. <a href=#refsCSSOM>[CSSOM]</a></p>
+ <p>The <code><a href=#linkstyle>LinkStyle</a></code> interface is also implemented by this element; the <a href=#styling>styling
+ processing model</a> defines how. <a href=#refsCSSOM>[CSSOM]</a></p>
<div class=example>
- <p>The following document has its stress emphasis styled as bright
- red text rather than italics text, while leaving titles of works
- and Latin words in their default italics. It shows how using
+ <p>The following document has its stress emphasis styled as bright red text rather than italics
+ text, while leaving titles of works and Latin words in their default italics. It shows how using
appropriate elements enables easier restyling of documents.</p>
<pre><!DOCTYPE html>
@@ -14243,24 +14178,25 @@
<p>Scripts allow authors to add interactivity to their documents.</p>
- <p>Authors are encouraged to use declarative alternatives to
- scripting where possible, as declarative mechanisms are often more
- maintainable, and many users disable scripting.</p>
+ <p>Authors are encouraged to use declarative alternatives to scripting where possible, as
+ declarative mechanisms are often more maintainable, and many users disable scripting.</p>
<div class=example>
- <p>For example, instead of using script to show or hide a section
- to show more details, the <code><a href=#the-details-element>details</a></code> element could be
- used.</p>
+
+ <p>For example, instead of using script to show or hide a section to show more details, the
+ <code><a href=#the-details-element>details</a></code> element could be used.</p>
+
</div>
- <p>Authors are also encouraged to make their applications degrade
- gracefully in the absence of scripting support.</p>
+ <p>Authors are also encouraged to make their applications degrade gracefully in the absence of
+ scripting support.</p>
<div class=example>
- <p>For example, if an author provides a link in a table header to
- dynamically resort the table, the link could also be made to
- function without scripts by requesting the sorted table from the
+
+ <p>For example, if an author provides a link in a table header to dynamically resort the table,
+ the link could also be made to function without scripts by requesting the sorted table from the
server.</p>
+
</div>
@@ -15252,40 +15188,31 @@
<p><i>This section is non-normative.</i></p>
- <p>This specification does not define how XSLT interacts with the
- <code><a href=#the-script-element>script</a></code> element. However, in the absence of another
- specification actually defining this, here are some guidelines for
- implementors, based on existing implementations:</p>
+ <p>This specification does not define how XSLT interacts with the <code><a href=#the-script-element>script</a></code> element.
+ However, in the absence of another specification actually defining this, here are some guidelines
+ for implementors, based on existing implementations:</p>
- <ul><li><p>When an XSLT transformation program is triggered by an <code title=""><?xml-stylesheet?></code> processing instruction and
- the browser implements a direct-to-DOM transformation,
- <code><a href=#the-script-element>script</a></code> elements created by the XSLT processor need to
- be marked <a href=#parser-inserted>"parser-inserted"</a> and run in document order
- (modulo scripts marked <code title=attr-script-defer><a href=#attr-script-defer>defer</a></code>
- or <code title=attr-script-async><a href=#attr-script-async>async</a></code>), asynchronously
- while the transformation is occurring.</li>
+ <ul><li><p>When an XSLT transformation program is triggered by an <code title=""><?xml-stylesheet?></code> processing instruction and the browser implements a
+ direct-to-DOM transformation, <code><a href=#the-script-element>script</a></code> elements created by the XSLT processor need to
+ be marked <a href=#parser-inserted>"parser-inserted"</a> and run in document order (modulo scripts marked <code title=attr-script-defer><a href=#attr-script-defer>defer</a></code> or <code title=attr-script-async><a href=#attr-script-async>async</a></code>),
+ asynchronously while the transformation is occurring.</li>
- <li><p>The <code title=dom-XSLTProcessor-transformToDocument>XSLTProcessor.transformToDocument()</code>
- method adds elements to a <code><a href=#document>Document</a></code> that is not in a
- <a href=#browsing-context>browsing context</a>, and, accordingly, any
- <code><a href=#the-script-element>script</a></code> elements they create need to have their
- <a href=#already-started>"already started"</a> flag set in the <a href=#prepare-a-script>prepare a
- script</a> algorithm and never get executed (<a href=#concept-bc-noscript title=concept-bc-noscript>scripting is disabled</a>). Such
- <code><a href=#the-script-element>script</a></code> elements still need to be marked
- <a href=#parser-inserted>"parser-inserted"</a>, though, such that their <code title=dom-script-async><a href=#dom-script-async>async</a></code> IDL attribute will return
- false in the absence of an <code title=attr-script-async><a href=#attr-script-async>async</a></code> content attribute.</li>
+ <li><p>The <code title=dom-XSLTProcessor-transformToDocument>XSLTProcessor.transformToDocument()</code> method
+ adds elements to a <code><a href=#document>Document</a></code> that is not in a <a href=#browsing-context>browsing context</a>, and,
+ accordingly, any <code><a href=#the-script-element>script</a></code> elements they create need to have their <a href=#already-started>"already
+ started"</a> flag set in the <a href=#prepare-a-script>prepare a script</a> algorithm and never get executed
+ (<a href=#concept-bc-noscript title=concept-bc-noscript>scripting is disabled</a>). Such <code><a href=#the-script-element>script</a></code>
+ elements still need to be marked <a href=#parser-inserted>"parser-inserted"</a>, though, such that their <code title=dom-script-async><a href=#dom-script-async>async</a></code> IDL attribute will return false in the absence of an <code title=attr-script-async><a href=#attr-script-async>async</a></code> content attribute.</li>
- <li><p>The <code title=dom-XSLTProcessor-transformToFragment>XSLTProcessor.transformToFragment()</code>
- method needs to create a fragment that is equivalent to one built
- manually by creating the elements using <code title=dom-document-createElementNS><a href=#dom-document-createelementns>document.createElementNS()</a></code>.
- For instance, it needs to create <code><a href=#the-script-element>script</a></code> elements that
- aren't <a href=#parser-inserted>"parser-inserted"</a> and that don't have their
- <a href=#already-started>"already started"</a> flag set, so that they will execute
- when the fragment is inserted into a document.</li>
+ <li><p>The <code title=dom-XSLTProcessor-transformToFragment>XSLTProcessor.transformToFragment()</code> method
+ needs to create a fragment that is equivalent to one built manually by creating the elements
+ using <code title=dom-document-createElementNS><a href=#dom-document-createelementns>document.createElementNS()</a></code>. For instance,
+ it needs to create <code><a href=#the-script-element>script</a></code> elements that aren't <a href=#parser-inserted>"parser-inserted"</a> and
+ that don't have their <a href=#already-started>"already started"</a> flag set, so that they will execute when the
+ fragment is inserted into a document.</li>
- </ul><p>The main distinction between the first two cases and the last
- case is that the first two operate on <code><a href=#document>Document</a></code>s and the
- last operates on a fragment.</p>
+ </ul><p>The main distinction between the first two cases and the last case is that the first two
+ operate on <code><a href=#document>Document</a></code>s and the last operates on a fragment.</p>
</div>
@@ -15310,120 +15237,96 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-noscript-element>noscript</a></code> element <a href=#represents>represents</a> nothing
- if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>, and
- <a href=#represents>represents</a> its children if <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a>. It is used
- to present different markup to user agents that support scripting
- and those that don't support scripting, by affecting how the
- document is parsed.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-noscript-element>noscript</a></code> element <a href=#represents>represents</a> nothing if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>, and <a href=#represents>represents</a> its children if
+ <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a>. It is used to present different
+ markup to user agents that support scripting and those that don't support scripting, by affecting
+ how the document is parsed.</p>
- <p>When used in <a href=#html-documents>HTML documents</a>, the allowed content
- model is as follows:</p>
+ <p>When used in <a href=#html-documents>HTML documents</a>, the allowed content model is as follows:</p>
- <dl><dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dl><dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is
+ disabled</a> for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
- <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only
- <code><a href=#the-link-element>link</a></code>, <code><a href=#the-style-element>style</a></code>, and <code><a href=#the-meta-element>meta</a></code>
- elements.</dd>
+ <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only <code><a href=#the-link-element>link</a></code>, <code><a href=#the-style-element>style</a></code>,
+ and <code><a href=#the-meta-element>meta</a></code> elements.</dd>
- <dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dt>In a <code><a href=#the-head-element>head</a></code> element, if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>
+ for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
- <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text,
- except that invoking the <a href=#html-fragment-parsing-algorithm>HTML fragment parsing
- algorithm</a> <!-- (which disables <script> execution) --> with
- the <code><a href=#the-noscript-element>noscript</a></code> element as the <var title=concept-frag-parse-context><a href=#concept-frag-parse-context>context</a></var> element and the
- text contents as the <var title="">input</var> must result in a
- list of nodes that consists only of <code><a href=#the-link-element>link</a></code>,
- <code><a href=#the-style-element>style</a></code>, and <code><a href=#the-meta-element>meta</a></code> elements that would be
- conforming if they were children of the <code><a href=#the-noscript-element>noscript</a></code>
- element, and no <a href=#parse-error title="parse error">parse
- errors</a>.</dd>
+ <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text, except that invoking the
+ <a href=#html-fragment-parsing-algorithm>HTML fragment parsing algorithm</a> <!-- (which disables <script> execution) --> with
+ the <code><a href=#the-noscript-element>noscript</a></code> element as the <var title=concept-frag-parse-context><a href=#concept-frag-parse-context>context</a></var>
+ element and the text contents as the <var title="">input</var> must result in a list of nodes
+ that consists only of <code><a href=#the-link-element>link</a></code>, <code><a href=#the-style-element>style</a></code>, and <code><a href=#the-meta-element>meta</a></code> elements that
+ would be conforming if they were children of the <code><a href=#the-noscript-element>noscript</a></code> element, and no <a href=#parse-error title="parse error">parse errors</a>.</dd>
- <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is disabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-noscript title=concept-n-noscript>scripting is
+ disabled</a> for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
- <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element's content model is
- <a href=#transparent>transparent</a>, with the additional restriction that a
- <code><a href=#the-noscript-element>noscript</a></code> element must not have a <code><a href=#the-noscript-element>noscript</a></code>
- element as an ancestor (that is, <code><a href=#the-noscript-element>noscript</a></code> can't be
- nested).</dd>
+ <dd><p>The <code><a href=#the-noscript-element>noscript</a></code> element's content model is <a href=#transparent>transparent</a>, with the
+ additional restriction that a <code><a href=#the-noscript-element>noscript</a></code> element must not have a <code><a href=#the-noscript-element>noscript</a></code>
+ element as an ancestor (that is, <code><a href=#the-noscript-element>noscript</a></code> can't be nested).</dd>
- <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-script title=concept-n-script>scripting is enabled</a> for the
- <code><a href=#the-noscript-element>noscript</a></code> element</dt>
+ <dt>Outside of <code><a href=#the-head-element>head</a></code> elements, if <a href=#concept-n-script title=concept-n-script>scripting is
+ enabled</a> for the <code><a href=#the-noscript-element>noscript</a></code> element</dt>
<dd>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text,
- except that the text must be such that running the following
- algorithm results in a conforming document with no
- <code><a href=#the-noscript-element>noscript</a></code> elements and no <code><a href=#the-script-element>script</a></code>
- elements, and such that no step in the algorithm causes an
- <a href=#html-parser>HTML parser</a> to flag a <a href=#parse-error>parse error</a>:</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element must contain only text, except that the text must be such
+ that running the following algorithm results in a conforming document with no
+ <code><a href=#the-noscript-element>noscript</a></code> elements and no <code><a href=#the-script-element>script</a></code> elements, and such that no step in the
+ algorithm causes an <a href=#html-parser>HTML parser</a> to flag a <a href=#parse-error>parse error</a>:</p>
- <ol><li>Remove every <code><a href=#the-script-element>script</a></code> element from the
- document.</li>
+ <ol><li>Remove every <code><a href=#the-script-element>script</a></code> element from the document.</li>
- <li>Make a list of every <code><a href=#the-noscript-element>noscript</a></code> element in the
- document. For every <code><a href=#the-noscript-element>noscript</a></code> element in that list,
- perform the following steps:
+ <li>Make a list of every <code><a href=#the-noscript-element>noscript</a></code> element in the document. For every
+ <code><a href=#the-noscript-element>noscript</a></code> element in that list, perform the following steps:
- <ol><li>Let the <var title="">parent element</var> be the parent
- element of the <code><a href=#the-noscript-element>noscript</a></code> element.</li>
+ <ol><li>Let the <var title="">parent element</var> be the parent element of the
+ <code><a href=#the-noscript-element>noscript</a></code> element.</li>
- <li>Take all the children of the <var title="">parent element</var>
- that come before the <code><a href=#the-noscript-element>noscript</a></code> element, and call these
- elements <var title="">the before children</var>.</li>
+ <li>Take all the children of the <var title="">parent element</var> that come before the
+ <code><a href=#the-noscript-element>noscript</a></code> element, and call these elements <var title="">the before
+ children</var>.</li>
- <li>Take all the children of the <var title="">parent element</var>
- that come <em>after</em> the <code><a href=#the-noscript-element>noscript</a></code> element, and
- call these elements <var title="">the after children</var>.</li>
+ <li>Take all the children of the <var title="">parent element</var> that come <em>after</em>
+ the <code><a href=#the-noscript-element>noscript</a></code> element, and call these elements <var title="">the after
+ children</var>.</li>
- <li>Let <var title="">s</var> be the concatenation of all the
- <code><a href=#text>Text</a></code> node children of the <code><a href=#the-noscript-element>noscript</a></code>
- element.</li>
+ <li>Let <var title="">s</var> be the concatenation of all the <code><a href=#text>Text</a></code> node children
+ of the <code><a href=#the-noscript-element>noscript</a></code> element.</li>
- <li>Set the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code>
- attribute of the <var title="">parent element</var> to the value
- of <var title="">s</var>. (This, as a side-effect, causes the
- <code><a href=#the-noscript-element>noscript</a></code> element to be removed from the
- document.)</li>
+ <li>Set the <code title=dom-innerHTML><a href=#dom-innerhtml>innerHTML</a></code> attribute of the <var title="">parent element</var> to the value of <var title="">s</var>. (This, as a side-effect,
+ causes the <code><a href=#the-noscript-element>noscript</a></code> element to be removed from the document.)</li>
- <li>Insert <var title="">the before children</var> at the start of
- the <var title="">parent element</var>, preserving their original
- relative order.</li>
+ <li>Insert <var title="">the before children</var> at the start of the <var title="">parent
+ element</var>, preserving their original relative order.</li>
- <li>Insert <var title="">the after children</var> at the end of the
- <var title="">parent element</var>, preserving their original
- relative order.</li>
+ <li>Insert <var title="">the after children</var> at the end of the <var title="">parent
+ element</var>, preserving their original relative order.</li>
</ol></li>
</ol></dd>
- </dl><p class=note>All these contortions are required because, for
- historical reasons, the <code><a href=#the-noscript-element>noscript</a></code> element is handled
- differently by the <a href=#html-parser>HTML parser</a> based on whether <a href=#scripting-flag title="scripting flag">scripting was enabled or not</a> when the
- parser was invoked.</p>
+ </dl><p class=note>All these contortions are required because, for historical reasons, the
+ <code><a href=#the-noscript-element>noscript</a></code> element is handled differently by the <a href=#html-parser>HTML parser</a> based on
+ whether <a href=#scripting-flag title="scripting flag">scripting was enabled or not</a> when the parser was
+ invoked.</p>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element must not be used in <a href=#xml-documents>XML
- documents</a>.</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element must not be used in <a href=#xml-documents>XML documents</a>.</p>
- <p class=note>The <code><a href=#the-noscript-element>noscript</a></code> element is only effective
- in <a href=#syntax>the HTML syntax</a>, it has no effect in <a href=#the-xhtml-syntax>the XHTML
- syntax</a>. This is because the way it works is by essentially
- "turning off" the parser when scripts are enabled, so that the
- contents of the element are treated as pure text and not as real
- elements. XML does not define a mechanism by which to do this.</p>
+ <p class=note>The <code><a href=#the-noscript-element>noscript</a></code> element is only effective in <a href=#syntax>the HTML
+ syntax</a>, it has no effect in <a href=#the-xhtml-syntax>the XHTML syntax</a>. This is because the way it works
+ is by essentially "turning off" the parser when scripts are enabled, so that the contents of the
+ element are treated as pure text and not as real elements. XML does not define a mechanism by
+ which to do this.</p>
<div class=impl>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element has no other requirements. In
- particular, children of the <code><a href=#the-noscript-element>noscript</a></code> element are not
- exempt from <a href=#form-submission>form submission</a>, scripting, and so forth,
- even when <a href=#concept-n-script title=concept-n-script>scripting is enabled</a>
- for the element.</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element has no other requirements. In particular, children of the
+ <code><a href=#the-noscript-element>noscript</a></code> element are not exempt from <a href=#form-submission>form submission</a>, scripting, and so
+ forth, even when <a href=#concept-n-script title=concept-n-script>scripting is enabled</a> for the element.</p>
</div>
@@ -15453,17 +15356,13 @@
</noscript>
</form></pre>
- <p>When script is disabled, a button appears to do the calculation
- on the server side. When script is enabled, the value is computed
- on-the-fly instead.</p>
+ <p>When script is disabled, a button appears to do the calculation on the server side. When
+ script is enabled, the value is computed on-the-fly instead.</p>
- <p>The <code><a href=#the-noscript-element>noscript</a></code> element is a blunt
- instrument. Sometimes, scripts might be enabled, but for some
- reason the page's script might fail. For this reason, it's
- generally better to avoid using <code><a href=#the-noscript-element>noscript</a></code>, and to
- instead design the script to change the page from being a
- scriptless page to a scripted page on the fly, as in the next
- example:</p>
+ <p>The <code><a href=#the-noscript-element>noscript</a></code> element is a blunt instrument. Sometimes, scripts might be enabled,
+ but for some reason the page's script might fail. For this reason, it's generally better to avoid
+ using <code><a href=#the-noscript-element>noscript</a></code>, and to instead design the script to change the page from being a
+ scriptless page to a scripted page on the fly, as in the next example:</p>
<pre><form action="calcSquare.php">
<p>
@@ -15486,9 +15385,8 @@
</script>
</form></pre>
- <p>The above technique is also useful in XHTML, since
- <code><a href=#the-noscript-element>noscript</a></code> is not supported in <a href=#the-xhtml-syntax>the XHTML
- syntax</a>.</p>
+ <p>The above technique is also useful in XHTML, since <code><a href=#the-noscript-element>noscript</a></code> is not supported in
+ <a href=#the-xhtml-syntax>the XHTML syntax</a>.</p>
</div>
@@ -19360,7 +19258,6 @@
<div class=impl>
-<!--CLEANUP-->
<p>The <code title=attr-hyperlink-href><a href=#attr-hyperlink-href>href</a></code>, <code title=attr-hyperlink-target><a href=#attr-hyperlink-target>target</a></code>, <code title=attr-hyperlink-download><a href=#attr-hyperlink-download>download</a></code>, and <code title=attr-hyperlink-ping><a href=#ping>ping</a></code>
attributes affect what happens when users <a href=#following-hyperlinks title="following hyperlinks">follow
hyperlinks</a> or <a href=#downloading-hyperlinks title="downloading hyperlinks">download hyperlinks</a> created using
@@ -19499,56 +19396,49 @@
<dd><a href=#global-attributes>Global attributes</a></dd>
<dt><a href=#element-dfn-dom title=element-dfn-dom>DOM interface</a>:</dt><!--TOPIC:DOM APIs-->
<dd>Uses <code><a href=#htmlelement>HTMLElement</a></code>.</dd>
- </dl><!--TOPIC:HTML--><p>The <code><a href=#the-em-element>em</a></code> element <a href=#represents>represents</a> stress
- emphasis of its contents.</p>
+ </dl><!--TOPIC:HTML--><p>The <code><a href=#the-em-element>em</a></code> element <a href=#represents>represents</a> stress emphasis of its contents.</p>
- <p>The level of stress that a particular piece of content has is
- given by its number of ancestor <code><a href=#the-em-element>em</a></code> elements.</p>
+ <p>The level of stress that a particular piece of content has is given by its number of ancestor
+ <code><a href=#the-em-element>em</a></code> elements.</p>
- <p>The placement of stress emphasis changes the meaning of the
- sentence. The element thus forms an integral part of the content.
- The precise way in which stress is used in this way depends on the
+ <p>The placement of stress emphasis changes the meaning of the sentence. The element thus forms an
+ integral part of the content. The precise way in which stress is used in this way depends on the
language.</p>
<div class=example>
- <p>These examples show how changing the stress emphasis changes the
- meaning. First, a general statement of fact, with no stress:</p>
+ <p>These examples show how changing the stress emphasis changes the meaning. First, a general
+ statement of fact, with no stress:</p>
<pre><p>Cats are cute animals.</p></pre>
- <p>By emphasizing the first word, the statement implies that the
- kind of animal under discussion is in question (maybe someone is
- asserting that dogs are cute):</p>
+ <p>By emphasizing the first word, the statement implies that the kind of animal under discussion
+ is in question (maybe someone is asserting that dogs are cute):</p>
<pre><p><em>Cats</em> are cute animals.</p></pre>
- <p>Moving the stress to the verb, one highlights that the truth of
- the entire sentence is in question (maybe someone is saying cats
- are not cute):</p>
+ <p>Moving the stress to the verb, one highlights that the truth of the entire sentence is in
+ question (maybe someone is saying cats are not cute):</p>
<pre><p>Cats <em>are</em> cute animals.</p></pre>
- <p>By moving it to the adjective, the exact nature of the cats
- is reasserted (maybe someone suggested cats were <em>mean</em>
- animals):</p>
+ <p>By moving it to the adjective, the exact nature of the cats is reasserted (maybe someone
+ suggested cats were <em>mean</em> animals):</p>
<pre><p>Cats are <em>cute</em> animals.</p></pre>
- <p>Similarly, if someone asserted that cats were vegetables,
- someone correcting this might emphasize the last word:</p>
+ <p>Similarly, if someone asserted that cats were vegetables, someone correcting this might
+ emphasize the last word:</p>
<pre><p>Cats are cute <em>animals</em>.</p></pre>
- <p>By emphasizing the entire sentence, it becomes clear that the
- speaker is fighting hard to get the point across. This kind of
- stress emphasis also typically affects the punctuation, hence the
+ <p>By emphasizing the entire sentence, it becomes clear that the speaker is fighting hard to get
+ the point across. This kind of stress emphasis also typically affects the punctuation, hence the
exclamation mark here.</p>
<pre><p><em>Cats are cute animals!</em></p></pre>
- <p>Anger mixed with emphasizing the cuteness could lead to markup
- such as:</p>
+ <p>Anger mixed with emphasizing the cuteness could lead to markup such as:</p>
<pre><p><em>Cats are <em>cute</em> animals!</em></p></pre>
@@ -19556,14 +19446,12 @@
<div class=note>
- <p>The <code><a href=#the-em-element>em</a></code> element isn't a generic "italics"
- element. Sometimes, text is intended to stand out from the rest of
- the paragraph, as if it was in a different mood or voice. For this,
+ <p>The <code><a href=#the-em-element>em</a></code> element isn't a generic "italics" element. Sometimes, text is intended to
+ stand out from the rest of the paragraph, as if it was in a different mood or voice. For this,
the <code><a href=#the-i-element>i</a></code> element is more appropriate.</p>
- <p>The <code><a href=#the-em-element>em</a></code> element also isn't intended to convey
- importance; for that purpose, the <code><a href=#the-strong-element>strong</a></code> element is
- more appropriate.</p>
+ <p>The <code><a href=#the-em-element>em</a></code> element also isn't intended to convey importance; for that purpose, the
+ <code><a href=#the-strong-element>strong</a></code> element is more appropriate.</p>
<!--
@@ -91272,7 +91160,7 @@
</dd>
- <dt id=adoptionAgency>An end tag whose tag name is one of: "a",
+ <dt>An end tag whose tag name is one of: "a",
"b", "big", "code", "em", "font", "i", "nobr", "s", "small",
"strike", "strong", "tt", "u"</dt>
<dd>
@@ -91771,7 +91659,7 @@
<li><p>Pop elements from the <a href=#stack-of-open-elements>stack of open elements</a> until a <code><a href=#the-p-element>p</a></code> element
has been popped from the stack.</li>
- </ol><p>The <dfn id=adoption-agency-algorithm>adoption agency algorithm</dfn>, which takes as its only argument a tag name <var title="">subject</var> for which the algorithm is being run, consists of the following steps:</p>
+ </ol><p id=adoptionAgency>The <dfn id=adoption-agency-algorithm>adoption agency algorithm</dfn>, which takes as its only argument a tag name <var title="">subject</var> for which the algorithm is being run, consists of the following steps:</p>
<!--CLEANUP-->
<ol><li><p>Let <var title="">outer loop counter</var> be
Modified: source
===================================================================
--- source 2013-07-30 21:45:54 UTC (rev 8104)
+++ source 2013-07-31 19:11:24 UTC (rev 8105)
@@ -9728,7 +9728,6 @@
the following list:</p>
<dl class="switch">
-<!--CLEANUP-->
<dt>If the element's <code title="attr-dir">dir</code> attribute is in the <span
@@ -9739,8 +9738,8 @@
<dt>If the element is an <code>input</code> element whose <code
title="attr-input-type">type</code> attribute is in the <span
- title="attr-input-type-tel">Telephone</span> state, and the <code
- title="attr-dir">dir</code> attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
+ title="attr-input-type-tel">Telephone</span> state, and the <code title="attr-dir">dir</code>
+ attribute is not in a defined state (i.e. it is not present or has an invalid value)</dt>
<dd><p><span>The directionality</span> of the element is '<span
title="concept-ltr">ltr</span>'.</p></dd>
@@ -9754,13 +9753,11 @@
<dt>If the element is an <code>input</code> element whose <code
title="attr-input-type">type</code> attribute is in the <span
- title="attr-input-type-text">Text</span>, <span
- title="attr-input-type-search">Search</span>, <span
- title="attr-input-type-tel">Telephone</span>, <span
- title="attr-input-type-url">URL</span>, or <span
- title="attr-input-type-email">E-mail</span> state, and the <code
- title="attr-dir">dir</code> attribute is in the <span
- title="attr-dir-auto-state">auto</span> state</dt>
+ title="attr-input-type-text">Text</span>, <span title="attr-input-type-search">Search</span>,
+ <span title="attr-input-type-tel">Telephone</span>, <span title="attr-input-type-url">URL</span>,
+ or <span title="attr-input-type-email">E-mail</span> state, and the <code
+ title="attr-dir">dir</code> attribute is in the <span title="attr-dir-auto-state">auto</span>
+ state</dt>
<dt>If the element is a <code>textarea</code> element and the <code title="attr-dir">dir</code>
attribute is in the <span title="attr-dir-auto-state">auto</span> state</dt>
@@ -9770,8 +9767,8 @@
<p>If the element's <span title="concept-fe-value">value</span> contains a character of
bidirectional character type AL or R, and there is no character of bidirectional character type
L anywhere before it in the element's <span title="concept-fe-value">value</span>, then
- <span>the directionality</span> of the element is '<span title="concept-rtl">rtl</span>'.
- <a href="#refsBIDI">[BIDI]</a></p>
+ <span>the directionality</span> of the element is '<span title="concept-rtl">rtl</span>'. <a
+ href="#refsBIDI">[BIDI]</a></p>
<p>Otherwise, if the element's <span title="concept-fe-value">value</span> is not the empty
string, or if the element is a <span>root element</span>, <span>the directionality</span> of the
@@ -9884,7 +9881,8 @@
</dl>
- <p>The following attributes are <dfn title="directionality-capable attribute">directionality-capable attributes</dfn>:</p>
+ <p>The following attributes are <dfn title="directionality-capable
+ attribute">directionality-capable attributes</dfn>:</p>
<ul class="brief">
<li><code title="attr-th-abbr">abbr</code> on <code>th</code> elements</li>
@@ -10351,11 +10349,12 @@
<h4><dfn>Content models</dfn></h4>
<p>Each element defined in this specification has a content model: a description of the element's
- expected <span title="concept-html-contents">contents</span>. An <span title="HTML elements">HTML element</span> must have contents that
- match the requirements described in the element's content model. The <dfn title="concept-html-contents">contents</dfn> of an element are
- its children in the DOM, except for <code>template</code> elements, where the children are those
- in the <span>template contents</span> (a separate <code>DocumentFragment</code> assigned to the
- element when the element is created).</p>
+ expected <span title="concept-html-contents">contents</span>. An <span title="HTML elements">HTML
+ element</span> must have contents that match the requirements described in the element's content
+ model. The <dfn title="concept-html-contents">contents</dfn> of an element are its children in the
+ DOM, except for <code>template</code> elements, where the children are those in the <span>template
+ contents</span> (a separate <code>DocumentFragment</code> assigned to the element when the element
+ is created).</p>
<p>The <span title="space character">space characters</span> are always allowed between elements.
User agents represent these characters between elements in the source markup as <code>Text</code>
@@ -12468,7 +12467,6 @@
<h4><code title="dom-document-writeln">document.writeln()</code></h4>
-<!--CLEANUP-->
<dl class="domintro">
<dt><var title="">document</var> . <code title="dom-document-writeln">writeln</code>(<var title="">text</var>...)</dt>
@@ -12632,7 +12630,6 @@
<h4 id="the-title-element">The <dfn><code>title</code></dfn> element</h4>
-<!--CLEANUP-->
<dl class="element">
<dt><span title="element-dfn-categories">Categories</span>:</dt>
@@ -12651,16 +12648,13 @@
</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>title</code> element <span>represents</span> the
- document's title or name. Authors should use titles that identify
- their documents even when they are used out of context, for example
- in a user's history or bookmarks, or in search results. The
- document's title is often different from its first heading, since the
- first heading does not have to stand alone when taken out of
- context.</p>
+ <p>The <code>title</code> element <span>represents</span> the document's title or name. Authors
+ should use titles that identify their documents even when they are used out of context, for
+ example in a user's history or bookmarks, or in search results. The document's title is often
+ different from its first heading, since the first heading does not have to stand alone when taken
+ out of context.</p>
- <p>There must be no more than one <code>title</code> element per
- document.</p>
+ <p>There must be no more than one <code>title</code> element per document.</p>
<p>The <code>title</code> element must not be empty.</p>
@@ -12675,11 +12669,10 @@
<dd>
- <p>Returns the contents of the element, ignoring child nodes that
- aren't <code>Text</code> nodes.</p>
+ <p>Returns the contents of the element, ignoring child nodes that aren't <code>Text</code>
+ nodes.</p>
- <p>Can be set, to replace the element's children with the given
- value.</p>
+ <p>Can be set, to replace the element's children with the given value.</p>
</dd>
@@ -12687,21 +12680,18 @@
<div class="impl">
- <p>The IDL attribute <dfn
- title="dom-title-text"><code>text</code></dfn> must return a
- concatenation of the contents of all the <code>Text</code> nodes
- that are children of the <code>title</code> element (ignoring any
- other nodes such as comments or elements), in tree order. On
- setting, it must act the same way as the <code>textContent</code>
- IDL attribute.</p>
+ <p>The IDL attribute <dfn title="dom-title-text"><code>text</code></dfn> must return a
+ concatenation of the contents of all the <code>Text</code> nodes that are children of the
+ <code>title</code> element (ignoring any other nodes such as comments or elements), in tree order.
+ On setting, it must act the same way as the <code>textContent</code> IDL attribute.</p>
</div>
<!--TOPIC:HTML-->
<div class="example">
- <p>Here are some examples of appropriate titles, contrasted with
- the top-level headings that might be used on those same pages.</p>
+ <p>Here are some examples of appropriate titles, contrasted with the top-level headings that
+ might be used on those same pages.</p>
<pre> <title>Introduction to The Mating Rituals of Bees</title>
...
@@ -12709,10 +12699,9 @@
<p>This companion guide to the highly successful
<cite>Introduction to Medieval Bee-Keeping</cite> book is...</pre>
- <p>The next page might be a part of the same site. Note how the
- title describes the subject matter unambiguously, while the first
- heading assumes the reader knows what the context is and therefore
- won't wonder if the dances are Salsa or Waltz:</p>
+ <p>The next page might be a part of the same site. Note how the title describes the subject
+ matter unambiguously, while the first heading assumes the reader knows what the context is and
+ therefore won't wonder if the dances are Salsa or Waltz:</p>
<pre> <title>Dances used during bee mating rituals</title>
...
@@ -12725,12 +12714,10 @@
<div class="impl">
- <p>User agents should use the document's title when referring to the
- document in their user interface. When the contents of a
- <code>title</code> element are used in this way, <span>the
- directionality</span> of that <code>title</code> element should be
- used to set the directionality of the document's title in the user
- interface.</p>
+ <p>User agents should use the document's title when referring to the document in their user
+ interface. When the contents of a <code>title</code> element are used in this way, <span>the
+ directionality</span> of that <code>title</code> element should be used to set the directionality
+ of the document's title in the user interface.</p>
</div>
@@ -12757,58 +12744,47 @@
</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>base</code> element allows authors to specify the
- <span>document base URL</span> for the purposes of <span
- title="resolve a url">resolving relative URLs</span>, and the name
- of the default <span>browsing context</span> for the purposes of
- <span>following hyperlinks</span>. The element does not <span
- title="represents">represent</span> any content beyond this
+ <p>The <code>base</code> element allows authors to specify the <span>document base URL</span> for
+ the purposes of <span title="resolve a url">resolving relative URLs</span>, and the name of the
+ default <span>browsing context</span> for the purposes of <span>following hyperlinks</span>. The
+ element does not <span title="represents">represent</span> any content beyond this
information.</p>
- <p>There must be no more than one <code>base</code> element per
- document.</p>
+ <p>There must be no more than one <code>base</code> element per document.</p>
- <p>A <code>base</code> element must have either an <code
- title="attr-base-href">href</code> attribute, a <code
- title="attr-base-target">target</code> attribute, or both.</p>
+ <p>A <code>base</code> element must have either an <code title="attr-base-href">href</code>
+ attribute, a <code title="attr-base-target">target</code> attribute, or both.</p>
- <p>The <dfn title="attr-base-href"><code>href</code></dfn> content
- attribute, if specified, must contain a <span>valid URL potentially
- surrounded by spaces</span>.</p>
+ <p>The <dfn title="attr-base-href"><code>href</code></dfn> content attribute, if specified, must
+ contain a <span>valid URL potentially surrounded by spaces</span>.</p>
- <p>A <code>base</code> element, if it has an <code
- title="attr-base-href">href</code> attribute, must come before any
- other elements in the tree that have attributes defined as taking
- <span title="URL">URLs</span>, except the <code>html</code> element
- (its <code title="attr-html-manifest">manifest</code> attribute
- isn't affected by <code>base</code> elements).</p>
+ <p>A <code>base</code> element, if it has an <code title="attr-base-href">href</code> attribute,
+ must come before any other elements in the tree that have attributes defined as taking <span
+ title="URL">URLs</span>, except the <code>html</code> element (its <code
+ title="attr-html-manifest">manifest</code> attribute isn't affected by <code>base</code>
+ elements).</p>
<div class="impl">
- <p class="note">If there are multiple <code>base</code> elements
- with <code title="attr-base-href">href</code> attributes, all but the
- first are ignored.</p>
+ <p class="note">If there are multiple <code>base</code> elements with <code
+ title="attr-base-href">href</code> attributes, all but the first are ignored.</p>
</div>
- <p>The <dfn title="attr-base-target"><code>target</code></dfn>
- attribute, if specified, must contain a <span>valid browsing context
- name or keyword</span>, which specifies which <span>browsing
- context</span> is to be used as the default when <span
- title="hyperlink">hyperlinks</span> and <span
- title="form">forms</span> in the <code>Document</code> cause <span
- title="navigate">navigation</span>.</p>
+ <p>The <dfn title="attr-base-target"><code>target</code></dfn> attribute, if specified, must
+ contain a <span>valid browsing context name or keyword</span>, which specifies which
+ <span>browsing context</span> is to be used as the default when <span
+ title="hyperlink">hyperlinks</span> and <span title="form">forms</span> in the
+ <code>Document</code> cause <span title="navigate">navigation</span>.</p>
- <p>A <code>base</code> element, if it has a <code
- title="attr-base-target">target</code> attribute, must come before
- any elements in the tree that represent <span
+ <p>A <code>base</code> element, if it has a <code title="attr-base-target">target</code>
+ attribute, must come before any elements in the tree that represent <span
title="hyperlink">hyperlinks</span>.</p>
<div class="impl">
- <p class="note">If there are multiple <code>base</code> elements
- with <code title="attr-base-target">target</code> attributes, all but
- the first are ignored.</p>
+ <p class="note">If there are multiple <code>base</code> elements with <code
+ title="attr-base-target">target</code> attributes, all but the first are ignored.</p>
<p>A <code>base</code> element that is the first <code>base</code> element with an <code
title="attr-base-href">href</code> content attribute in a particular <code>Document</code> has a
@@ -12834,51 +12810,44 @@
<span>frozen base URL</span> to the <span>resulting absolute URL</span>, otherwise, set the
<span>frozen base URL</span> to the <span>fallback base URL</span>.</p>
- <p>The <dfn title="dom-base-href"><code>href</code></dfn> IDL
- attribute, on getting, must return the result of running the
- following algorithm:
+ <p>The <dfn title="dom-base-href"><code>href</code></dfn> IDL attribute, on getting, must return
+ the result of running the following algorithm:
<ol> <!-- http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1715 -->
- <li><p>If the <code>base</code> element has no <code
- title="attr-base-href">href</code> content attribute, then return
- the <span>document base URL</span> and abort these steps.</p></li>
+ <li><p>If the <code>base</code> element has no <code title="attr-base-href">href</code> content
+ attribute, then return the <span>document base URL</span> and abort these steps.</p></li>
- <li><p>Let <var title="">fallback base url</var> be the
- <code>Document</code>'s <span>fallback base URL</span>.</p></li>
+ <li><p>Let <var title="">fallback base url</var> be the <code>Document</code>'s <span>fallback
+ base URL</span>.</p></li>
- <li><p>Let <var title="">url</var> be the value of the <code
- title="attr-base-href">href</code> attribute of the
- <code>base</code> element.</p></li>
+ <li><p>Let <var title="">url</var> be the value of the <code title="attr-base-href">href</code>
+ attribute of the <code>base</code> element.</p></li>
- <li><p><span title="resolve a URL">Resolve</span> <var
- title="">url</var> relative to <var title="">fallback base
- url</var> (thus, the <code>base</code> <code
- title="attr-base-href">href</code> attribute isn't affected by
- <code title="attr-xml-base">xml:base</code> attributes or
- <code>base</code> elements).</p></li>
+ <li><p><span title="resolve a URL">Resolve</span> <var title="">url</var> relative to <var
+ title="">fallback base url</var> (thus, the <code>base</code> <code
+ title="attr-base-href">href</code> attribute isn't affected by <code
+ title="attr-xml-base">xml:base</code> attributes or <code>base</code> elements).</p></li>
- <li><p>If the previous step was successful, return the resulting
- <span>absolute URL</span> and abort these steps.</p></li>
+ <li><p>If the previous step was successful, return the resulting <span>absolute URL</span> and
+ abort these steps.</p></li>
<li><p>Otherwise, return the empty string.</p></li>
</ol>
- <p>The <code title="dom-base-href">href</code> IDL attribute, on
- setting, must set the <code title="attr-base-href">href</code>
- content attribute to the given new value.</p>
+ <p>The <code title="dom-base-href">href</code> IDL attribute, on setting, must set the <code
+ title="attr-base-href">href</code> content attribute to the given new value.</p>
- <p>The <dfn title="dom-base-target"><code>target</code></dfn> IDL
- attribute must <span>reflect</span> the content attribute of the
- same name.</p>
+ <p>The <dfn title="dom-base-target"><code>target</code></dfn> IDL attribute must
+ <span>reflect</span> the content attribute of the same name.</p>
</div>
<div class="example">
- <p>In this example, a <code>base</code> element is used to set the
- <span>document base URL</span>:</p>
+ <p>In this example, a <code>base</code> element is used to set the <span>document base
+ URL</span>:</p>
<pre><!DOCTYPE html>
<html>
@@ -13755,14 +13724,12 @@
-->
<div class="impl">
-<!--CLEANUP-->
- <p>When a <code>meta</code> element is <span title="insert an
- element into a document">inserted into the document</span>, if its
- <code title="attr-meta-http-equiv">http-equiv</code> attribute is
- present and represents one of the above states, then the user agent
- must run the algorithm appropriate for that state, as described in
- the following list:</p>
+ <p>When a <code>meta</code> element is <span title="insert an element into a document">inserted
+ into the document</span>, if its <code title="attr-meta-http-equiv">http-equiv</code> attribute is
+ present and represents one of the above states, then the user agent must run the algorithm
+ appropriate for that state, as described in the following list:</p>
+
</div>
<dl>
@@ -13771,40 +13738,34 @@
<dd class="impl">
- <p class="note">This feature is non-conforming. Authors are
- encouraged to use the <code title="attr-lang">lang</code>
- attribute instead.</p>
+ <p class="note">This feature is non-conforming. Authors are encouraged to use the <code
+ title="attr-lang">lang</code> attribute instead.</p>
- <p>This pragma sets the <dfn>pragma-set default language</dfn>.
- Until such a pragma is successfully processed, there is no
- <span>pragma-set default language</span>.</p>
+ <p>This pragma sets the <dfn>pragma-set default language</dfn>. Until such a pragma is
+ successfully processed, there is no <span>pragma-set default language</span>.</p>
<!-- http://www.hixie.ch/tests/adhoc/html/meta/content-language/ -->
<ol>
- <li><p>If the <code>meta</code> element has no <code
- title="attr-meta-content">content</code> attribute, then abort these
- steps.</p></li>
+ <li><p>If the <code>meta</code> element has no <code title="attr-meta-content">content</code>
+ attribute, then abort these steps.</p></li>
- <li><p>If the element's <code
- title="attr-meta-content">content</code> attribute contains a
- U+002C COMMA character (,) then abort these steps.</p></li><!--
- if you remove this, un-comment-out the corresponding bits in the
- step below. -->
+ <li><p>If the element's <code title="attr-meta-content">content</code> attribute contains a
+ U+002C COMMA character (,) then abort these steps.</p></li><!-- if you remove this,
+ un-comment-out the corresponding bits in the step below. -->
- <li><p>Let <var title="">input</var> be the value of the
- element's <code title="attr-meta-content">content</code>
- attribute.</p></li>
+ <li><p>Let <var title="">input</var> be the value of the element's <code
+ title="attr-meta-content">content</code> attribute.</p></li>
- <li><p>Let <var title="">position</var> point at the first
- character of <var title="">input</var>.</p></li>
+ <li><p>Let <var title="">position</var> point at the first character of <var
+ title="">input</var>.</p></li>
<li><p><span>Skip whitespace</span>.</p></li>
<li><p><span>Collect a sequence of characters</span> that are not<!--neither--> <span
- title="space character">space characters</span><!-- nor a U+002C
- COMMA character (,)-->.</p></li>
+ title="space character">space characters</span><!-- nor a U+002C COMMA character
+ (,)-->.</p></li>
<li><p>Let <var title="">candidate</var> be the string that resulted from the previous
step.</p></li>
@@ -13816,8 +13777,8 @@
</ol>
- <p class="note">This pragma is not exactly equivalent to the HTTP
- <code>Content-Language</code> header. <a href="#refsHTTP">[HTTP]</a></p>
+ <p class="note">This pragma is not exactly equivalent to the HTTP <code>Content-Language</code>
+ header. <a href="#refsHTTP">[HTTP]</a></p>
</dd>
@@ -13857,23 +13818,18 @@
<dd>
- <p>This pragma sets the name of the default <span
- title="alternative style sheet sets">alternative style sheet
- set</span>.</p>
+ <p>This pragma sets the name of the default <span title="alternative style sheet
+ sets">alternative style sheet set</span>.</p>
<div class="impl">
<ol>
- <li><p>If the <code>meta</code> element has no <code
- title="attr-meta-content">content</code> attribute, or if that
- attribute's value is the empty string, then abort these
- steps.</p></li>
+ <li><p>If the <code>meta</code> element has no <code title="attr-meta-content">content</code>
+ attribute, or if that attribute's value is the empty string, then abort these steps.</p></li>
- <li><p>Set the <span>preferred style sheet set</span> to the
- value of the element's <code
- title="attr-meta-content">content</code> attribute. <a
- href="#refsCSSOM">[CSSOM]</a></p></li>
+ <li><p>Set the <span>preferred style sheet set</span> to the value of the element's <code
+ title="attr-meta-content">content</code> attribute. <a href="#refsCSSOM">[CSSOM]</a></p></li>
</ol>
@@ -14011,8 +13967,8 @@
<li><p>Provide the user with an interface that, when selected, <span
title="navigate">navigates</span><!--DONAV meta refresh--> a <span>browsing context</span> to
- <var title="">url</var>, with the <code>Document</code>'s <span>browsing context</span> as the <span>source browsing
- context</span>.</p></li>
+ <var title="">url</var>, with the <code>Document</code>'s <span>browsing context</span> as
+ the <span>source browsing context</span>.</p></li>
<li><p>Do nothing.</p></li>
@@ -14104,63 +14060,53 @@
<h5>Other pragma directives</h5>
- <p><dfn title="concept-http-equiv-extensions">Extensions to the
- predefined set of pragma directives</dfn> may, under certain
- conditions, be registered in the <a
- href="http://wiki.whatwg.org/wiki/PragmaExtensions">WHATWG Wiki
- PragmaExtensions page</a>. <a
+ <p><dfn title="concept-http-equiv-extensions">Extensions to the predefined set of pragma
+ directives</dfn> may, under certain conditions, be registered in the <a
+ href="http://wiki.whatwg.org/wiki/PragmaExtensions">WHATWG Wiki PragmaExtensions page</a>. <a
href="#refsWHATWGWIKI">[WHATWGWIKI]</a></p>
- <p>Such extensions must use a name that is identical to an HTTP
- header registered in the Permanent Message Header Field Registry,
- and must have behavior identical to that described for the HTTP
+ <p>Such extensions must use a name that is identical to an HTTP header registered in the Permanent
+ Message Header Field Registry, and must have behavior identical to that described for the HTTP
header. <a href="#refsIANAPERMHEADERS">[IANAPERMHEADERS]</a></p>
- <p>Pragma directives corresponding to headers describing metadata,
- or not requiring specific user agent processing, must not be
- registered; instead, use <span
- title="concept-meta-extensions">metadata names</span>. Pragma
- directives corresponding to headers that affect the HTTP processing
- model (e.g. caching) must not be registered, as they would result in
- HTTP-level behavior being different for user agents that implement
- HTML than for user agents that do not.</p>
+ <p>Pragma directives corresponding to headers describing metadata, or not requiring specific user
+ agent processing, must not be registered; instead, use <span
+ title="concept-meta-extensions">metadata names</span>. Pragma directives corresponding to headers
+ that affect the HTTP processing model (e.g. caching) must not be registered, as they would result
+ in HTTP-level behavior being different for user agents that implement HTML than for user agents
+ that do not.</p>
- <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at
- any time to add a pragma directive satisfying these conditions. Such
- registrations must specify the following information:</p>
+ <p>Anyone is free to edit the WHATWG Wiki PragmaExtensions page at any time to add a pragma
+ directive satisfying these conditions. Such registrations must specify the following
+ information:</p>
<dl>
<dt>Keyword</dt>
- <dd><p>The actual name being defined. The name must match a
- previously-registered HTTP name with the same
- requirements.</p></dd>
+ <dd><p>The actual name being defined. The name must match a previously-registered HTTP name with
+ the same requirements.</p></dd>
<dt>Brief description</dt>
- <dd><p>A short non-normative description of the purpose of the
- pragma directive.</p></dd>
+ <dd><p>A short non-normative description of the purpose of the pragma directive.</p></dd>
<dt>Specification</dt>
- <dd>A link to the specification defining the corresponding HTTP
- header.</dd>
+ <dd>A link to the specification defining the corresponding HTTP header.</dd>
</dl>
<div class="impl">
- <p>Conformance checkers must use the information given on the WHATWG
- Wiki PragmaExtensions page to establish if a value is allowed or
- not: values defined in this specification or listed on the
- aforementioned page must be accepted, whereas values not listed in
- either this specification or on the aforementioned page must be
- rejected as invalid. Conformance checkers may cache this information
- (e.g. for performance reasons or to avoid the use of unreliable
- network connectivity).</p>
+ <p>Conformance checkers must use the information given on the WHATWG Wiki PragmaExtensions page to
+ establish if a value is allowed or not: values defined in this specification or listed on the
+ aforementioned page must be accepted, whereas values not listed in either this specification or on
+ the aforementioned page must be rejected as invalid. Conformance checkers may cache this
+ information (e.g. for performance reasons or to avoid the use of unreliable network
+ connectivity).</p>
</div>
@@ -14321,30 +14267,24 @@
</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>style</code> element allows authors to embed style
- information in their documents. The <code>style</code> element is
- one of several inputs to the <span>styling processing
- model</span>. The element does not <span
- title="represents">represent</span> content for the user.</p>
+ <p>The <code>style</code> element allows authors to embed style information in their documents.
+ The <code>style</code> element is one of several inputs to the <span>styling processing
+ model</span>. The element does not <span title="represents">represent</span> content for the
+ user.</p>
- <p>The <dfn title="attr-style-type"><code>type</code></dfn>
- attribute gives the styling language. If the attribute is present,
- its value must be a <span>valid MIME type</span> that designates a
- styling language. The <code title="">charset</code> parameter must
- not be specified. The default value for the <code
- title="attr-style-type">type</code> attribute, which is used if the
- attribute is absent, is "<code title="">text/css</code>". <a
- href="#refsRFC2318">[RFC2318]</a></p>
+ <p>The <dfn title="attr-style-type"><code>type</code></dfn> attribute gives the styling language.
+ If the attribute is present, its value must be a <span>valid MIME type</span> that designates a
+ styling language. The <code title="">charset</code> parameter must not be specified. The default
+ value for the <code title="attr-style-type">type</code> attribute, which is used if the attribute
+ is absent, is "<code title="">text/css</code>". <a href="#refsRFC2318">[RFC2318]</a></p>
<div class="impl">
- <!-- similar paragraph is also present in the <script> section -->
- <p>When examining types to determine if they support the language,
- user agents must not ignore unknown MIME parameters — types
- with unknown parameters must be assumed to be unsupported. The <code
- title="">charset</code> parameter must be treated as an unknown
- parameter for the purpose of comparing <span title="MIME type">MIME
- types</span> here.</p>
+ <!-- similar paragraph is also present in the <script> section --> <p>When examining types to
+ determine if they support the language, user agents must not ignore unknown MIME parameters
+ — types with unknown parameters must be assumed to be unsupported. The <code
+ title="">charset</code> parameter must be treated as an unknown parameter for the purpose of
+ comparing <span title="MIME type">MIME types</span> here.</p>
</div>
@@ -14371,15 +14311,15 @@
rooted at the <code>style</code> element's parent element, as opposed to the whole
<code>Document</code>.</p>
-<!--CLEANUP-->
<p>If the <code title="attr-style-scoped">scoped</code> attribute is present and the element has a
- parent element, then the <code>style</code> element must precede any <span>flow
- content</span> in its parent element other than <span>inter-element whitespace</span> and other <code>style</code> elements, and the
- parent element's content model must not have a <span>transparent</span> component.</p>
+ parent element, then the <code>style</code> element must precede any <span>flow content</span> in
+ its parent element other than <span>inter-element whitespace</span> and other <code>style</code>
+ elements, and the parent element's content model must not have a <span>transparent</span>
+ component.</p>
- <p class="note">This implies that scoped <code>style</code> elements
- cannot be children of, e.g., <code>a</code> or <code>ins</code> elements,
- even when those are used as <span>flow content</span> containers.</p>
+ <p class="note">This implies that scoped <code>style</code> elements cannot be children of, e.g.,
+ <code>a</code> or <code>ins</code> elements, even when those are used as <span>flow content</span>
+ containers.</p>
<p class="note">A <code>style</code> element <em>without</em> a <code
title="attr-style-scoped">scoped</code> attribute is restricted to appearing in the
@@ -14409,23 +14349,19 @@
<pre>B b|\\0{0,4}(42|62)(\r\n|[ \t\r\n\f])?
@{G}{L}{O}{B}{A}{L} {return GLOBAL_SYM;}</pre>
- <p>Simple selectors in rule sets prefixed by the <code
- title="">@global</code> @-rule in scoped CSS resources must be
- processed in the same way as normal rule sets in non-scoped CSS
+ <p>Simple selectors in rule sets prefixed by the <code title="">@global</code> @-rule in scoped
+ CSS resources must be processed in the same way as normal rule sets in non-scoped CSS
resources.</p>
- <p>Simple selectors in scoped CSS resources that are not prefixed by
- an <code title="">@global</code> @-rule must only match the
- <code>style</code> element's parent element (if any), and that
- element's descendants.</p>
+ <p>Simple selectors in scoped CSS resources that are not prefixed by an <code
+ title="">@global</code> @-rule must only match the <code>style</code> element's parent element (if
+ any), and that element's descendants.</p>
- <p>For scoped CSS resources, the effect of other @-rules must be
- scoped to either the scoped sheet and its subresources or to the
- subtree rooted at the <code>style</code> element's parent (if any),
- even if the @-rule in question would ordinarily apply to all style
- sheets that affect the <code>Document</code>, or to all nodes in the
- <code>Document</code>. Any '@page' rules in scoped CSS resources
- must be ignored.</p>
+ <p>For scoped CSS resources, the effect of other @-rules must be scoped to either the scoped sheet
+ and its subresources or to the subtree rooted at the <code>style</code> element's parent (if any),
+ even if the @-rule in question would ordinarily apply to all style sheets that affect the
+ <code>Document</code>, or to all nodes in the <code>Document</code>. Any '@page' rules in scoped
+ CSS resources must be ignored.</p>
<p class="example">For example, an '@font-face' rule defined in a scoped style sheet would only
define the font for the purposes of elements in the scoped section; the font would not be used for
@@ -14437,26 +14373,20 @@
</div>
- <p id="title-on-style">The <dfn
- title="attr-style-title"><code>title</code></dfn> attribute on
- <code>style</code> elements defines <span>alternative style sheet
- sets</span>. If the <code>style</code> element has no <code
- title="attr-style-title">title</code> attribute, then it has no
- title; the <code title="attr-title">title</code> attribute of
- ancestors does not apply to the <code>style</code> element. <a
- href="#refsCSSOM">[CSSOM]</a></p>
+ <p id="title-on-style">The <dfn title="attr-style-title"><code>title</code></dfn> attribute on
+ <code>style</code> elements defines <span>alternative style sheet sets</span>. If the
+ <code>style</code> element has no <code title="attr-style-title">title</code> attribute, then it
+ has no title; the <code title="attr-title">title</code> attribute of ancestors does not apply to
+ the <code>style</code> element. <a href="#refsCSSOM">[CSSOM]</a></p>
- <p class="note">The <code title="attr-style-title">title</code>
- attribute on <code>style</code> elements, like the <code
- title="attr-link-title">title</code> attribute on <code>link</code>
- elements, differs from the global <code
- title="attr-title">title</code> attribute in that a
- <code>style</code> block without a title does not inherit the title
- of the parent element: it merely has no title.</p>
+ <p class="note">The <code title="attr-style-title">title</code> attribute on <code>style</code>
+ elements, like the <code title="attr-link-title">title</code> attribute on <code>link</code>
+ elements, differs from the global <code title="attr-title">title</code> attribute in that a
+ <code>style</code> block without a title does not inherit the title of the parent element: it
+ merely has no title.</p>
- <p>The <code>textContent</code> of a <code>style</code> element must
- match the <code title="">style</code> production in the following
- ABNF, the character set for which is Unicode. <a
+ <p>The <code>textContent</code> of a <code>style</code> element must match the <code
+ title="">style</code> production in the following ABNF, the character set for which is Unicode. <a
href="#refsABNF">[ABNF]</a></p>
<pre>style = no-c-start *( c-start no-c-end c-end no-c-start )
@@ -14476,79 +14406,62 @@
<div class="impl">
- <p>All descendant elements must be processed, according to their
- semantics, before the <code>style</code> element itself is
- evaluated. For styling languages that consist of pure text (as
- opposed to XML), user agents must evaluate <code>style</code>
- elements by passing the concatenation of the contents of all the
- <code>Text</code> nodes that are children of the
- <code>style</code> element (not any other nodes such as comments or
- elements), in <span>tree order</span>, to the style system. For
- XML-based styling languages, user agents must pass all the child
- nodes of the <code>style</code> element to the style system.</p>
+ <p>All descendant elements must be processed, according to their semantics, before the
+ <code>style</code> element itself is evaluated. For styling languages that consist of pure text
+ (as opposed to XML), user agents must evaluate <code>style</code> elements by passing the
+ concatenation of the contents of all the <code>Text</code> nodes that are children of the
+ <code>style</code> element (not any other nodes such as comments or elements), in <span>tree
+ order</span>, to the style system. For XML-based styling languages, user agents must pass all the
+ child nodes of the <code>style</code> element to the style system.</p>
- <p>All <span title="URL">URLs</span> found by the styling language's
- processor must be <span title="resolve a url">resolved</span>,
- relative to the element (or as defined by the styling language),
- when the processor is invoked.<!-- so dynamic changes to the base
- URL don't affect the CSS --></p>
+ <p>All <span title="URL">URLs</span> found by the styling language's processor must be <span
+ title="resolve a url">resolved</span>, relative to the element (or as defined by the styling
+ language), when the processor is invoked.<!-- so dynamic changes to the base URL don't affect the
+ CSS --></p>
<!-- the next few paragraph are similar to text in the <style> section -->
- <p>Once the attempts to obtain the style sheet's <span>critical
- subresources</span>, if any, are complete, or, if the style sheet
- has no <span>critical subresources</span>, once the style sheet has
- been parsed and processed, the user agent must, if the loads were
- successful or there were none, <span>queue a task</span> to
- <span>fire a simple event</span> named <code
- title="event-load">load</code> at the <code>style</code> element,
- or, if one of the style sheet's <span>critical subresources</span>
- failed to completely load for any reason (e.g. DNS error, HTTP 404
- response, a connection being prematurely closed, unsupported
- Content-Type), <span>queue a task</span> to <span>fire a simple
- event</span> named <code title="event-error">error</code> at the
- <code>style</code> element. Non-network errors in processing the
- style sheet or its subresources (e.g. CSS parse errors, PNG decoding
- errors) are not failures for the purposes of this paragraph.</p>
+ <p>Once the attempts to obtain the style sheet's <span>critical subresources</span>, if any, are
+ complete, or, if the style sheet has no <span>critical subresources</span>, once the style sheet
+ has been parsed and processed, the user agent must, if the loads were successful or there were
+ none, <span>queue a task</span> to <span>fire a simple event</span> named <code
+ title="event-load">load</code> at the <code>style</code> element, or, if one of the style sheet's
+ <span>critical subresources</span> failed to completely load for any reason (e.g. DNS error, HTTP
+ 404 response, a connection being prematurely closed, unsupported Content-Type), <span>queue a
+ task</span> to <span>fire a simple event</span> named <code title="event-error">error</code> at
+ the <code>style</code> element. Non-network errors in processing the style sheet or its
+ subresources (e.g. CSS parse errors, PNG decoding errors) are not failures for the purposes of
+ this paragraph.</p>
- <p>The <span>task source</span> for these <span
- title="concept-task">tasks</span> is the <span>DOM manipulation task
- source</span>.</p>
+ <p>The <span>task source</span> for these <span title="concept-task">tasks</span> is the <span>DOM
+ manipulation task source</span>.</p>
- <p>The element must <span>delay the load event</span> of the
- element's document until all the attempts to obtain the style
- sheet's <span>critical subresources</span>, if any, are
- complete.</p>
+ <p>The element must <span>delay the load event</span> of the element's document until all the
+ attempts to obtain the style sheet's <span>critical subresources</span>, if any, are complete.</p>
</div>
- <p class="note">This specification does not specify a style system,
- but CSS is expected to be supported by most Web browsers. <a
- href="#refsCSS">[CSS]</a></p>
+ <p class="note">This specification does not specify a style system, but CSS is expected to be
+ supported by most Web browsers. <a href="#refsCSS">[CSS]</a></p>
<div class="impl">
<p>The <dfn title="dom-style-media"><code>media</code></dfn>, <dfn
title="dom-style-type"><code>type</code></dfn> and <dfn
- title="dom-style-scoped"><code>scoped</code></dfn> IDL attributes
- must <span>reflect</span> the respective content attributes of the
- same name.</p>
+ title="dom-style-scoped"><code>scoped</code></dfn> IDL attributes must <span>reflect</span> the
+ respective content attributes of the same name.</p>
</div>
- <p>The <dfn title="dom-style-disabled"><code>disabled</code></dfn>
- IDL attribute behaves as defined <span
- title="dom-linkstyle-disabled">for the alternative style sheets
- DOM</span>.</p>
+ <p>The <dfn title="dom-style-disabled"><code>disabled</code></dfn> IDL attribute behaves as
+ defined <span title="dom-linkstyle-disabled">for the alternative style sheets DOM</span>.</p>
- <p>The <code>LinkStyle</code> interface is also implemented by
- this element; the <span>styling processing model</span> defines
- how. <a href="#refsCSSOM">[CSSOM]</a></p>
+ <p>The <code>LinkStyle</code> interface is also implemented by this element; the <span>styling
+ processing model</span> defines how. <a href="#refsCSSOM">[CSSOM]</a></p>
<div class="example">
- <p>The following document has its stress emphasis styled as bright
- red text rather than italics text, while leaving titles of works
- and Latin words in their default italics. It shows how using
+ <p>The following document has its stress emphasis styled as bright red text rather than italics
+ text, while leaving titles of works and Latin words in their default italics. It shows how using
appropriate elements enables easier restyling of documents.</p>
<pre><!DOCTYPE html>
@@ -14715,24 +14628,25 @@
<p>Scripts allow authors to add interactivity to their documents.</p>
- <p>Authors are encouraged to use declarative alternatives to
- scripting where possible, as declarative mechanisms are often more
- maintainable, and many users disable scripting.</p>
+ <p>Authors are encouraged to use declarative alternatives to scripting where possible, as
+ declarative mechanisms are often more maintainable, and many users disable scripting.</p>
<div class="example">
- <p>For example, instead of using script to show or hide a section
- to show more details, the <code>details</code> element could be
- used.</p>
+
+ <p>For example, instead of using script to show or hide a section to show more details, the
+ <code>details</code> element could be used.</p>
+
</div>
- <p>Authors are also encouraged to make their applications degrade
- gracefully in the absence of scripting support.</p>
+ <p>Authors are also encouraged to make their applications degrade gracefully in the absence of
+ scripting support.</p>
<div class="example">
- <p>For example, if an author provides a link in a table header to
- dynamically resort the table, the link could also be made to
- function without scripts by requesting the sorted table from the
+
+ <p>For example, if an author provides a link in a table header to dynamically resort the table,
+ the link could also be made to function without scripts by requesting the sorted table from the
server.</p>
+
</div>
@@ -15835,51 +15749,41 @@
<!--END dev-html--><p><i>This section is non-normative.</i></p><!--START dev-html-->
- <p>This specification does not define how XSLT interacts with the
- <code>script</code> element. However, in the absence of another
- specification actually defining this, here are some guidelines for
- implementors, based on existing implementations:</p>
+ <p>This specification does not define how XSLT interacts with the <code>script</code> element.
+ However, in the absence of another specification actually defining this, here are some guidelines
+ for implementors, based on existing implementations:</p>
<ul>
<li><p>When an XSLT transformation program is triggered by an <code
- title=""><?xml-stylesheet?></code> processing instruction and
- the browser implements a direct-to-DOM transformation,
- <code>script</code> elements created by the XSLT processor need to
- be marked <span>"parser-inserted"</span> and run in document order
- (modulo scripts marked <code title="attr-script-defer">defer</code>
- or <code title="attr-script-async">async</code>), asynchronously
- while the transformation is occurring.</p></li>
+ title=""><?xml-stylesheet?></code> processing instruction and the browser implements a
+ direct-to-DOM transformation, <code>script</code> elements created by the XSLT processor need to
+ be marked <span>"parser-inserted"</span> and run in document order (modulo scripts marked <code
+ title="attr-script-defer">defer</code> or <code title="attr-script-async">async</code>),
+ asynchronously while the transformation is occurring.</p></li>
<li><p>The <code
- title="dom-XSLTProcessor-transformToDocument">XSLTProcessor.transformToDocument()</code>
- method adds elements to a <code>Document</code> that is not in a
- <span>browsing context</span>, and, accordingly, any
- <code>script</code> elements they create need to have their
- <span>"already started"</span> flag set in the <span>prepare a
- script</span> algorithm and never get executed (<span
- title="concept-bc-noscript">scripting is disabled</span>). Such
- <code>script</code> elements still need to be marked
- <span>"parser-inserted"</span>, though, such that their <code
- title="dom-script-async">async</code> IDL attribute will return
- false in the absence of an <code
+ title="dom-XSLTProcessor-transformToDocument">XSLTProcessor.transformToDocument()</code> method
+ adds elements to a <code>Document</code> that is not in a <span>browsing context</span>, and,
+ accordingly, any <code>script</code> elements they create need to have their <span>"already
+ started"</span> flag set in the <span>prepare a script</span> algorithm and never get executed
+ (<span title="concept-bc-noscript">scripting is disabled</span>). Such <code>script</code>
+ elements still need to be marked <span>"parser-inserted"</span>, though, such that their <code
+ title="dom-script-async">async</code> IDL attribute will return false in the absence of an <code
title="attr-script-async">async</code> content attribute.</p></li>
<li><p>The <code
- title="dom-XSLTProcessor-transformToFragment">XSLTProcessor.transformToFragment()</code>
- method needs to create a fragment that is equivalent to one built
- manually by creating the elements using <code
- title="dom-document-createElementNS">document.createElementNS()</code>.
- For instance, it needs to create <code>script</code> elements that
- aren't <span>"parser-inserted"</span> and that don't have their
- <span>"already started"</span> flag set, so that they will execute
- when the fragment is inserted into a document.</p></li>
+ title="dom-XSLTProcessor-transformToFragment">XSLTProcessor.transformToFragment()</code> method
+ needs to create a fragment that is equivalent to one built manually by creating the elements
+ using <code title="dom-document-createElementNS">document.createElementNS()</code>. For instance,
+ it needs to create <code>script</code> elements that aren't <span>"parser-inserted"</span> and
+ that don't have their <span>"already started"</span> flag set, so that they will execute when the
+ fragment is inserted into a document.</p></li>
</ul>
- <p>The main distinction between the first two cases and the last
- case is that the first two operate on <code>Document</code>s and the
- last operates on a fragment.</p>
+ <p>The main distinction between the first two cases and the last case is that the first two
+ operate on <code>Document</code>s and the last operates on a fragment.</p>
</div>
@@ -15905,105 +15809,82 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>noscript</code> element <span>represents</span> nothing
- if <span title="concept-n-script">scripting is enabled</span>, and
- <span>represents</span> its children if <span
- title="concept-n-noscript">scripting is disabled</span>. It is used
- to present different markup to user agents that support scripting
- and those that don't support scripting, by affecting how the
- document is parsed.</p>
+ <p>The <code>noscript</code> element <span>represents</span> nothing if <span
+ title="concept-n-script">scripting is enabled</span>, and <span>represents</span> its children if
+ <span title="concept-n-noscript">scripting is disabled</span>. It is used to present different
+ markup to user agents that support scripting and those that don't support scripting, by affecting
+ how the document is parsed.</p>
- <p>When used in <span>HTML documents</span>, the allowed content
- model is as follows:</p>
+ <p>When used in <span>HTML documents</span>, the allowed content model is as follows:</p>
<dl>
- <dt>In a <code>head</code> element, if <span
- title="concept-n-noscript">scripting is disabled</span> for the
- <code>noscript</code> element</dt>
+ <dt>In a <code>head</code> element, if <span title="concept-n-noscript">scripting is
+ disabled</span> for the <code>noscript</code> element</dt>
- <dd><p>The <code>noscript</code> element must contain only
- <code>link</code>, <code>style</code>, and <code>meta</code>
- elements.</p></dd>
+ <dd><p>The <code>noscript</code> element must contain only <code>link</code>, <code>style</code>,
+ and <code>meta</code> elements.</p></dd>
- <dt>In a <code>head</code> element, if <span
- title="concept-n-script">scripting is enabled</span> for the
- <code>noscript</code> element</dt>
+ <dt>In a <code>head</code> element, if <span title="concept-n-script">scripting is enabled</span>
+ for the <code>noscript</code> element</dt>
- <dd><p>The <code>noscript</code> element must contain only text,
- except that invoking the <span>HTML fragment parsing
- algorithm</span> <!-- (which disables <script> execution) --> with
- the <code>noscript</code> element as the <var
- title="concept-frag-parse-context">context</var> element and the
- text contents as the <var title="">input</var> must result in a
- list of nodes that consists only of <code>link</code>,
- <code>style</code>, and <code>meta</code> elements that would be
- conforming if they were children of the <code>noscript</code>
- element, and no <span title="parse error">parse
- errors</span>.</p></dd>
+ <dd><p>The <code>noscript</code> element must contain only text, except that invoking the
+ <span>HTML fragment parsing algorithm</span> <!-- (which disables <script> execution) --> with
+ the <code>noscript</code> element as the <var title="concept-frag-parse-context">context</var>
+ element and the text contents as the <var title="">input</var> must result in a list of nodes
+ that consists only of <code>link</code>, <code>style</code>, and <code>meta</code> elements that
+ would be conforming if they were children of the <code>noscript</code> element, and no <span
+ title="parse error">parse errors</span>.</p></dd>
- <dt>Outside of <code>head</code> elements, if <span
- title="concept-n-noscript">scripting is disabled</span> for the
- <code>noscript</code> element</dt>
+ <dt>Outside of <code>head</code> elements, if <span title="concept-n-noscript">scripting is
+ disabled</span> for the <code>noscript</code> element</dt>
- <dd><p>The <code>noscript</code> element's content model is
- <span>transparent</span>, with the additional restriction that a
- <code>noscript</code> element must not have a <code>noscript</code>
- element as an ancestor (that is, <code>noscript</code> can't be
- nested).</p></dd>
+ <dd><p>The <code>noscript</code> element's content model is <span>transparent</span>, with the
+ additional restriction that a <code>noscript</code> element must not have a <code>noscript</code>
+ element as an ancestor (that is, <code>noscript</code> can't be nested).</p></dd>
- <dt>Outside of <code>head</code> elements, if <span
- title="concept-n-script">scripting is enabled</span> for the
- <code>noscript</code> element</dt>
+ <dt>Outside of <code>head</code> elements, if <span title="concept-n-script">scripting is
+ enabled</span> for the <code>noscript</code> element</dt>
<dd>
- <p>The <code>noscript</code> element must contain only text,
- except that the text must be such that running the following
- algorithm results in a conforming document with no
- <code>noscript</code> elements and no <code>script</code>
- elements, and such that no step in the algorithm causes an
- <span>HTML parser</span> to flag a <span>parse error</span>:</p>
+ <p>The <code>noscript</code> element must contain only text, except that the text must be such
+ that running the following algorithm results in a conforming document with no
+ <code>noscript</code> elements and no <code>script</code> elements, and such that no step in the
+ algorithm causes an <span>HTML parser</span> to flag a <span>parse error</span>:</p>
<ol>
- <li>Remove every <code>script</code> element from the
- document.</li>
+ <li>Remove every <code>script</code> element from the document.</li>
- <li>Make a list of every <code>noscript</code> element in the
- document. For every <code>noscript</code> element in that list,
- perform the following steps:
+ <li>Make a list of every <code>noscript</code> element in the document. For every
+ <code>noscript</code> element in that list, perform the following steps:
<ol>
- <li>Let the <var title="">parent element</var> be the parent
- element of the <code>noscript</code> element.</li>
+ <li>Let the <var title="">parent element</var> be the parent element of the
+ <code>noscript</code> element.</li>
- <li>Take all the children of the <var title="">parent element</var>
- that come before the <code>noscript</code> element, and call these
- elements <var title="">the before children</var>.</li>
+ <li>Take all the children of the <var title="">parent element</var> that come before the
+ <code>noscript</code> element, and call these elements <var title="">the before
+ children</var>.</li>
- <li>Take all the children of the <var title="">parent element</var>
- that come <em>after</em> the <code>noscript</code> element, and
- call these elements <var title="">the after children</var>.</li>
+ <li>Take all the children of the <var title="">parent element</var> that come <em>after</em>
+ the <code>noscript</code> element, and call these elements <var title="">the after
+ children</var>.</li>
- <li>Let <var title="">s</var> be the concatenation of all the
- <code>Text</code> node children of the <code>noscript</code>
- element.</li>
+ <li>Let <var title="">s</var> be the concatenation of all the <code>Text</code> node children
+ of the <code>noscript</code> element.</li>
- <li>Set the <code title="dom-innerHTML">innerHTML</code>
- attribute of the <var title="">parent element</var> to the value
- of <var title="">s</var>. (This, as a side-effect, causes the
- <code>noscript</code> element to be removed from the
- document.)</li>
+ <li>Set the <code title="dom-innerHTML">innerHTML</code> attribute of the <var
+ title="">parent element</var> to the value of <var title="">s</var>. (This, as a side-effect,
+ causes the <code>noscript</code> element to be removed from the document.)</li>
- <li>Insert <var title="">the before children</var> at the start of
- the <var title="">parent element</var>, preserving their original
- relative order.</li>
+ <li>Insert <var title="">the before children</var> at the start of the <var title="">parent
+ element</var>, preserving their original relative order.</li>
- <li>Insert <var title="">the after children</var> at the end of the
- <var title="">parent element</var>, preserving their original
- relative order.</li>
+ <li>Insert <var title="">the after children</var> at the end of the <var title="">parent
+ element</var>, preserving their original relative order.</li>
</ol>
@@ -16015,29 +15896,24 @@
</dl>
- <p class="note">All these contortions are required because, for
- historical reasons, the <code>noscript</code> element is handled
- differently by the <span>HTML parser</span> based on whether <span
- title="scripting flag">scripting was enabled or not</span> when the
- parser was invoked.</p>
+ <p class="note">All these contortions are required because, for historical reasons, the
+ <code>noscript</code> element is handled differently by the <span>HTML parser</span> based on
+ whether <span title="scripting flag">scripting was enabled or not</span> when the parser was
+ invoked.</p>
- <p>The <code>noscript</code> element must not be used in <span>XML
- documents</span>.</p>
+ <p>The <code>noscript</code> element must not be used in <span>XML documents</span>.</p>
- <p class="note">The <code>noscript</code> element is only effective
- in <span>the HTML syntax</span>, it has no effect in <span>the XHTML
- syntax</span>. This is because the way it works is by essentially
- "turning off" the parser when scripts are enabled, so that the
- contents of the element are treated as pure text and not as real
- elements. XML does not define a mechanism by which to do this.</p>
+ <p class="note">The <code>noscript</code> element is only effective in <span>the HTML
+ syntax</span>, it has no effect in <span>the XHTML syntax</span>. This is because the way it works
+ is by essentially "turning off" the parser when scripts are enabled, so that the contents of the
+ element are treated as pure text and not as real elements. XML does not define a mechanism by
+ which to do this.</p>
<div class="impl">
- <p>The <code>noscript</code> element has no other requirements. In
- particular, children of the <code>noscript</code> element are not
- exempt from <span>form submission</span>, scripting, and so forth,
- even when <span title="concept-n-script">scripting is enabled</span>
- for the element.</p>
+ <p>The <code>noscript</code> element has no other requirements. In particular, children of the
+ <code>noscript</code> element are not exempt from <span>form submission</span>, scripting, and so
+ forth, even when <span title="concept-n-script">scripting is enabled</span> for the element.</p>
</div>
@@ -16067,17 +15943,13 @@
</noscript>
</form></pre>
- <p>When script is disabled, a button appears to do the calculation
- on the server side. When script is enabled, the value is computed
- on-the-fly instead.</p>
+ <p>When script is disabled, a button appears to do the calculation on the server side. When
+ script is enabled, the value is computed on-the-fly instead.</p>
- <p>The <code>noscript</code> element is a blunt
- instrument. Sometimes, scripts might be enabled, but for some
- reason the page's script might fail. For this reason, it's
- generally better to avoid using <code>noscript</code>, and to
- instead design the script to change the page from being a
- scriptless page to a scripted page on the fly, as in the next
- example:</p>
+ <p>The <code>noscript</code> element is a blunt instrument. Sometimes, scripts might be enabled,
+ but for some reason the page's script might fail. For this reason, it's generally better to avoid
+ using <code>noscript</code>, and to instead design the script to change the page from being a
+ scriptless page to a scripted page on the fly, as in the next example:</p>
<pre><form action="calcSquare.php">
<p>
@@ -16100,9 +15972,8 @@
</script>
</form></pre>
- <p>The above technique is also useful in XHTML, since
- <code>noscript</code> is not supported in <span>the XHTML
- syntax</span>.</p>
+ <p>The above technique is also useful in XHTML, since <code>noscript</code> is not supported in
+ <span>the XHTML syntax</span>.</p>
</div>
@@ -20182,7 +20053,6 @@
<div class="impl">
-<!--CLEANUP-->
<p>The <code title="attr-hyperlink-href">href</code>, <code
title="attr-hyperlink-target">target</code>, <code
title="attr-hyperlink-download">download</code>, and <code title="attr-hyperlink-ping">ping</code>
@@ -20358,56 +20228,49 @@
<dd>Uses <code>HTMLElement</code>.</dd>
</dl><!--TOPIC:HTML-->
- <p>The <code>em</code> element <span>represents</span> stress
- emphasis of its contents.</p>
+ <p>The <code>em</code> element <span>represents</span> stress emphasis of its contents.</p>
- <p>The level of stress that a particular piece of content has is
- given by its number of ancestor <code>em</code> elements.</p>
+ <p>The level of stress that a particular piece of content has is given by its number of ancestor
+ <code>em</code> elements.</p>
- <p>The placement of stress emphasis changes the meaning of the
- sentence. The element thus forms an integral part of the content.
- The precise way in which stress is used in this way depends on the
+ <p>The placement of stress emphasis changes the meaning of the sentence. The element thus forms an
+ integral part of the content. The precise way in which stress is used in this way depends on the
language.</p>
<div class="example">
- <p>These examples show how changing the stress emphasis changes the
- meaning. First, a general statement of fact, with no stress:</p>
+ <p>These examples show how changing the stress emphasis changes the meaning. First, a general
+ statement of fact, with no stress:</p>
<pre><p>Cats are cute animals.</p></pre>
- <p>By emphasizing the first word, the statement implies that the
- kind of animal under discussion is in question (maybe someone is
- asserting that dogs are cute):</p>
+ <p>By emphasizing the first word, the statement implies that the kind of animal under discussion
+ is in question (maybe someone is asserting that dogs are cute):</p>
<pre><p><em>Cats</em> are cute animals.</p></pre>
- <p>Moving the stress to the verb, one highlights that the truth of
- the entire sentence is in question (maybe someone is saying cats
- are not cute):</p>
+ <p>Moving the stress to the verb, one highlights that the truth of the entire sentence is in
+ question (maybe someone is saying cats are not cute):</p>
<pre><p>Cats <em>are</em> cute animals.</p></pre>
- <p>By moving it to the adjective, the exact nature of the cats
- is reasserted (maybe someone suggested cats were <em>mean</em>
- animals):</p>
+ <p>By moving it to the adjective, the exact nature of the cats is reasserted (maybe someone
+ suggested cats were <em>mean</em> animals):</p>
<pre><p>Cats are <em>cute</em> animals.</p></pre>
- <p>Similarly, if someone asserted that cats were vegetables,
- someone correcting this might emphasize the last word:</p>
+ <p>Similarly, if someone asserted that cats were vegetables, someone correcting this might
+ emphasize the last word:</p>
<pre><p>Cats are cute <em>animals</em>.</p></pre>
- <p>By emphasizing the entire sentence, it becomes clear that the
- speaker is fighting hard to get the point across. This kind of
- stress emphasis also typically affects the punctuation, hence the
+ <p>By emphasizing the entire sentence, it becomes clear that the speaker is fighting hard to get
+ the point across. This kind of stress emphasis also typically affects the punctuation, hence the
exclamation mark here.</p>
<pre><p><em>Cats are cute animals!</em></p></pre>
- <p>Anger mixed with emphasizing the cuteness could lead to markup
- such as:</p>
+ <p>Anger mixed with emphasizing the cuteness could lead to markup such as:</p>
<pre><p><em>Cats are <em>cute</em> animals!</em></p></pre>
@@ -20415,14 +20278,12 @@
<div class="note">
- <p>The <code>em</code> element isn't a generic "italics"
- element. Sometimes, text is intended to stand out from the rest of
- the paragraph, as if it was in a different mood or voice. For this,
+ <p>The <code>em</code> element isn't a generic "italics" element. Sometimes, text is intended to
+ stand out from the rest of the paragraph, as if it was in a different mood or voice. For this,
the <code>i</code> element is more appropriate.</p>
- <p>The <code>em</code> element also isn't intended to convey
- importance; for that purpose, the <code>strong</code> element is
- more appropriate.</p>
+ <p>The <code>em</code> element also isn't intended to convey importance; for that purpose, the
+ <code>strong</code> element is more appropriate.</p>
<!--
@@ -102006,7 +101867,7 @@
</dd>
- <dt id="adoptionAgency">An end tag whose tag name is one of: "a",
+ <dt>An end tag whose tag name is one of: "a",
"b", "big", "code", "em", "font", "i", "nobr", "s", "small",
"strike", "strong", "tt", "u"</dt>
<dd>
@@ -102539,7 +102400,7 @@
</ol>
- <p>The <dfn>adoption agency algorithm</dfn>, which takes as its only argument a tag name <var
+ <p id="adoptionAgency">The <dfn>adoption agency algorithm</dfn>, which takes as its only argument a tag name <var
title="">subject</var> for which the algorithm is being run, consists of the following steps:</p>
<!--CLEANUP-->
More information about the Commit-Watchers
mailing list