- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 06 May 2011 00:47:41 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv22523
Modified Files:
association-of-controls-and-forms.html number-state.html
scripting-1.html sections.html spec.html
Log Message:
correct example (whatwg r6095)
[updated by splitter]
Index: scripting-1.html
===================================================================
RCS file: /sources/public/html5/spec/scripting-1.html,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -d -r1.51 -r1.52
--- scripting-1.html 3 May 2011 20:47:31 -0000 1.51
+++ scripting-1.html 6 May 2011 00:47:21 -0000 1.52
@@ -1153,12 +1153,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: association-of-controls-and-forms.html
===================================================================
RCS file: /sources/public/html5/spec/association-of-controls-and-forms.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -d -r1.78 -r1.79
--- association-of-controls-and-forms.html 4 May 2011 23:46:54 -0000 1.78
+++ association-of-controls-and-forms.html 6 May 2011 00:47:13 -0000 1.79
@@ -992,7 +992,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>
@@ -1569,7 +1571,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: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1477
retrieving revision 1.1478
diff -u -d -r1.1477 -r1.1478
--- spec.html 5 May 2011 23:46:54 -0000 1.1477
+++ spec.html 6 May 2011 00:47:29 -0000 1.1478
@@ -344,7 +344,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>
@@ -367,7 +367,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.4893.
+This is revision 1.4899.
</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
@@ -487,7 +487,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/spec/number-state.html,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- number-state.html 5 May 2011 19:47:06 -0000 1.44
+++ number-state.html 6 May 2011 00:47:13 -0000 1.45
@@ -897,11 +897,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,
Index: sections.html
===================================================================
RCS file: /sources/public/html5/spec/sections.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- sections.html 4 May 2011 20:47:31 -0000 1.40
+++ sections.html 6 May 2011 00:47:21 -0000 1.41
@@ -1133,17 +1133,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>
@@ -1204,6 +1204,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>
@@ -1498,8 +1537,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>
@@ -1535,6 +1574,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>
@@ -1657,9 +1698,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>
Received on Friday, 6 May 2011 00:47:46 UTC