html5/spec forms.html,1.1041,1.1042 introduction.html,1.1044,1.1045 spec.html,1.1608,1.1609

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv7452

Modified Files:
	forms.html introduction.html spec.html 
Log Message:
This seems to be a common mistake, so let's call it out. (whatwg r6419)

[updated by splitter]


Index: forms.html
===================================================================
RCS file: /sources/public/html5/spec/forms.html,v
retrieving revision 1.1041
retrieving revision 1.1042
diff -u -d -r1.1041 -r1.1042
--- forms.html	10 Aug 2011 02:46:28 -0000	1.1041
+++ forms.html	11 Aug 2011 20:46:29 -0000	1.1042
@@ -722,8 +722,8 @@
 
   readonly attribute <a href="common-dom-interfaces.html#htmlformcontrolscollection">HTMLFormControlsCollection</a> <a href="#dom-form-elements" title="dom-form-elements">elements</a>;
   readonly attribute long <a href="#dom-form-length" title="dom-form-length">length</a>;
-  caller <a href="#dom-form-item" title="dom-form-item">getter</a> any (in unsigned long index);
-  caller <a href="#dom-form-nameditem" title="dom-form-namedItem">getter</a> any (in DOMString name);
+  caller <a href="#dom-form-item" title="dom-form-item">getter</a> <a href="infrastructure.html#element">Element</a> (in unsigned long index);
+  caller <a href="#dom-form-nameditem" title="dom-form-namedItem">getter</a> object (in DOMString name);
 
   void <a href="#dom-form-submit" title="dom-form-submit">submit</a>();
   void <a href="#dom-form-reset" title="dom-form-reset">reset</a>();

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1608
retrieving revision 1.1609
diff -u -d -r1.1608 -r1.1609
--- spec.html	11 Aug 2011 18:46:27 -0000	1.1608
+++ spec.html	11 Aug 2011 20:46:30 -0000	1.1609
@@ -349,7 +349,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.5122.
+This is revision 1.5124.
    </p> 
      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2011 <a href="http://www.w3.org/"><abbr title="World Wide

Index: introduction.html
===================================================================
RCS file: /sources/public/html5/spec/introduction.html,v
retrieving revision 1.1044
retrieving revision 1.1045
diff -u -d -r1.1044 -r1.1045
--- introduction.html	11 Aug 2011 06:46:23 -0000	1.1044
+++ introduction.html	11 Aug 2011 20:46:30 -0000	1.1045
@@ -559,7 +559,39 @@
   First, it should be read cover-to-cover, multiple times. Then, it
   should be read backwards at least once. Then it should be read by
   picking random sections from the contents list and following all the
-  cross-references.</p><h4 id="typographic-conventions"><span class="secno">1.7.2 </span>Typographic conventions</h4><p>This is a definition, requirement, or explanation.</p><p class="note">This is a note.</p><p class="example">This is an example.</p><p class="XXX">This is an open issue.</p><p class="warning">This is a warning.</p><pre class="idl extract">interface <dfn title="">Example</dfn> {
+  cross-references.</p><p>As described in the conformance requirements section below, this
+  specification describes conformance criteria for a variety of
+  conformance classes. In particular, there are conformance
+  requirements that apply to <em>producers</em>, for example authors
+  and the documents they create, and there are conformance
+  requirements that apply to <em>consumers</em>, for example Web
+  browsers. They can be distinguished by what they are requiring: a
+  requirement on a producer states what is allowed, while a
+  requirement on a consumer states how software is to act.</p><div class="example">
+
+   <p>For example, "the <code title="">foo</code> attribute's value
+   must be a <a href="common-microsyntaxes.html#valid-integer">valid integer</a>" is a requirement on
+   producers, as it lays out the allowed values; in contrast, the
+   requirement "the <code title="">foo</code> attribute's value must
+   be parsed using the <a href="common-microsyntaxes.html#rules-for-parsing-integers">rules for parsing integers</a>" is a
+   requirement on consumers, as it describes how to process the
+   content.</p>
+
+  </div><p><strong>Requirements on producers have no bearing whatsoever on
+  consumers.</strong></p><div class="example">
+
+   <p>Continuing the above example, a requirement stating that a
+   particular attribute's value is constrained to being a <a href="common-microsyntaxes.html#valid-integer">valid
+   integer</a> emphatically does <em>not</em> imply anything about
+   the requirements on consumers. It might be that the consumers are
+   in fact required to treat the attribute as an opaque string,
+   completely unaffected by whether the value conforms to the
+   requirements or not. It might be (as in the previous example) that
+   the consumers are required to parse the value using specific rules
+   that define how invalid (non-numeric in this case) values are to be
+   processed.</p>
+
+  </div><h4 id="typographic-conventions"><span class="secno">1.7.2 </span>Typographic conventions</h4><p>This is a definition, requirement, or explanation.</p><p class="note">This is a note.</p><p class="example">This is an example.</p><p class="XXX">This is an open issue.</p><p class="warning">This is a warning.</p><pre class="idl extract">interface <dfn title="">Example</dfn> {
   // this is an IDL definition
 };</pre><dl class="domintro"><dt><var title="">variable</var> = <var title="">object</var> . <code title="">method</code>( [ <var title="">optionalArgument</var> ] )</dt>

Received on Thursday, 11 August 2011 20:46:38 UTC