- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 28 Aug 2009 19:42:43 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv21847
Modified Files:
Overview.html
Log Message:
Typo omnibus. (whatwg r3689)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2867
retrieving revision 1.2868
diff -u -d -r1.2867 -r1.2868
--- Overview.html 28 Aug 2009 02:16:15 -0000 1.2867
+++ Overview.html 28 Aug 2009 19:42:40 -0000 1.2868
@@ -3010,10 +3010,10 @@
<p class="note">While the formats described here are intended to be
subsets of the corresponding ISO8601 formats, this specification
defines parsing rules in much more detail than ISO8601.
- Implementators are therefore encouraged to carefully examine any
- date parsing libraries before using them to implement the parsing
- rules described below; ISO8601 libraries might not parse dates and
- times exactly the same manner. <a href="#refsISO8601">[ISO8601]</a></p>
+ Implementors are therefore encouraged to carefully examine any date
+ parsing libraries before using them to implement the parsing rules
+ described below; ISO8601 libraries might not parse dates and times
+ exactly the same manner. <a href="#refsISO8601">[ISO8601]</a></p>
</div><h5 id="months"><span class="secno">2.4.5.1 </span>Months</h5><p>A <dfn id="concept-month" title="concept-month">month</dfn> consists of a specific
proleptic Gregorian date with no time-zone information and no date
@@ -4376,8 +4376,8 @@
<li>
<p>If the resource is identified by an <a href="#absolute-url">absolute URL</a>,
- and the resource is to be obtained using a idempotent action (such
- as an HTTP GET <a href="#concept-http-equivalent-get" title="concept-http-equivalent-get">or
+ and the resource is to be obtained using an idempotent action
+ (such as an HTTP GET <a href="#concept-http-equivalent-get" title="concept-http-equivalent-get">or
equivalent</a>), and it is already being downloaded for other
reasons (e.g. another invocation of this algorithm), and the user
agent is configured such that it is to reuse the data from the
@@ -7909,7 +7909,7 @@
<p>To avoid this confusion, explicit <code><a href="#the-p-element">p</a></code> elements can be
used.</p>
- </div><h4 id="annotations-for-assistive-technology-products"><span class="secno">3.2.6 </span><dfn>Annotations for assistive technology products</dfn></h4><p class="XXX annotation"><b>Status: </b><i>First draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/35">ISSUE-35</a> (aria-processing) and <a href="http://www.w3.org/html/wg/tracker/issues/14">ISSUE-14</a> (aria-role) block progress to Last Call</span><p>Authors may use the ARIA <code title="attr-aria-role">role</code>
+ </div><h4 id="annotations-for-assistive-technology-products"><span class="secno">3.2.6 </span><dfn>Annotations for assistive technology products</dfn></h4><p class="XXX annotation"><b>Status: </b><i>First draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/14">ISSUE-14</a> (aria-role) and <a href="http://www.w3.org/html/wg/tracker/issues/35">ISSUE-35</a> (aria-processing) block progress to Last Call</span><p>Authors may use the ARIA <code title="attr-aria-role">role</code>
and <code title="attr-aria-*">aria-*</code> attributes on <a href="#html-elements">HTML
elements</a>, in accordance with the requirements described in
the ARIA specifications, except where these conflict with the
@@ -10221,7 +10221,7 @@
sets", the term "default style sheet set", preferred stylesheets,
alternative stylesheets, persistent stylesheets, ordering of
stylesheets, dynamic additions/removals, window.styleSheets, style
- sheets given by HTTP Link: headers, and the alternative stylesheet
+ sheets given by HTTP Link: headers, and the alternative style sheet
API -->
<p id="alternate-style-sheets">The rules for handling alternative
@@ -10309,7 +10309,7 @@
parsing. If neither attribute is present, then the script is
fetched and executed immediately, before the user agent continues
parsing the page. The exact processing details for these attributes
- is described below.<p>The <code title="attr-script-defer"><a href="#attr-script-defer">defer</a></code> attribute may be
+ are described below.<p>The <code title="attr-script-defer"><a href="#attr-script-defer">defer</a></code> attribute may be
specified even if the <code title="attr-script-async"><a href="#attr-script-async">async</a></code>
attribute is specified, to cause legacy Web browsers that only
support <code title="attr-script-defer"><a href="#attr-script-defer">defer</a></code> (and not <code title="attr-script-async"><a href="#attr-script-async">async</a></code>) to fall back to the <code title="attr-script-defer"><a href="#attr-script-defer">defer</a></code> behavior instead of the
@@ -11141,7 +11141,7 @@
have a list of links to various key parts of a site, but the
<code><a href="#the-footer-element">footer</a></code> element is more appropriate in such cases, and
no <code><a href="#the-nav-element">nav</a></code> element is necessary for those links.<p class="note">User agents (such as screen readers) that are
- targetted at users who can benefit from navigation information being
+ targeted at users who can benefit from navigation information being
omitted in the initial rendering, or who can benefit from navigation
information being immediately available, can use this element as a
way to determine what content on the page to initially skip and/or
@@ -17586,7 +17586,7 @@
<a href="#reflect">reflect</a> the respective content attributes of the same
name.</p>
- </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization), <a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil) and <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
+ </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil), <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) and <a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
<dd><a href="#flow-content">Flow content</a>.</dd>
<dd><a href="#phrasing-content">Phrasing content</a>.</dd>
<dd><a href="#embedded-content">Embedded content</a>.</dd>
@@ -17777,7 +17777,7 @@
system-modal dialog had been shown, and prompt the user for a
password. There is also the danger of "mere" annoyance, with pages
launching full-screen videos when links are clicked or pages
- navigated. Instead, user-agent specific interface features may be
+ navigated. Instead, user-agent-specific interface features may be
provided to easily allow the user to obtain a full-screen playback
mode.</p>
@@ -19286,7 +19286,7 @@
<p>User agents must act as if the timeline of the <a href="#media-resource">media
resource</a> increases linearly starting from the <a href="#earliest-possible-position">earliest
- possible position</a>, even if the underling <a href="#media-data">media
+ possible position</a>, even if the underlying <a href="#media-data">media
data</a> has out-of-order or even overlapping time codes.</p>
<p class="example">For example, if two clips have been concatenated
@@ -22237,14 +22237,15 @@
<p>The <dfn id="dom-context-2d-font" title="dom-context-2d-font"><code>font</code></dfn> DOM
attribute, on setting, must be parsed the same way as the 'font'
- property of CSS (but without supporting property-independent
- stylesheet syntax like 'inherit'), and the resulting font must be
+ property of CSS (but without supporting property-independent style
+ sheet syntax like 'inherit'), and the resulting font must be
assigned to the context, with the 'line-height' component forced to
'normal', with the 'font-size' component converted to CSS pixels,
and with system fonts being computed to explicit values. If the new
value is syntactically incorrect (including using
- property-independent stylesheet syntax like 'inherit' or 'initial'),
- then it must be ignored, without assigning a new font value. <a href="#refsCSS">[CSS]</a></p>
+ property-independent style sheet syntax like 'inherit' or
+ 'initial'), then it must be ignored, without assigning a new font
+ value. <a href="#refsCSS">[CSS]</a></p>
<p>Font names must be interpreted in the context of the
<code><a href="#the-canvas-element">canvas</a></code> element's stylesheets; any fonts embedded using
@@ -26665,7 +26666,7 @@
<code><a href="#the-input-element">input</a></code> element depends on the state of its <code title="attr-input-type"><a href="#attr-input-type">type</a></code> attribute. Similarly, the <code title="dom-input-checked"><a href="#dom-input-checked">checked</a></code>, <code title="dom-input-files"><a href="#dom-input-files">files</a></code>, <code title="dom-input-valueAsDate"><a href="#dom-input-valueasdate">valueAsDate</a></code>, <code title="dom-input-valueAsNumber"><a href="#dom-input-valueasnumber">valueAsNumber</a></code>, <code title="dom-input-list"><a href="#dom-input-list">list</a></code>, and <code title="dom-input-selectedOption"><a href="#dom-input-selectedoption">selectedOption</a></code> DOM
attributes, and the <code title="dom-input-stepUp"><a href="#dom-input-stepup">stepUp()</a></code>
and <code title="dom-input-stepDown"><a href="#dom-input-stepdown">stepDown()</a></code> methods, are
- specific to certain states. The following table <span class="impl">is non-normative and</span> summarises which content
+ specific to certain states. The following table <span class="impl">is non-normative and</span> summarizes which content
attributes, DOM attributes, and methods apply to each state:<table class="applies" id="input-type-attr-summary"><thead><tr><td>
<th> <span title=""><a href="#hidden-state" title="attr-input-type-hidden">Hidden</a></span>
<th> <span title=""><a href="#text-state-and-search-state" title="attr-input-type-text">Text</a>,</span>
@@ -30923,7 +30924,7 @@
more <code><a href="#the-option-element">option</a></code> elements being changed by the user, and
before the relevant user interaction event <!-- interaction event
spec point --> is queued (e.g. before a related <span title="event-click">click</span> event), the user agent must
- <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a> tgat
+ <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a> that
bubbles called <code title="event-change">change</code> at the
<code><a href="#the-select-element">select</a></code> element, using the <a href="#user-interaction-task-source">user interaction task
source</a> as the task source, then <a href="#broadcast-formchange-events">broadcast <code title="event-formchange">formchange</code> events</a> at the
@@ -31467,7 +31468,7 @@
<p>When a <code><a href="#the-textarea-element">textarea</a></code> is <a href="#concept-textarea-mutable" title="concept-textarea-mutable">mutable</a>, its <a href="#concept-textarea-raw-value" title="concept-textarea-raw-value">raw value</a> should be
editable by the user. Any time the user causes the element's <a href="#concept-textarea-raw-value" title="concept-textarea-raw-value">raw value</a> to change, the
user agent must <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple
- event</a> that bubbls called <code title="event-input">input</code> at the <code><a href="#the-textarea-element">textarea</a></code>
+ event</a> that bubbles called <code title="event-input">input</code> at the <code><a href="#the-textarea-element">textarea</a></code>
element, then <a href="#broadcast-forminput-events">broadcast <code title="event-forminput">forminput</code> events</a> at the
<code><a href="#the-textarea-element">textarea</a></code> element's <a href="#form-owner">form owner</a>. User agents
may wait for a suitable break in the user's interaction before
@@ -38242,7 +38243,7 @@
name">predefined global property names</dfn> that can be used for
any item.<h4 id="general"><span class="secno">5.4.1 </span>General</h4><p>The <a href="#predefined-global-property-name">predefined global property name</a> <dfn id="md-about" title="md-about"><code>about</code></dfn> can be used to name an
<a href="#concept-item" title="concept-item">item</a> for the purposes of
- identifying or refering to the data defined in that item.<p>A single property with the name <code title="md-about"><a href="#md-about">about</a></code> may be present within each <a href="#concept-item" title="concept-item">item</a>. Its <a href="#concept-property-value" title="concept-property-value">value</a> must be an
+ identifying or referring to the data defined in that item.<p>A single property with the name <code title="md-about"><a href="#md-about">about</a></code> may be present within each <a href="#concept-item" title="concept-item">item</a>. Its <a href="#concept-property-value" title="concept-property-value">value</a> must be an
<a href="#absolute-url">absolute URL</a>.<h4 id="vcard"><span class="secno">5.4.2 </span>vCard</h4><p>An item with the <a href="#predefined-type">predefined type</a> <dfn id="md-vcard" title="md-vcard"><code>vcard</code></dfn> represents a person's or
organization's contact information.<p>The following are the type's <a href="#predefined-property-name" title="predefined property
name">predefined property names</a>. They are based on the
@@ -38881,11 +38882,11 @@
NINE.</li>
</ol><p>The optional components marked with an asterisk (*) should be
- included, and should have dix digits each.</p>
+ included, and should have six digits each.</p>
<!-- copied from vCard -->
<p class="note">The value specifies latitude and longitude, in
- that order (i.e., "LAT LON" ordering), in decimal degress. The
+ that order (i.e., "LAT LON" ordering), in decimal degrees. The
longitude represents the location east and west of the prime
meridian as a positive or negative real number, respectively. The
latitude represents the location north and south of the equator as
@@ -39554,14 +39555,14 @@
NINE.</li>
</ol><p>The optional components marked with an asterisk (*) should be
- included, and should have dix digits each.</p> <!-- iCalendar
+ included, and should have six digits each.</p> <!-- iCalendar
actually limits the range to -91.0 < lat < 91.0; -181.0 < long <
181.0, which seems weird. It also gives special meanings to
+90/-90 lat, and +180 long. -->
<!-- copied from vcard (not icalendar!) -->
<p class="note">The value specifies latitude and longitude, in
- that order (i.e., "LAT LON" ordering), in decimal degress. The
+ that order (i.e., "LAT LON" ordering), in decimal degrees. The
longitude represents the location east and west of the prime
meridian as a positive or negative real number, respectively. The
latitude represents the location north and south of the equator as
@@ -40071,7 +40072,7 @@
</dl><p>In addition, exactly one property with the name <code title="md-about"><a href="#md-about">about</a></code> must be present within each <a href="#concept-item" title="concept-item">item</a> with the type <code title="md-work"><a href="#md-work">work</a></code>, giving the <a href="#url">URL</a> of the
work.<h5 id="examples-1"><span class="secno">5.4.4.1 </span>Examples</h5><div class="example">
- <p>This example shows an embedded image entitiled <cite>My
+ <p>This example shows an embedded image entitled <cite>My
Pond</cite>, licensed under the Creative Commons Attribution-Share
Alike 3.0 United States License and the MIT license
simultaneously.</p>
@@ -40097,7 +40098,7 @@
iterate over a series of elements (whether items, properties, or
otherwise) must do so in <a href="#tree-order">tree order</a>.</p>
- <p>A generic API upon which the vocaulary-specific conversions
+ <p>A generic API upon which the vocabulary-specific conversions
defined below (vCard, iCalendar) can be built will need to provide
the following information when given a <code>Document</code> (or
equivalent):</p>
@@ -40945,8 +40946,8 @@
<li><p><a href="#add-an-icalendar-line">Add an iCalendar line</a> with the type "<code title="">BEGIN</code>" and the value "<code title="">VCALENDAR</code>"
to <var title="">output</var>.</li>
- <li><p><a href="#add-an-icalendar-line">Add an iCalendar line</a> with the type "<code title="">PRODID</code>" and the value equal to a user-agent
- specific string representing the user agent to <var title="">output</var>.</li>
+ <li><p><a href="#add-an-icalendar-line">Add an iCalendar line</a> with the type "<code title="">PRODID</code>" and the value equal to a
+ user-agent-specific string representing the user agent to <var title="">output</var>.</li>
<li><p><a href="#add-an-icalendar-line">Add an iCalendar line</a> with the type "<code title="">VERSION</code>" and the value "<code title="">2.0</code>"
to <var title="">output</var>.</li>
@@ -41034,7 +41035,7 @@
</ol><p>When the above algorithm says that the user agent is to <dfn id="add-an-icalendar-line">add
an iCalendar line</dfn> consisting of a type <var title="">type</var>, a value <var title="">value</var>, and
- optinally an annotation, to a string <var title="">output</var>, it
+ optionally an annotation, to a string <var title="">output</var>, it
must run the following steps:</p>
<ol><li><p>Let <var title="">line</var> be an empty string.</li>
@@ -41175,7 +41176,7 @@
<p>Optionally: Let <var title="">x</var> be a <code title="">link</code> element in the <a href="#atom-namespace">Atom
namespace</a>. Add a <code title="">rel</code> attribute whose
value is the string "<code title="">self</code>" to <var title="">x</var>. Append a text node with its data set to the
- (user-agent defined) <a href="#the-document-s-address" title="the document's
+ (user-agent-defined) <a href="#the-document-s-address" title="the document's
address">address</a> of <var title="">R</var> to <var title="">x</var>. Append <var title="">x</var> to the root element
of <var title="">R</var>.</p>
@@ -41427,7 +41428,7 @@
<dd>Let <var title="">id</var> be the <a href="#absolute-url">absolute URL</a>
resulting from <a href="#resolve-a-url" title="resolve a url">resolving</a> the
value of the <code title="attr-hyperlink-href"><a href="#attr-hyperlink-href">href</a></code>
- attribute of the first such <code><a href="#the-a-element">a</a></code> ot <code><a href="#the-area-element">area</a></code>
+ attribute of the first such <code><a href="#the-a-element">a</a></code> or <code><a href="#the-area-element">area</a></code>
element, relative to the element. Let <var title="">has-alternate</var> be true.</dd>
<dt>If the <var title="">article</var> node has an <code title="attr-id"><a href="#the-id-attribute">id</a></code> attribute</dt>
@@ -41439,8 +41440,8 @@
<dt>Otherwise</dt>
- <dd>Let <var title="">id</var> be a user-agent defined
- undereferencable yet globally unique <a href="#absolute-url">absolute
+ <dd>Let <var title="">id</var> be a user-agent-defined
+ undereferenceable yet globally unique <a href="#absolute-url">absolute
URL</a>. Let <var title="">has-alternate</var> be
false.</dd>
@@ -41739,7 +41740,7 @@
container</a> for <var title="">b</var>.</li>
</ol></div><h4 id="auxiliary-browsing-contexts"><span class="secno">6.1.2 </span>Auxiliary browsing contexts</h4><p>It is possible to create new browsing contexts that are related
- to a <span>top level browsing context</span> without being nested
+ to a <a href="#top-level-browsing-context">top-level browsing context</a> without being nested
through an element. Such browsing contexts are called <dfn id="auxiliary-browsing-context" title="auxiliary browsing context">auxiliary browsing
contexts</dfn>. Auxiliary browsing contexts are always <a href="#top-level-browsing-context" title="top-level browsing context">top-level browsing
contexts</a>.<p>An <a href="#auxiliary-browsing-context">auxiliary browsing context</a> has an <dfn id="opener-browsing-context">opener
@@ -42571,7 +42572,7 @@
its own trust domain (e.g. it identifies an e-mail on an IMAP
server or a post on an NNTP server) then return a globally unique
identifier specific to the resource identified by <var title="">url</var>, so that if this algorithm is invoked again
- for <a href="#url" title="URL">URLs</a> that identify the same resouce,
+ for <a href="#url" title="URL">URLs</a> that identify the same resource,
the same identifier will be returned.</li>
<li><p>If <var title="">url</var> does not use a server-based
@@ -44088,7 +44089,7 @@
exactly on schedule. Delays due to CPU load, other tasks, etc, are
to be expected.<div class="impl">
- <p class="note">The <code><a href="#windowtimers">WindowTimers</a></code> interfaceadds to the
+ <p class="note">The <code><a href="#windowtimers">WindowTimers</a></code> interface adds to the
<code><a href="#window">Window</a></code> interface and the <code>WorkerUtils</code>
interface (part of Web Workers).</p>
@@ -44111,7 +44112,7 @@
<var title="">timeout</var> is less than 4, then increase <var title="">timeout</var> to 4.</li>
<li><p>Add an entry to the <a href="#list-of-active-timeouts">list of active timeouts</a>,
- identified by a user-agent defined integer that is greater than
+ identified by a user-agent-defined integer that is greater than
zero.</li>
<li><p>Return the number identifying the newly added entry in the
@@ -44164,7 +44165,7 @@
note below about IE) -->
<li><p>Add an entry to the <a href="#list-of-active-intervals">list of active intervals</a>,
- identified by a user-agent defined integer that is greater than
+ identified by a user-agent-defined integer that is greater than
zero.</li>
<li><p>Return the number identifying the newly added entry in the
@@ -47766,7 +47767,7 @@
<li><p>If <a href="#the-document-s-address">the document's address</a> has a fragment
identifier, then run these substeps:</p>
- <ol><li><p>Wait for a user-agent defined amount of time, as desired
+ <ol><li><p>Wait for a user-agent-defined amount of time, as desired
by the user agent implementor. (This is intended to allow the
user agent to optimize the user experience in the face of
performance concerns.)</li>
@@ -47912,7 +47913,7 @@
<a href="#update-the-session-history-with-the-new-page">update the session history with the new page</a>.</p>
<p>User agents may add content to the <code><a href="#the-head-element-0">head</a></code> element of
- the <code>Document</code>, e.g. linking to stylesheet or an XBL
+ the <code>Document</code>, e.g. linking to a style sheet or an XBL
binding, providing script, giving the document a <code><a href="#the-title-element-0">title</a></code>,
etc.</p>
@@ -47945,8 +47946,8 @@
<p>User agents may add content to the <code><a href="#the-head-element-0">head</a></code> element of
the <code>Document</code>, or attributes to the <code><a href="#the-img-element">img</a></code>
- element, e.g. to link to stylesheet or an XBL binding, to provide a
- script, to give the document a <code><a href="#the-title-element-0">title</a></code>, etc.</p>
+ element, e.g. to link to a style sheet or an XBL binding, to provide
+ a script, to give the document a <code><a href="#the-title-element-0">title</a></code>, etc.</p>
<h4 id="read-plugin"><span class="secno">6.11.6 </span><dfn title="navigate-plugin">Page load processing model for content that uses plugins</dfn></h4>
@@ -47978,7 +47979,7 @@
<p>User agents may add content to the <code><a href="#the-head-element-0">head</a></code> element of
the <code>Document</code>, or attributes to the <code><a href="#the-embed-element">embed</a></code>
- element, e.g. to link to stylesheet or an XBL binding, or to give
+ element, e.g. to link to a style sheet or an XBL binding, or to give
the document a <code><a href="#the-title-element-0">title</a></code>.</p>
<p class="note" id="sandboxPluginNavigate">If the <a href="#sandboxed-plugins-browsing-context-flag">sandboxed
@@ -48929,7 +48930,7 @@
<html>
<head>
<title>Exampl Pictures: Kissat</title>
- <link rel="stylesheet href="/style/default">
+ <link rel="stylesheet" href="/style/default">
</head>
<body>
<h1>Kissat</h1>
@@ -49742,7 +49743,7 @@
</ol></li>
<li><p><i>Fallback</i>: Optionally, the user agent may assign a key
- combination of its chosing as the element's <a href="#assigned-access-key">assigned access
+ combination of its choosing as the element's <a href="#assigned-access-key">assigned access
key</a> and then abort these steps.</li>
<li><p>If this step is reached, the element has no <a href="#assigned-access-key">assigned
@@ -53987,7 +53988,7 @@
condition to the user if one or more parse error conditions exist in
the document and must not report parse error conditions if none
exist in the document. Conformance checkers may report more than one
- parse error condition if more than one parse error conditions exist
+ parse error condition if more than one parse error condition exists
in the document. Conformance checkers are not required to recover
from parse errors.</p>
@@ -54773,7 +54774,8 @@
<code><a href="#the-section-element">section</a></code>, <code><a href="#the-select-element">select</a></code>, <code><a href="#spacer">spacer</a></code>,
<code><a href="#the-style-element">style</a></code>, <code><a href="#the-tbody-element">tbody</a></code>, <code><a href="#the-textarea-element">textarea</a></code>,
<code><a href="#the-tfoot-element">tfoot</a></code>, <code><a href="#the-thead-element">thead</a></code>, <code><a href="#the-title-element-0">title</a></code>,
- <code><a href="#the-tr-element">tr</a></code>, <code><a href="#the-ul-element">ul</a></code>, and <code>wbr</code>.</dd>
+ <code><a href="#the-tr-element">tr</a></code>, <code><a href="#the-ul-element">ul</a></code>, <code>wbr</code>, and
+ <code><a href="#xmp">xmp</a></code>.</dd>
<dt><dfn id="scoping">Scoping</dfn></dt>
<dd><p>The following HTML elements introduce new <a href="#has-an-element-in-scope" title="has
Received on Friday, 28 August 2009 19:42:54 UTC