- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 06 May 2011 02:48:18 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/markup/html5-spec
In directory hutz:/tmp/cvs-serv9531/html5-spec
Modified Files:
Overview.html association-of-controls-and-forms.html
common-dom-interfaces.html
common-input-element-attributes.html common-microsyntaxes.html
fetching-resources.html infrastructure.html introduction.html
number-state.html obsolete.html rendering.html
scripting-1.html sections.html spec.html
the-canvas-element.html the-iframe-element.html
webappapis.html
Log Message:
Fixed assertions for alt-less img.
Index: infrastructure.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/infrastructure.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- infrastructure.html 5 May 2011 18:12:08 -0000 1.10
+++ infrastructure.html 6 May 2011 02:48:14 -0000 1.11
@@ -1308,7 +1308,7 @@
<dt>One byte in the range 80 to BF preceded by a byte that is part of a complete UTF-8 sequence that does not include this byte</dt>
- <dt>One byte in the range 80 to BF preceded by a byte that is part of a sequence that has been replaced by a U+FFFD REPLACEMENT CHARACTER, either alone or as port of a sequence</dt>
+ <dt>One byte in the range 80 to BF preceded by a byte that is part of a sequence that has been replaced by a U+FFFD REPLACEMENT CHARACTER, either alone or as part of a sequence</dt>
<dd>Each such byte must be replaced with a U+FFFD REPLACEMENT CHARACTER.</dd>
Index: scripting-1.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/scripting-1.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- scripting-1.html 5 May 2011 18:12:09 -0000 1.9
+++ scripting-1.html 6 May 2011 02:48:14 -0000 1.10
@@ -1141,12 +1141,12 @@
form.elements.result.value = price;
}
</script>
-<form name="pricecalc" onsubmit="return false">
+<form name="pricecalc" onsubmit="return false" onchange="calculate(this)">
<fieldset>
<legend>Work out the price of your car</legend>
<p>Base cost: £52000.</p>
<p>Select additional options:</p>
- <ul onchange="calculate(form)">
+ <ul>
<li><label><input type=checkbox name=brakes> Ceramic brakes (£1000)</label></li>
<li><label><input type=checkbox name=radio> Satellite radio (£2500)</label></li>
<li><label><input type=checkbox name=turbo> Turbo charger (£5000)</label></li>
Index: the-canvas-element.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/the-canvas-element.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- the-canvas-element.html 5 May 2011 18:12:09 -0000 1.10
+++ the-canvas-element.html 6 May 2011 02:48:15 -0000 1.11
@@ -399,10 +399,13 @@
instead.</p><!-- CANVAS-FOCUS-FALLBACK --><p>When a <code><a href="#the-canvas-element">canvas</a></code> element <a href="rendering.html#represents">represents</a>
<a href="content-models.html#embedded-content">embedded content</a>, the user can still focus descendants
of the <code><a href="#the-canvas-element">canvas</a></code> element (in the <a href="content-models.html#fallback-content">fallback
- content</a>). This allows authors to make an interactive canvas
- keyboard-focusable: authors should have a one-to-one mapping of
+ content</a>). When an element is focused, it is the target of
+ keyboard interaction events (even though the element itself is not
+ visible). This allows authors to make an interactive canvas
+ keyboard-accessible: authors should have a one-to-one mapping of
interactive regions to focusable elements in the <a href="content-models.html#fallback-content">fallback
- content</a>.</p><p>The <code><a href="#the-canvas-element">canvas</a></code> element has two attributes to control the
+ content</a>. (Focus has no effect on mouse interaction
+ events.) <a href="#DOMEVENTS">[DOMEVENTS]</a></p><p>The <code><a href="#the-canvas-element">canvas</a></code> element has two attributes to control the
size of the coordinate space: <dfn id="attr-canvas-width" title="attr-canvas-width"><code>width</code></dfn> and <dfn id="attr-canvas-height" title="attr-canvas-height"><code>height</code></dfn>. These
attributes, when specified, must have values that are <a href="common-microsyntaxes.html#valid-non-negative-integer" title="valid non-negative integer">valid non-negative
integers</a>. <span class="impl">The <a href="common-microsyntaxes.html#rules-for-parsing-non-negative-integers">rules for parsing
Index: the-iframe-element.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/the-iframe-element.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- the-iframe-element.html 5 May 2011 18:12:09 -0000 1.10
+++ the-iframe-element.html 6 May 2011 02:48:15 -0000 1.11
@@ -1549,7 +1549,7 @@
resource's Content-Type metadata</a> is
"<code>text/plain</code>", and the result of applying the
<a href="fetching-resources.html#content-type-sniffing:-text-or-binary" title="Content-Type sniffing: text or binary">rules
- for distingushing if a resource is text or binary</a>
+ for distinguishing if a resource is text or binary</a>
to the resource is that the resource is not
<code>text/plain</code>, then set <var title="">binary</var> to true.</p>
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/Overview.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- Overview.html 5 May 2011 18:12:05 -0000 1.13
+++ Overview.html 6 May 2011 02:48:12 -0000 1.14
@@ -342,7 +342,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-5-may-2011">Editor's Draft 5 May 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-6-may-2011">Editor's Draft 6 May 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -482,7 +482,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 5 May 2011 Editor's Draft.
+ This specification is the 6 May 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -1934,10 +1934,10 @@
<div class="example">
<p>In the fragments below, for example, the semantics are
- nonsensical: a row cannot simultaneously be a cell, nor can a
- radio button be a progress bar.</p>
+ nonsensical: a separator cannot simultaneously be a cell, nor can
+ a radio button be a progress bar.</p>
- <pre class="bad"><tr role="cell"></pre>
+ <pre class="bad"><hr role="cell"></pre>
<pre class="bad"><input type=radio role=progressbar></pre>
</div>
@@ -3189,7 +3189,7 @@
<dt>One byte in the range 80 to BF preceded by a byte that is part of a complete UTF-8 sequence that does not include this byte</dt>
- <dt>One byte in the range 80 to BF preceded by a byte that is part of a sequence that has been replaced by a U+FFFD REPLACEMENT CHARACTER, either alone or as port of a sequence</dt>
+ <dt>One byte in the range 80 to BF preceded by a byte that is part of a sequence that has been replaced by a U+FFFD REPLACEMENT CHARACTER, either alone or as part of a sequence</dt>
<dd>Each such byte must be replaced with a U+FFFD REPLACEMENT CHARACTER.</dd>
@@ -3511,6 +3511,15 @@
<li>If <var title="">position</var> is past the end of <var title="">input</var>, return an error.</li>
+ </ol><p>Otherwise, if the character indicated by <var title="">position</var> (the first character) is a U+002B PLUS
+ SIGN character (+):</p>
+
+ <ol><li>Advance <var title="">position</var> to the next
+ character. (The "<code title="">+</code>" is ignored, but it is
+ not conforming.)</li>
+
+ <li>If <var title="">position</var> is past the end of <var title="">input</var>, return an error.</li>
+
</ol></li>
<li><p>If the character indicated by <var title="">position</var>
@@ -3532,10 +3541,16 @@
character.</p></li>
<li><p>If <var title="">position</var> is past the end of <var title="">input</var>, or if the character indicated by <var title="">position</var> is not one of U+0030 DIGIT ZERO (0) to
- U+0039 DIGIT NINE (9), then jump to the step labeled
+ U+0039 DIGIT NINE (9), U+0065 LATIN SMALL LETTER E (e), or U+0045
+ LATIN CAPITAL LETTER E (E), then jump to the step labeled
<i>conversion</i>.</p></li>
- <li><p><i>Fraction loop</i>: Multiply <var title="">divisor</var>
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+0065 LATIN SMALL LETTER E character (e) or a U+0045 LATIN
+ CAPITAL LETTER E character (E), skip the remainder of these
+ substeps.</p>
+
+ </li><li><p><i>Fraction loop</i>: Multiply <var title="">divisor</var>
by ten.</p></li>
<li>Add the value of the character indicated by <var title="">position</var>, interpreted as a base-ten digit (0..9)
@@ -5973,7 +5988,7 @@
sequence of octets. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
<p>The <dfn id="content-type-sniffing:-image" title="Content-Type sniffing: image">rules for sniffing
- images specifically</dfn> and the <dfn id="content-type-sniffing:-text-or-binary" title="Content-Type sniffing: text or binary">rules for distingushing if a resource is text or
+ images specifically</dfn> and the <dfn id="content-type-sniffing:-text-or-binary" title="Content-Type sniffing: text or binary">rules for distinguishing if a resource is text or
binary</dfn> are also defined in the Media Type Sniffing
specification. Both sets of rules return a <a href="#mime-type">MIME type</a> as
their result. <a href="#refsMIMESNIFF">[MIMESNIFF]</a></p>
@@ -6761,12 +6776,12 @@
<li>Otherwise, <a href="#split-a-string-on-spaces" title="split a string on spaces">split the
underlying string on spaces</a> to get the list of tokens in the
- object's underlying string.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</li>
<li>If the token indicated by <var title="">token</var> is a
<a href="#case-sensitive">case-sensitive</a> match for one of the tokens in the
- object's underlying string then return true and stop this
- algorithm.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string then return
+ true and stop this algorithm.</li>
<li>Otherwise, return false.</li>
@@ -6783,7 +6798,7 @@
<li>Otherwise, <a href="#split-a-string-on-spaces" title="split a string on spaces">split the
underlying string on spaces</a> to get the list of tokens in the
- object's underlying string.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</li>
<li>If the given <var title="">token</var> is a
<a href="#case-sensitive">case-sensitive</a> match for one of the tokens in the
@@ -6826,7 +6841,7 @@
<li>Otherwise, <a href="#split-a-string-on-spaces" title="split a string on spaces">split the
underlying string on spaces</a> to get the list of tokens in the
- object's underlying string.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</li>
<li>If the given <var title="">token</var> is a
<a href="#case-sensitive">case-sensitive</a> match for one of the tokens in the
@@ -6843,9 +6858,8 @@
<li>Return true.</li>
- </ol><p>Objects implementing the <code><a href="#domtokenlist">DOMTokenList</a></code> interface must
- <dfn id="dom-tokenlist-tostring" title="dom-tokenlist-toString">stringify</dfn> to the object's
- underlying string representation.</p>
+ </ol><p>A <code><a href="#domtokenlist">DOMTokenList</a></code> object must <dfn id="dom-tokenlist-tostring" title="dom-tokenlist-toString">stringify</dfn> to the value of the
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</p>
</div><h4 id="domsettabletokenlist-0"><span class="secno">2.8.4 </span>DOMSettableTokenList</h4><p>The <code><a href="#domsettabletokenlist">DOMSettableTokenList</a></code> interface is the same as the
<code><a href="#domtokenlist">DOMTokenList</a></code> interface, except that it allows the
@@ -6977,7 +6991,7 @@
<li>
<p>If <var title="">input</var> is an Array object or an Object
- object, then, for each enumerable property in <var title="">input</var>, add a corresponding property to <var title="">output</var> having the same name, and having a value
+ object, then, for each enumerable property in <var title="">input</var>, add a new property to <var title="">output</var> having the same name, and having a value
created from invoking the <a href="#internal-structured-cloning-algorithm">internal structured cloning
algorithm</a> recursively with the value of the property as the
"<var title="">input</var>" argument and <var title="">memory</var> as the "<var title="">memory</var>"
@@ -6986,6 +7000,12 @@
<p class="note">This does not walk the prototype chain.</p>
+ <p class="note">Property descriptors, setters, getters, and
+ analogous features are not copied in this process. For example,
+ the property in the input could be marked as read-only, but in the
+ output it would just have the default state (typically read-write,
+ though that could depend on the scripting environment).</p>
+
</li>
<li><p>Return <var title="">output</var>.</p></li>
@@ -13251,12 +13271,12 @@
form.elements.result.value = price;
}
</script>
-<form name="pricecalc" onsubmit="return false">
+<form name="pricecalc" onsubmit="return false" onchange="calculate(this)">
<fieldset>
<legend>Work out the price of your car</legend>
<p>Base cost: £52000.</p>
<p>Select additional options:</p>
- <ul onchange="calculate(form)">
+ <ul>
<li><label><input type=checkbox name=brakes> Ceramic brakes (£1000)</label></li>
<li><label><input type=checkbox name=radio> Satellite radio (£2500)</label></li>
<li><label><input type=checkbox name=turbo> Turbo charger (£5000)</label></li>
@@ -14392,17 +14412,17 @@
for its nearest ancestor <a href="#sectioning-content">sectioning content</a> or
<a href="#sectioning-root">sectioning root</a> element. A footer typically contains
information about its section such as who wrote it, links to related
- documents, copyright data, and the like.</p><p class="note">Contact information for the author or editor of a
- section belongs in an <code><a href="#the-address-element">address</a></code> element, possibly itself
- inside a <code><a href="#the-footer-element">footer</a></code>.</p><p>Footers don't necessarily have to appear at the <em>end</em> of a
- section, though they usually do.</p><p>When the <code><a href="#the-footer-element">footer</a></code> element contains entire sections,
+ documents, copyright data, and the like.</p><p>When the <code><a href="#the-footer-element">footer</a></code> element contains entire sections,
they <a href="#represents" title="represents">represent</a> appendices, indexes,
long colophons, verbose license agreements, and other such
- content.</p><p class="note">The <code><a href="#the-footer-element">footer</a></code> element is not
- <a href="#sectioning-content">sectioning content</a>; it doesn't introduce a new
- section.</p><p>When the nearest ancestor <a href="#sectioning-content">sectioning content</a> or
+ content.</p><p class="note">Contact information for the author or editor of a
+ section belongs in an <code><a href="#the-address-element">address</a></code> element, possibly itself
+ inside a <code><a href="#the-footer-element">footer</a></code>.</p><p>Footers don't necessarily have to appear at the <em>end</em> of a
+ section, though they usually do.</p><p>When the nearest ancestor <a href="#sectioning-content">sectioning content</a> or
<a href="#sectioning-root">sectioning root</a> element is <a href="#the-body-element-0">the body
- element</a>, then it applies to the whole page.</p><div class="example">
+ element</a>, then it applies to the whole page.</p><p class="note">The <code><a href="#the-footer-element">footer</a></code> element is not
+ <a href="#sectioning-content">sectioning content</a>; it doesn't introduce a new
+ section.</p><div class="example">
<p>Here is a page with two footers, one at the top and one at the
bottom, with the same content:</p>
@@ -14463,6 +14483,45 @@
</BODY>
</HTML></pre>
+ </div><div class="example">
+
+ <p>Some site designs have what is sometimes referred to as "fat
+ footers" — footers that contain a lot of material, including
+ images, links to other articles, links to pages for sending
+ feedback, special offers... in some ways, a whole "front page" in
+ the footer.</p>
+
+ <p>This fragment shows the bottom of a page on a site with a "fat
+ footer":</p>
+
+ <pre>...
+ <footer>
+ <nav>
+ <section>
+ <h1>Articles</h1>
+ <p><img src="http://dev.w3.org/html5/spec/images/somersaults.jpeg" alt=""> Go to the gym with
+ our somersaults class! Our teacher Jim takes you through the paces
+ in this two-part article. <a href="articles/somersaults/1">Part
+ 1</a> · <a href="articles/somersaults/1">Part 2</a></p>
+ <p><img src="http://dev.w3.org/html5/spec/images/kindplus.jpeg"> Tired of walking on the edge of
+ a clif<!-- sic -->? Our guest writer Lara shows you how to bumble
+ your way through the bars. <a href="articles/kindplus/1">Read
+ more...</a></p>
+ <p><img src="http://dev.w3.org/html5/spec/images/crisps.jpeg"> The chips are down, now all
+ that's left is a potato. What can you do with it? <a
+ href="articles/crisps/1">Read more...</a></p>
+ </section>
+ <ul>
+ <li> <a href="/about">About us...</a>
+ <li> <a href="/feedback">Send feedback!</a>
+ <li> <a href="/sitemap">Sitemap</a>
+ </ul>
+ </nav>
+ <p><small>Copyright © 2015 The Snacker —
+ <a href="/tos">Terms of Service</a></small></p>
+ </footer>
+</body></pre>
+
</div><h4 id="the-address-element"><span class="secno">4.4.10 </span>The <dfn><code>address</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
<dd><a href="#flow-content">Flow content</a>.</dd>
<dd><a href="#formatblock-candidate"><code title="">formatBlock</code> candidate</a>.</dd>
@@ -14756,8 +14815,8 @@
the first relevant step below for each element as you enter and
exit it.</p>
- <dl class="switch"><dt>If the top of the stack is an element, and you are exiting
- that element</dt>
+ <dl class="switch"><dt>If you are exiting an element and that element is the element
+ at the top of the stack</dt>
<dd>
@@ -14793,6 +14852,8 @@
<p>Let <var title="">current section</var> be a newly created
<a href="#concept-section" title="concept-section">section</a> for the <var title="">current outlinee</var> element.</p>
+ <p>Associate <var title="">current outlinee</var> with <var title="">current section</var>.</p>
+
<p>Let there be a new <a href="#outline">outline</a> for the new <var title="">current outlinee</var>, initialized with just the new
<var title="">current section</var> as the only <a href="#concept-section" title="concept-section">section</a> in the outline.</p>
@@ -14915,9 +14976,9 @@
<dd><p>Do nothing.</p></dd>
</dl><p id="associatedSection">In addition, whenever you exit a node,
- after doing the steps above, if <var title="">current
- section</var> is not null, associate the node with the <a href="#concept-section" title="concept-section">section</a> <var title="">current
- section</var>.</p>
+ after doing the steps above, if the node is not associated with a
+ <a href="#concept-section" title="concept-section">section</a> yet and <var title="">current section</var> is not null, associate the node
+ with the <a href="#concept-section" title="concept-section">section</a> <var title="">current section</var>.</p>
</li>
@@ -20472,7 +20533,7 @@
resource's Content-Type metadata</a> is
"<code>text/plain</code>", and the result of applying the
<a href="#content-type-sniffing:-text-or-binary" title="Content-Type sniffing: text or binary">rules
- for distingushing if a resource is text or binary</a>
+ for distinguishing if a resource is text or binary</a>
to the resource is that the resource is not
<code>text/plain</code>, then set <var title="">binary</var> to true.</p>
@@ -26620,10 +26681,13 @@
instead.</p><!-- CANVAS-FOCUS-FALLBACK --><p>When a <code><a href="#the-canvas-element">canvas</a></code> element <a href="#represents">represents</a>
<a href="#embedded-content">embedded content</a>, the user can still focus descendants
of the <code><a href="#the-canvas-element">canvas</a></code> element (in the <a href="#fallback-content">fallback
- content</a>). This allows authors to make an interactive canvas
- keyboard-focusable: authors should have a one-to-one mapping of
+ content</a>). When an element is focused, it is the target of
+ keyboard interaction events (even though the element itself is not
+ visible). This allows authors to make an interactive canvas
+ keyboard-accessible: authors should have a one-to-one mapping of
interactive regions to focusable elements in the <a href="#fallback-content">fallback
- content</a>.</p><p>The <code><a href="#the-canvas-element">canvas</a></code> element has two attributes to control the
+ content</a>. (Focus has no effect on mouse interaction
+ events.) <a href="#DOMEVENTS">[DOMEVENTS]</a></p><p>The <code><a href="#the-canvas-element">canvas</a></code> element has two attributes to control the
size of the coordinate space: <dfn id="attr-canvas-width" title="attr-canvas-width"><code>width</code></dfn> and <dfn id="attr-canvas-height" title="attr-canvas-height"><code>height</code></dfn>. These
attributes, when specified, must have values that are <a href="#valid-non-negative-integer" title="valid non-negative integer">valid non-negative
integers</a>. <span class="impl">The <a href="#rules-for-parsing-non-negative-integers">rules for parsing
@@ -33875,11 +33939,11 @@
false. The <a href="#activation-behavior">activation behavior</a> is to <a href="#fire-a-simple-event">fire a
simple event</a> that bubbles named <code title="event-change">change</code> at the element. .</p>
- <p><strong>Constraint validation</strong>: If the element is <i title="concept-input-required"><a href="#concept-input-required">required</a></i> and all of the
+ <p><strong>Constraint validation</strong>: If an element in the
+ <i><a href="#radio-button-group">radio button group</a></i> is <i title="concept-input-required"><a href="#concept-input-required">required</a></i>, and all of the
<code><a href="#the-input-element">input</a></code> elements in the <i><a href="#radio-button-group">radio button group</a></i> have a
- <a href="#concept-fe-checked" title="concept-fe-checked">checkedness</a> that is
- false, then the element is <a href="#suffering-from-being-missing">suffering from being
- missing</a>.</p>
+ <a href="#concept-fe-checked" title="concept-fe-checked">checkedness</a> that is false,
+ then the element is <a href="#suffering-from-being-missing">suffering from being missing</a>.</p>
</div><p class="note">If none of the radio buttons in a <a href="#radio-button-group">radio button
group</a> are checked when they are inserted into the document,
@@ -34005,7 +34069,7 @@
<p>User agents should prevent the user from selecting files that are
not accepted by one (or more) of these tokens.</p>
- </div><div class="example">
+ </div><div class="example" id="fakepath-srsly">
<p>For historical reasons, the <code title="dom-input-value"><a href="#dom-input-value">value</a></code> IDL attribute prefixes the
filename with the string "<code title="">C:\fakepath\</code>". Some
@@ -35249,34 +35313,56 @@
<dl><dt><dfn id="dom-input-value-value" title="dom-input-value-value">value</dfn>
- </dt><dd>On getting, it must return the current <a href="#concept-fe-value" title="concept-fe-value">value</a> of the element. On setting,
- it must set the element's <a href="#concept-fe-value" title="concept-fe-value">value</a> to the new value, set the
- element's <a href="#concept-input-value-dirty-flag" title="concept-input-value-dirty-flag">dirty value
- flag</a> to true, and then invoke the <a href="#value-sanitization-algorithm">value sanitization
- algorithm</a>, if the element's <code title="attr-input-type"><a href="#attr-input-type">type</a></code> attribute's current state
- defines one.</dd>
+ </dt><dd>
+
+ <p>On getting, it must return the current <a href="#concept-fe-value" title="concept-fe-value">value</a> of the element. On setting,
+ it must set the element's <a href="#concept-fe-value" title="concept-fe-value">value</a> to the new value, set the
+ element's <a href="#concept-input-value-dirty-flag" title="concept-input-value-dirty-flag">dirty value
+ flag</a> to true, and then invoke the <a href="#value-sanitization-algorithm">value sanitization
+ algorithm</a>, if the element's <code title="attr-input-type"><a href="#attr-input-type">type</a></code> attribute's current state
+ defines one.</p>
+
+ </dd>
<dt><dfn id="dom-input-value-default" title="dom-input-value-default">default</dfn>
- </dt><dd>On getting, if the element has a <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute, it must return
- that attribute's value; otherwise, it must return the empty
- string. On setting, it must set the element's <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute to the new
- value.</dd>
+ </dt><dd>
+
+ <p>On getting, if the element has a <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute, it must return
+ that attribute's value; otherwise, it must return the empty
+ string. On setting, it must set the element's <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute to the new
+ value.</p>
+
+ </dd>
<dt><dfn id="dom-input-value-default-on" title="dom-input-value-default-on">default/on</dfn>
- </dt><dd>On getting, if the element has a <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute, it must return
- that attribute's value; otherwise, it must return the string "<code title="">on</code>". On setting, it must set the element's <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute to the new
- value.</dd>
+ </dt><dd>
+
+ <p>On getting, if the element has a <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute, it must return
+ that attribute's value; otherwise, it must return the string
+ "<code title="">on</code>". On setting, it must set the element's
+ <code title="attr-input-value"><a href="#attr-input-value">value</a></code> attribute to the new
+ value.</p>
+
+ </dd>
<dt><dfn id="dom-input-value-filename" title="dom-input-value-filename">filename</dfn>
- </dt><dd>On getting, it must return the string "<code title="">C:\fakepath\</code>" followed by the filename of the first
- file in the list of <a href="#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>, if
- any, or the empty string if the list is empty. On setting, if the
- new value is the empty string, it must empty the list of <a href="#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>;
- otherwise, it must throw an <code><a href="#invalid_state_err">INVALID_STATE_ERR</a></code>
- exception.</dd>
+ </dt><dd id="fakepath-orly">
+
+ <p>On getting, it must return the string "<code title="">C:\fakepath\</code>" followed by the filename of the
+ first file in the list of <a href="#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>, if
+ any, or the empty string if the list is empty. On setting, if the
+ new value is the empty string, it must empty the list of <a href="#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>;
+ otherwise, it must throw an <code><a href="#invalid_state_err">INVALID_STATE_ERR</a></code>
+ exception.</p>
+
+ <p class="note">This "fakepath" requirement is a sad accident of
+ history. See <a href="#fakepath-srsly">the example in the File
+ Upload state section</a> for more information.</p>
+
+ </dd>
</dl><hr/><p>The <dfn id="dom-input-checked" title="dom-input-checked"><code>checked</code></dfn> IDL
attribute allows scripts to manipulate the <a href="#concept-fe-checked" title="concept-fe-checked">checkedness</a> of an
@@ -38130,7 +38216,9 @@
<dd> <p>When a control has no <a href="#concept-fe-value" title="concept-fe-value">value</a> but has a <code title="">required</code> attribute (<code><a href="#the-input-element">input</a></code> <code title="attr-input-required"><a href="#attr-input-required">required</a></code>, <code><a href="#the-select-element">select</a></code>
<code title="attr-select-required"><a href="#attr-select-required">required</a></code>,
- <code><a href="#the-textarea-element">textarea</a></code> <code title="attr-textarea-required"><a href="#attr-textarea-required">required</a></code>). </p></dd>
+ <code><a href="#the-textarea-element">textarea</a></code> <code title="attr-textarea-required"><a href="#attr-textarea-required">required</a></code>), or, in the case of
+ an element in a <i><a href="#radio-button-group">radio button group</a></i>, any of the other
+ elements in the group has a <code title="attr-input-required"><a href="#attr-input-required">required</a></code> attribute. </p></dd>
<dt> <dfn id="suffering-from-a-type-mismatch">Suffering from a type mismatch</dfn> </dt>
@@ -38706,7 +38794,7 @@
<dd>Let <var title="">MIME type</var> be the concatenation of
the string "<code title="">multipart/form-data;</code>", a
- U+0020 SPACE character, and the <a href="#multipart-form-data-boundary-string"><code title="">multipart/form-data</code> boundary string</a>
+ U+0020 SPACE character, the string "<code title="">boundary=</code>", and the <a href="#multipart-form-data-boundary-string"><code title="">multipart/form-data</code> boundary string</a>
generated by the <a href="#multipart-form-data-encoding-algorithm"><code title="">multipart/form-data</code> encoding
algorithm</a>.</dd>
@@ -48322,10 +48410,12 @@
<li>
<p>If <var title="">body</var> is not parsable as
- <i>FunctionBody</i> then abort these steps.</p>
+ <i>FunctionBody</i> or if parsing detects an <i>early error</i>
+ then abort these steps.</p>
<p class="note"><i>FunctionBody</i> is defined in ECMAScript
- edition 5 section 13 Function Definition. <a href="#refsECMA262">[ECMA262]</a></p>
+ edition 5 section 13 Function Definition. <i>Early error</i> is
+ defined in ECMAScript edition 5 section 16 Errors. <a href="#refsECMA262">[ECMA262]</a></p>
</li>
@@ -48339,15 +48429,6 @@
</li>
- <li>
-
- <p>If <var title="">strict</var> is true, and anything in <var title="">body</var> is a <code>SyntaxError</code> according to the
- Strict Mode Restrictions, then abort these steps.</p>
-
- <p class="note">The Strict Mode Restrictions are those listed in
- ECMAScript edition 5 section 13.1 Strict Mode Restrictions. <a href="#refsECMA262">[ECMA262]</a></p>
-
- </li>
<li>
@@ -64732,11 +64813,20 @@
<p>When the <i title="">progress</i> binding applies to a
<code><a href="#the-progress-element">progress</a></code> element, the element is expected to render as
an 'inline-block' box with a 'height' of '1em' and a 'width' of
- '10em', a 'vertical-align' of '-0.2em', and with its contents
- depicting a horizontal progress bar, with the start on the right and
- the end on the left if the 'direction' property on this element has
- a computed value of 'rtl', and with the start on the left and the
- end on the right otherwise.</p>
+ '10em', and a 'vertical-align' of '-0.2em'.</p>
+
+
+
+ <p> <img alt="" class="extra" src="http://dev.w3.org/html5/spec/images/sample-progress.png"/>
+ When the element is wider than it is tall, the element is
+ expected to be depicted as a horizontal progress bar, with the start
+ on the right and the end on the left if the 'direction' property on
+ this element has a computed value of 'rtl', and with the start on
+ the left and the end on the right otherwise. When the element is
+ taller than it is wide, it is expected to depicted as a vertical
+ progress bar, with the lowest value on the bottom. When the element
+ is square, it is expected to be depicted as a direction-independent
+ progress widget (e.g. a circular progress ring).</p>
<p>User agents are expected to use a presentation consistent with
platform conventions for progress bars. In particular, user agents
@@ -65460,7 +65550,6 @@
<dd><p>Use an explicit <code><a href="#the-form-element">form</a></code> and <a href="#text-state-and-search-state" title="attr-input-type-text">text field</a> combination instead.</p></dd>
<dt><dfn id="listing"><code>listing</code></dfn></dt>
- <dt><dfn id="xmp"><code>xmp</code></dfn></dt>
<dd><p>Use <code><a href="#the-pre-element">pre</a></code> and <code><a href="#the-code-element">code</a></code> instead.</p></dd>
<dt><dfn id="nextid"><code>nextid</code></dfn></dt>
@@ -65478,6 +65567,9 @@
<dt><dfn id="strike"><code>strike</code></dfn></dt>
<dd><p>Use <code><a href="#the-del-element">del</a></code> instead if the element is marking an edit, otherwise use <code><a href="#the-s-element">s</a></code> instead.</p></dd>
+ <dt><dfn id="xmp"><code>xmp</code></dfn></dt>
+ <dd><p>Use <code><a href="#the-code-element">code</a></code> instead, and escape "<code title=""><</code>" and "<code title="">&</code>" characters as "<code title="">&lt;</code>" and "<code title="">&amp;</code>" respectively.</p></dd>
+
<dt><dfn id="basefont"><code>basefont</code></dfn></dt>
<dt><dfn id="big"><code>big</code></dfn></dt>
<dt><dfn id="blink"><code>blink</code></dfn></dt>
@@ -66596,8 +66688,9 @@
<a href="#reflect">reflect</a> the element's <code title="attr-param-valuetype"><a href="#attr-param-valuetype">valuetype</a></code> content attribute.</p>
<hr/><p>User agents must treat <code><a href="#plaintext">plaintext</a></code> elements in a
- manner equivalent to <code><a href="#the-pre-element">pre</a></code> elements in terms of semantics and
- for purposes of rendering.</p>
+ manner equivalent to <code><a href="#the-pre-element">pre</a></code> elements in terms of semantics
+ and for purposes of rendering. (The parser has special behavior for
+ this element, though.)</p>
<hr/><pre class="idl">[Supplemental]
interface <a href="#htmlpreelement">HTMLPreElement</a> {
@@ -66763,7 +66856,8 @@
<hr/><p>User agents must treat <code><a href="#xmp">xmp</a></code> elements in a manner
equivalent to <code><a href="#the-pre-element">pre</a></code> elements in terms of semantics and
- for purposes of rendering.</p>
+ for purposes of rendering. (The parser has special behavior for this
+ element though.)</p>
<hr/><p>The <code><a href="#bgsound">bgsound</a></code>, <code><a href="#isindex-0">isindex</a></code>,
<code><a href="#multicol">multicol</a></code>, <code><a href="#nextid">nextid</a></code>, <code><a href="#rb">rb</a></code>, and
Index: common-dom-interfaces.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/common-dom-interfaces.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- common-dom-interfaces.html 5 May 2011 18:12:08 -0000 1.9
+++ common-dom-interfaces.html 6 May 2011 02:48:13 -0000 1.10
@@ -1069,12 +1069,12 @@
<li>Otherwise, <a href="common-microsyntaxes.html#split-a-string-on-spaces" title="split a string on spaces">split the
underlying string on spaces</a> to get the list of tokens in the
- object's underlying string.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</li>
<li>If the token indicated by <var title="">token</var> is a
<a href="infrastructure.html#case-sensitive">case-sensitive</a> match for one of the tokens in the
- object's underlying string then return true and stop this
- algorithm.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string then return
+ true and stop this algorithm.</li>
<li>Otherwise, return false.</li>
@@ -1091,7 +1091,7 @@
<li>Otherwise, <a href="common-microsyntaxes.html#split-a-string-on-spaces" title="split a string on spaces">split the
underlying string on spaces</a> to get the list of tokens in the
- object's underlying string.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</li>
<li>If the given <var title="">token</var> is a
<a href="infrastructure.html#case-sensitive">case-sensitive</a> match for one of the tokens in the
@@ -1134,7 +1134,7 @@
<li>Otherwise, <a href="common-microsyntaxes.html#split-a-string-on-spaces" title="split a string on spaces">split the
underlying string on spaces</a> to get the list of tokens in the
- object's underlying string.</li>
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</li>
<li>If the given <var title="">token</var> is a
<a href="infrastructure.html#case-sensitive">case-sensitive</a> match for one of the tokens in the
@@ -1151,9 +1151,8 @@
<li>Return true.</li>
- </ol><p>Objects implementing the <code><a href="#domtokenlist">DOMTokenList</a></code> interface must
- <dfn id="dom-tokenlist-tostring" title="dom-tokenlist-toString">stringify</dfn> to the object's
- underlying string representation.</p>
+ </ol><p>A <code><a href="#domtokenlist">DOMTokenList</a></code> object must <dfn id="dom-tokenlist-tostring" title="dom-tokenlist-toString">stringify</dfn> to the value of the
+ <code><a href="#domtokenlist">DOMTokenList</a></code> object's underlying string.</p>
</div><h4 id="domsettabletokenlist-0"><span class="secno">2.8.4 </span>DOMSettableTokenList</h4><p>The <code><a href="#domsettabletokenlist">DOMSettableTokenList</a></code> interface is the same as the
<code><a href="#domtokenlist">DOMTokenList</a></code> interface, except that it allows the
@@ -1285,7 +1284,7 @@
<li>
<p>If <var title="">input</var> is an Array object or an Object
- object, then, for each enumerable property in <var title="">input</var>, add a corresponding property to <var title="">output</var> having the same name, and having a value
+ object, then, for each enumerable property in <var title="">input</var>, add a new property to <var title="">output</var> having the same name, and having a value
created from invoking the <a href="#internal-structured-cloning-algorithm">internal structured cloning
algorithm</a> recursively with the value of the property as the
"<var title="">input</var>" argument and <var title="">memory</var> as the "<var title="">memory</var>"
@@ -1294,6 +1293,12 @@
<p class="note">This does not walk the prototype chain.</p>
+ <p class="note">Property descriptors, setters, getters, and
+ analogous features are not copied in this process. For example,
+ the property in the input could be marked as read-only, but in the
+ output it would just have the default state (typically read-write,
+ though that could depend on the scripting environment).</p>
+
</li>
<li><p>Return <var title="">output</var>.</p></li>
Index: fetching-resources.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/fetching-resources.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- fetching-resources.html 5 May 2011 18:12:08 -0000 1.9
+++ fetching-resources.html 6 May 2011 02:48:14 -0000 1.10
@@ -647,7 +647,7 @@
sequence of octets. <a href="references.html#refsMIMESNIFF">[MIMESNIFF]</a></p>
<p>The <dfn id="content-type-sniffing:-image" title="Content-Type sniffing: image">rules for sniffing
- images specifically</dfn> and the <dfn id="content-type-sniffing:-text-or-binary" title="Content-Type sniffing: text or binary">rules for distingushing if a resource is text or
+ images specifically</dfn> and the <dfn id="content-type-sniffing:-text-or-binary" title="Content-Type sniffing: text or binary">rules for distinguishing if a resource is text or
binary</dfn> are also defined in the Media Type Sniffing
specification. Both sets of rules return a <a href="infrastructure.html#mime-type">MIME type</a> as
their result. <a href="references.html#refsMIMESNIFF">[MIMESNIFF]</a></p>
Index: common-input-element-attributes.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/common-input-element-attributes.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- common-input-element-attributes.html 5 May 2011 18:12:08 -0000 1.9
+++ common-input-element-attributes.html 6 May 2011 02:48:14 -0000 1.10
@@ -1084,34 +1084,56 @@
<dl><dt><dfn id="dom-input-value-value" title="dom-input-value-value">value</dfn>
- </dt><dd>On getting, it must return the current <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> of the element. On setting,
- it must set the element's <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the new value, set the
- element's <a href="the-input-element.html#concept-input-value-dirty-flag" title="concept-input-value-dirty-flag">dirty value
- flag</a> to true, and then invoke the <a href="the-input-element.html#value-sanitization-algorithm">value sanitization
- algorithm</a>, if the element's <code title="attr-input-type"><a href="the-input-element.html#attr-input-type">type</a></code> attribute's current state
- defines one.</dd>
+ </dt><dd>
+
+ <p>On getting, it must return the current <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> of the element. On setting,
+ it must set the element's <a href="association-of-controls-and-forms.html#concept-fe-value" title="concept-fe-value">value</a> to the new value, set the
+ element's <a href="the-input-element.html#concept-input-value-dirty-flag" title="concept-input-value-dirty-flag">dirty value
+ flag</a> to true, and then invoke the <a href="the-input-element.html#value-sanitization-algorithm">value sanitization
+ algorithm</a>, if the element's <code title="attr-input-type"><a href="the-input-element.html#attr-input-type">type</a></code> attribute's current state
+ defines one.</p>
+
+ </dd>
<dt><dfn id="dom-input-value-default" title="dom-input-value-default">default</dfn>
- </dt><dd>On getting, if the element has a <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, it must return
- that attribute's value; otherwise, it must return the empty
- string. On setting, it must set the element's <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute to the new
- value.</dd>
+ </dt><dd>
+
+ <p>On getting, if the element has a <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, it must return
+ that attribute's value; otherwise, it must return the empty
+ string. On setting, it must set the element's <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute to the new
+ value.</p>
+
+ </dd>
<dt><dfn id="dom-input-value-default-on" title="dom-input-value-default-on">default/on</dfn>
- </dt><dd>On getting, if the element has a <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, it must return
- that attribute's value; otherwise, it must return the string "<code title="">on</code>". On setting, it must set the element's <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute to the new
- value.</dd>
+ </dt><dd>
+
+ <p>On getting, if the element has a <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute, it must return
+ that attribute's value; otherwise, it must return the string
+ "<code title="">on</code>". On setting, it must set the element's
+ <code title="attr-input-value"><a href="the-input-element.html#attr-input-value">value</a></code> attribute to the new
+ value.</p>
+
+ </dd>
<dt><dfn id="dom-input-value-filename" title="dom-input-value-filename">filename</dfn>
- </dt><dd>On getting, it must return the string "<code title="">C:\fakepath\</code>" followed by the filename of the first
- file in the list of <a href="number-state.html#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>, if
- any, or the empty string if the list is empty. On setting, if the
- new value is the empty string, it must empty the list of <a href="number-state.html#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>;
- otherwise, it must throw an <code><a href="common-dom-interfaces.html#invalid_state_err">INVALID_STATE_ERR</a></code>
- exception.</dd>
+ </dt><dd id="fakepath-orly">
+
+ <p>On getting, it must return the string "<code title="">C:\fakepath\</code>" followed by the filename of the
+ first file in the list of <a href="number-state.html#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>, if
+ any, or the empty string if the list is empty. On setting, if the
+ new value is the empty string, it must empty the list of <a href="number-state.html#concept-input-type-file-selected" title="concept-input-type-file-selected">selected files</a>;
+ otherwise, it must throw an <code><a href="common-dom-interfaces.html#invalid_state_err">INVALID_STATE_ERR</a></code>
+ exception.</p>
+
+ <p class="note">This "fakepath" requirement is a sad accident of
+ history. See <a href="number-state.html#fakepath-srsly">the example in the File
+ Upload state section</a> for more information.</p>
+
+ </dd>
</dl><hr/><p>The <dfn id="dom-input-checked" title="dom-input-checked"><code>checked</code></dfn> IDL
attribute allows scripts to manipulate the <a href="association-of-controls-and-forms.html#concept-fe-checked" title="concept-fe-checked">checkedness</a> of an
Index: rendering.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/rendering.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- rendering.html 5 May 2011 18:12:09 -0000 1.11
+++ rendering.html 6 May 2011 02:48:14 -0000 1.12
@@ -2830,11 +2830,20 @@
<p>When the <i title="">progress</i> binding applies to a
<code><a href="the-button-element.html#the-progress-element">progress</a></code> element, the element is expected to render as
an 'inline-block' box with a 'height' of '1em' and a 'width' of
- '10em', a 'vertical-align' of '-0.2em', and with its contents
- depicting a horizontal progress bar, with the start on the right and
- the end on the left if the 'direction' property on this element has
- a computed value of 'rtl', and with the start on the left and the
- end on the right otherwise.</p>
+ '10em', and a 'vertical-align' of '-0.2em'.</p>
+
+
+
+ <p> <img alt="" class="extra" src="http://dev.w3.org/html5/spec/images/sample-progress.png"/>
+ When the element is wider than it is tall, the element is
+ expected to be depicted as a horizontal progress bar, with the start
+ on the right and the end on the left if the 'direction' property on
+ this element has a computed value of 'rtl', and with the start on
+ the left and the end on the right otherwise. When the element is
+ taller than it is wide, it is expected to depicted as a vertical
+ progress bar, with the lowest value on the bottom. When the element
+ is square, it is expected to be depicted as a direction-independent
+ progress widget (e.g. a circular progress ring).</p>
<p>User agents are expected to use a presentation consistent with
platform conventions for progress bars. In particular, user agents
Index: association-of-controls-and-forms.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/association-of-controls-and-forms.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- association-of-controls-and-forms.html 5 May 2011 18:12:07 -0000 1.11
+++ association-of-controls-and-forms.html 6 May 2011 02:48:13 -0000 1.12
@@ -981,7 +981,9 @@
<dd> <p>When a control has no <a href="#concept-fe-value" title="concept-fe-value">value</a> but has a <code title="">required</code> attribute (<code><a href="the-input-element.html#the-input-element">input</a></code> <code title="attr-input-required"><a href="common-input-element-attributes.html#attr-input-required">required</a></code>, <code><a href="the-button-element.html#the-select-element">select</a></code>
<code title="attr-select-required"><a href="the-button-element.html#attr-select-required">required</a></code>,
- <code><a href="the-button-element.html#the-textarea-element">textarea</a></code> <code title="attr-textarea-required"><a href="the-button-element.html#attr-textarea-required">required</a></code>). </p></dd>
+ <code><a href="the-button-element.html#the-textarea-element">textarea</a></code> <code title="attr-textarea-required"><a href="the-button-element.html#attr-textarea-required">required</a></code>), or, in the case of
+ an element in a <i><a href="number-state.html#radio-button-group">radio button group</a></i>, any of the other
+ elements in the group has a <code title="attr-input-required"><a href="common-input-element-attributes.html#attr-input-required">required</a></code> attribute. </p></dd>
<dt> <dfn id="suffering-from-a-type-mismatch">Suffering from a type mismatch</dfn> </dt>
@@ -1557,7 +1559,7 @@
<dd>Let <var title="">MIME type</var> be the concatenation of
the string "<code title="">multipart/form-data;</code>", a
- U+0020 SPACE character, and the <a href="#multipart-form-data-boundary-string"><code title="">multipart/form-data</code> boundary string</a>
+ U+0020 SPACE character, the string "<code title="">boundary=</code>", and the <a href="#multipart-form-data-boundary-string"><code title="">multipart/form-data</code> boundary string</a>
generated by the <a href="#multipart-form-data-encoding-algorithm"><code title="">multipart/form-data</code> encoding
algorithm</a>.</dd>
Index: obsolete.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/obsolete.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- obsolete.html 5 May 2011 18:12:08 -0000 1.9
+++ obsolete.html 6 May 2011 02:48:14 -0000 1.10
@@ -435,7 +435,6 @@
<dd><p>Use an explicit <code><a href="forms.html#the-form-element">form</a></code> and <a href="states-of-the-type-attribute.html#text-state-and-search-state" title="attr-input-type-text">text field</a> combination instead.</p></dd>
<dt><dfn id="listing"><code>listing</code></dfn></dt>
- <dt><dfn id="xmp"><code>xmp</code></dfn></dt>
<dd><p>Use <code><a href="grouping-content.html#the-pre-element">pre</a></code> and <code><a href="text-level-semantics.html#the-code-element">code</a></code> instead.</p></dd>
<dt><dfn id="nextid"><code>nextid</code></dfn></dt>
@@ -453,6 +452,9 @@
<dt><dfn id="strike"><code>strike</code></dfn></dt>
<dd><p>Use <code><a href="edits.html#the-del-element">del</a></code> instead if the element is marking an edit, otherwise use <code><a href="text-level-semantics.html#the-s-element">s</a></code> instead.</p></dd>
+ <dt><dfn id="xmp"><code>xmp</code></dfn></dt>
+ <dd><p>Use <code><a href="text-level-semantics.html#the-code-element">code</a></code> instead, and escape "<code title=""><</code>" and "<code title="">&</code>" characters as "<code title="">&lt;</code>" and "<code title="">&amp;</code>" respectively.</p></dd>
+
<dt><dfn id="basefont"><code>basefont</code></dfn></dt>
<dt><dfn id="big"><code>big</code></dfn></dt>
<dt><dfn id="blink"><code>blink</code></dfn></dt>
@@ -1571,8 +1573,9 @@
<a href="common-dom-interfaces.html#reflect">reflect</a> the element's <code title="attr-param-valuetype"><a href="#attr-param-valuetype">valuetype</a></code> content attribute.</p>
<hr/><p>User agents must treat <code><a href="#plaintext">plaintext</a></code> elements in a
- manner equivalent to <code><a href="grouping-content.html#the-pre-element">pre</a></code> elements in terms of semantics and
- for purposes of rendering.</p>
+ manner equivalent to <code><a href="grouping-content.html#the-pre-element">pre</a></code> elements in terms of semantics
+ and for purposes of rendering. (The parser has special behavior for
+ this element, though.)</p>
<hr/><pre class="idl">[Supplemental]
interface <a href="grouping-content.html#htmlpreelement">HTMLPreElement</a> {
@@ -1738,7 +1741,8 @@
<hr/><p>User agents must treat <code><a href="#xmp">xmp</a></code> elements in a manner
equivalent to <code><a href="grouping-content.html#the-pre-element">pre</a></code> elements in terms of semantics and
- for purposes of rendering.</p>
+ for purposes of rendering. (The parser has special behavior for this
+ element though.)</p>
<hr/><p>The <code><a href="#bgsound">bgsound</a></code>, <code><a href="#isindex-0">isindex</a></code>,
<code><a href="#multicol">multicol</a></code>, <code><a href="#nextid">nextid</a></code>, <code><a href="#rb">rb</a></code>, and
Index: spec.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/spec.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -d -r1.11 -r1.12
--- spec.html 5 May 2011 18:12:09 -0000 1.11
+++ spec.html 6 May 2011 02:48:15 -0000 1.12
@@ -342,7 +342,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-5-may-2011">Editor's Draft 5 May 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-6-may-2011">Editor's Draft 6 May 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -365,7 +365,7 @@
<a href="Overview.html">single page HTML</a>,
<a href="spec.html">multipage HTML</a>,
<a href="author/">web developer edition</a>.
-This is revision 1.4886.
+This is revision 1.4903.
</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2010 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.org/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C
@@ -482,7 +482,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 5 May 2011 Editor's Draft.
+ This specification is the 6 May 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
Index: number-state.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/number-state.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- number-state.html 5 May 2011 18:12:08 -0000 1.9
+++ number-state.html 6 May 2011 02:48:14 -0000 1.10
@@ -886,11 +886,11 @@
false. The <a href="content-models.html#activation-behavior">activation behavior</a> is to <a href="webappapis.html#fire-a-simple-event">fire a
simple event</a> that bubbles named <code title="event-change">change</code> at the element. .</p>
- <p><strong>Constraint validation</strong>: If the element is <i title="concept-input-required"><a href="common-input-element-attributes.html#concept-input-required">required</a></i> and all of the
+ <p><strong>Constraint validation</strong>: If an element in the
+ <i><a href="#radio-button-group">radio button group</a></i> is <i title="concept-input-required"><a href="common-input-element-attributes.html#concept-input-required">required</a></i>, and all of the
<code><a href="the-input-element.html#the-input-element">input</a></code> elements in the <i><a href="#radio-button-group">radio button group</a></i> have a
- <a href="association-of-controls-and-forms.html#concept-fe-checked" title="concept-fe-checked">checkedness</a> that is
- false, then the element is <a href="association-of-controls-and-forms.html#suffering-from-being-missing">suffering from being
- missing</a>.</p>
+ <a href="association-of-controls-and-forms.html#concept-fe-checked" title="concept-fe-checked">checkedness</a> that is false,
+ then the element is <a href="association-of-controls-and-forms.html#suffering-from-being-missing">suffering from being missing</a>.</p>
</div><p class="note">If none of the radio buttons in a <a href="#radio-button-group">radio button
group</a> are checked when they are inserted into the document,
@@ -1016,7 +1016,7 @@
<p>User agents should prevent the user from selecting files that are
not accepted by one (or more) of these tokens.</p>
- </div><div class="example">
+ </div><div class="example" id="fakepath-srsly">
<p>For historical reasons, the <code title="dom-input-value"><a href="common-input-element-attributes.html#dom-input-value">value</a></code> IDL attribute prefixes the
filename with the string "<code title="">C:\fakepath\</code>". Some
Index: sections.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/sections.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- sections.html 5 May 2011 18:12:09 -0000 1.9
+++ sections.html 6 May 2011 02:48:15 -0000 1.10
@@ -1126,17 +1126,17 @@
for its nearest ancestor <a href="content-models.html#sectioning-content">sectioning content</a> or
<a href="#sectioning-root">sectioning root</a> element. A footer typically contains
information about its section such as who wrote it, links to related
- documents, copyright data, and the like.</p><p class="note">Contact information for the author or editor of a
- section belongs in an <code><a href="#the-address-element">address</a></code> element, possibly itself
- inside a <code><a href="#the-footer-element">footer</a></code>.</p><p>Footers don't necessarily have to appear at the <em>end</em> of a
- section, though they usually do.</p><p>When the <code><a href="#the-footer-element">footer</a></code> element contains entire sections,
+ documents, copyright data, and the like.</p><p>When the <code><a href="#the-footer-element">footer</a></code> element contains entire sections,
they <a href="rendering.html#represents" title="represents">represent</a> appendices, indexes,
long colophons, verbose license agreements, and other such
- content.</p><p class="note">The <code><a href="#the-footer-element">footer</a></code> element is not
- <a href="content-models.html#sectioning-content">sectioning content</a>; it doesn't introduce a new
- section.</p><p>When the nearest ancestor <a href="content-models.html#sectioning-content">sectioning content</a> or
+ content.</p><p class="note">Contact information for the author or editor of a
+ section belongs in an <code><a href="#the-address-element">address</a></code> element, possibly itself
+ inside a <code><a href="#the-footer-element">footer</a></code>.</p><p>Footers don't necessarily have to appear at the <em>end</em> of a
+ section, though they usually do.</p><p>When the nearest ancestor <a href="content-models.html#sectioning-content">sectioning content</a> or
<a href="#sectioning-root">sectioning root</a> element is <a href="dom.html#the-body-element-0">the body
- element</a>, then it applies to the whole page.</p><div class="example">
+ element</a>, then it applies to the whole page.</p><p class="note">The <code><a href="#the-footer-element">footer</a></code> element is not
+ <a href="content-models.html#sectioning-content">sectioning content</a>; it doesn't introduce a new
+ section.</p><div class="example">
<p>Here is a page with two footers, one at the top and one at the
bottom, with the same content:</p>
@@ -1197,6 +1197,45 @@
</BODY>
</HTML></pre>
+ </div><div class="example">
+
+ <p>Some site designs have what is sometimes referred to as "fat
+ footers" — footers that contain a lot of material, including
+ images, links to other articles, links to pages for sending
+ feedback, special offers... in some ways, a whole "front page" in
+ the footer.</p>
+
+ <p>This fragment shows the bottom of a page on a site with a "fat
+ footer":</p>
+
+ <pre>...
+ <footer>
+ <nav>
+ <section>
+ <h1>Articles</h1>
+ <p><img src="http://dev.w3.org/html5/spec/images/somersaults.jpeg" alt=""> Go to the gym with
+ our somersaults class! Our teacher Jim takes you through the paces
+ in this two-part article. <a href="articles/somersaults/1">Part
+ 1</a> · <a href="articles/somersaults/1">Part 2</a></p>
+ <p><img src="http://dev.w3.org/html5/spec/images/kindplus.jpeg"> Tired of walking on the edge of
+ a clif<!-- sic -->? Our guest writer Lara shows you how to bumble
+ your way through the bars. <a href="articles/kindplus/1">Read
+ more...</a></p>
+ <p><img src="http://dev.w3.org/html5/spec/images/crisps.jpeg"> The chips are down, now all
+ that's left is a potato. What can you do with it? <a
+ href="articles/crisps/1">Read more...</a></p>
+ </section>
+ <ul>
+ <li> <a href="/about">About us...</a>
+ <li> <a href="/feedback">Send feedback!</a>
+ <li> <a href="/sitemap">Sitemap</a>
+ </ul>
+ </nav>
+ <p><small>Copyright © 2015 The Snacker —
+ <a href="/tos">Terms of Service</a></small></p>
+ </footer>
+</body></pre>
+
</div><h4 id="the-address-element"><span class="secno">4.4.10 </span>The <dfn><code>address</code></dfn> element</h4><dl class="element"><dt>Categories</dt>
<dd><a href="content-models.html#flow-content">Flow content</a>.</dd>
<dd><a href="dnd.html#formatblock-candidate"><code title="">formatBlock</code> candidate</a>.</dd>
@@ -1490,8 +1529,8 @@
the first relevant step below for each element as you enter and
exit it.</p>
- <dl class="switch"><dt>If the top of the stack is an element, and you are exiting
- that element</dt>
+ <dl class="switch"><dt>If you are exiting an element and that element is the element
+ at the top of the stack</dt>
<dd>
@@ -1527,6 +1566,8 @@
<p>Let <var title="">current section</var> be a newly created
<a href="#concept-section" title="concept-section">section</a> for the <var title="">current outlinee</var> element.</p>
+ <p>Associate <var title="">current outlinee</var> with <var title="">current section</var>.</p>
+
<p>Let there be a new <a href="#outline">outline</a> for the new <var title="">current outlinee</var>, initialized with just the new
<var title="">current section</var> as the only <a href="#concept-section" title="concept-section">section</a> in the outline.</p>
@@ -1649,9 +1690,9 @@
<dd><p>Do nothing.</p></dd>
</dl><p id="associatedSection">In addition, whenever you exit a node,
- after doing the steps above, if <var title="">current
- section</var> is not null, associate the node with the <a href="#concept-section" title="concept-section">section</a> <var title="">current
- section</var>.</p>
+ after doing the steps above, if the node is not associated with a
+ <a href="#concept-section" title="concept-section">section</a> yet and <var title="">current section</var> is not null, associate the node
+ with the <a href="#concept-section" title="concept-section">section</a> <var title="">current section</var>.</p>
</li>
Index: introduction.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/introduction.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- introduction.html 5 May 2011 18:12:08 -0000 1.9
+++ introduction.html 6 May 2011 02:48:14 -0000 1.10
@@ -1029,10 +1029,10 @@
<div class="example">
<p>In the fragments below, for example, the semantics are
- nonsensical: a row cannot simultaneously be a cell, nor can a
- radio button be a progress bar.</p>
+ nonsensical: a separator cannot simultaneously be a cell, nor can
+ a radio button be a progress bar.</p>
- <pre class="bad"><tr role="cell"></pre>
+ <pre class="bad"><hr role="cell"></pre>
<pre class="bad"><input type=radio role=progressbar></pre>
</div>
Index: webappapis.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/webappapis.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- webappapis.html 5 May 2011 18:12:10 -0000 1.10
+++ webappapis.html 6 May 2011 02:48:15 -0000 1.11
@@ -1152,10 +1152,12 @@
<li>
<p>If <var title="">body</var> is not parsable as
- <i>FunctionBody</i> then abort these steps.</p>
+ <i>FunctionBody</i> or if parsing detects an <i>early error</i>
+ then abort these steps.</p>
<p class="note"><i>FunctionBody</i> is defined in ECMAScript
- edition 5 section 13 Function Definition. <a href="references.html#refsECMA262">[ECMA262]</a></p>
+ edition 5 section 13 Function Definition. <i>Early error</i> is
+ defined in ECMAScript edition 5 section 16 Errors. <a href="references.html#refsECMA262">[ECMA262]</a></p>
</li>
@@ -1169,15 +1171,6 @@
</li>
- <li>
-
- <p>If <var title="">strict</var> is true, and anything in <var title="">body</var> is a <code>SyntaxError</code> according to the
- Strict Mode Restrictions, then abort these steps.</p>
-
- <p class="note">The Strict Mode Restrictions are those listed in
- ECMAScript edition 5 section 13.1 Strict Mode Restrictions. <a href="references.html#refsECMA262">[ECMA262]</a></p>
-
- </li>
<li>
Index: common-microsyntaxes.html
===================================================================
RCS file: /sources/public/html5/markup/html5-spec/common-microsyntaxes.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- common-microsyntaxes.html 30 Apr 2011 11:35:44 -0000 1.8
+++ common-microsyntaxes.html 6 May 2011 02:48:14 -0000 1.9
@@ -656,6 +656,15 @@
<li>If <var title="">position</var> is past the end of <var title="">input</var>, return an error.</li>
+ </ol><p>Otherwise, if the character indicated by <var title="">position</var> (the first character) is a U+002B PLUS
+ SIGN character (+):</p>
+
+ <ol><li>Advance <var title="">position</var> to the next
+ character. (The "<code title="">+</code>" is ignored, but it is
+ not conforming.)</li>
+
+ <li>If <var title="">position</var> is past the end of <var title="">input</var>, return an error.</li>
+
</ol></li>
<li><p>If the character indicated by <var title="">position</var>
@@ -677,10 +686,16 @@
character.</p></li>
<li><p>If <var title="">position</var> is past the end of <var title="">input</var>, or if the character indicated by <var title="">position</var> is not one of U+0030 DIGIT ZERO (0) to
- U+0039 DIGIT NINE (9), then jump to the step labeled
+ U+0039 DIGIT NINE (9), U+0065 LATIN SMALL LETTER E (e), or U+0045
+ LATIN CAPITAL LETTER E (E), then jump to the step labeled
<i>conversion</i>.</p></li>
- <li><p><i>Fraction loop</i>: Multiply <var title="">divisor</var>
+ <li><p>If the character indicated by <var title="">position</var>
+ is a U+0065 LATIN SMALL LETTER E character (e) or a U+0045 LATIN
+ CAPITAL LETTER E character (E), skip the remainder of these
+ substeps.</p>
+
+ </li><li><p><i>Fraction loop</i>: Multiply <var title="">divisor</var>
by ten.</p></li>
<li>Add the value of the character indicated by <var title="">position</var>, interpreted as a base-ten digit (0..9)
Received on Friday, 6 May 2011 02:48:23 UTC