spec/Overview.html 1.1343 2170 WF2: Various tweaks, mostly editorial. (

WF2: Various tweaks, mostly editorial. (whatwg r2170)

Fragment identifiers: If the absolute URL of the new resource is the same as the address of the active document of the browsing context being navigated, ignoring any <fragment> components of those URLs, and the new resource is to be fetched using HTTP GET or equivalent, then navigate to that fragment identifier and abort these steps.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#navigate-fragid-step
application/x-www-form-urlencoded encoding algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#applicationx-www-form-urlencoded
4.9.16.1. URL-encoded form data
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#url-encoded
multipart/form-data encoding algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#multipartform-data
text/plain encoding algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#textplain
appropriate form encoding algorithm
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#appropriate
Constructing the form data set. For each element field in controls, in tree order, run the following substeps: If any of the following conditions are met, then skip these substeps for this element: The field element has a datalist element ancestor. The field element is disabled. The field element is a button but it is not submitter. The field element is an input element whose type attribute is in the Checkbox state and the control is not checked. The field element is an input element whose type attribute is in the Radio Button state and the control is not checked. The field element is an input element whose type attribute is in the File Upload state but the control does not have any files selected. Otherwise, process field as follows: If the field element is an input element whose type attribute is in the Image Button state, then run these further nested substeps: If the field element has an name attribute specified and value is not the empty string, let name be that value followed by a single U+002E FULL SOP (.) character. Otherwise, let name be the empty string. Let namex be the string consisting of the concatenation of name and a single U+0078 LATIN SMALL LETTER X (x) character. Let namey be the string consisting of the concatenation of name and a single U+0079 LATIN SMALL LETTER Y (y) character. The field element is submitter, and before this algorithm was invoked the user indicated a coordinate. Let x be the x-component of the coordindate selected by the user, and let y be the y-component of the coordinate selected by the user. Append an entry in the form data set with the name namex and the value x. Append an entry in the form data set with the name namey and the value y. Skip the remaining substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the next step in the overall form submission algorithm. If the field element does not have a name attribute specified, or its name attribute's value is the empty strig, skip these substeps for this element: if there are any more elements in controls, return to the top of the constructing the form data set step, otherwise, jump to the next step in the overall form submission algorithm. Let name be the value of the field element's name attribute. If the field element is a select element, then for each option element in the select element that is selected, append an entry in the form data set with the name as the name and the value of the option element as the value. Otherwise, if the field element is an input element whose type attribute is in the File Upload state, then for each file selected in the input element, append an entry in the form data set with the name as the name and the file as the value. (Both the file name and the file contents are subsequently used.) Otherwise, append an entry in the form data set with name as the name and the value of the field element as the value.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#constructing-form-data-set
4.9.16.2. Multipart form data
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#multipart
4.9.16.3. Plain text form data
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1343.html#plain

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1342&r2=1.1343&f=h
http://html5.org/tools/web-apps-tracker?from=2169&to=2170

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1342
retrieving revision 1.1343
diff -u -d -r1.1342 -r1.1343
--- Overview.html 12 Sep 2008 09:10:14 -0000 1.1342
+++ Overview.html 12 Sep 2008 09:54:58 -0000 1.1343
@@ -1078,6 +1078,16 @@
 
        <li><a href="#form-submission"><span class=secno>4.9.16 </span>Form
         submission</a>
+        <ul class=toc>
+         <li><a href="#url-encoded"><span class=secno>4.9.16.1.
+          </span>URL-encoded form data</a>
+
+         <li><a href="#multipart"><span class=secno>4.9.16.2.
+          </span>Multipart form data</a>
+
+         <li><a href="#plain"><span class=secno>4.9.16.3. </span>Plain text
+          form data</a>
+        </ul>
       </ul>
 
      <li><a href="#scripting1"><span class=secno>4.10 </span>Scripting</a>
@@ -27713,13 +27723,13 @@
       <tr>
        <td>
 
-       <th> GET
+       <th> <span title=attr-fs-method-GET>GET</span>
 
-       <th> POST
+       <th> <span title=attr-fs-method-POST>POST</span>
 
-       <th> PUT
+       <th> <span title=attr-fs-method-PUT>PUT</span>
 
-       <th> DELETE
+       <th> <span title=attr-fs-method-DELETE>DELETE</span>
 
       <tr>
        <th> <code title="">http</code>
@@ -28051,11 +28061,10 @@
      <dd>Use the <a href="#textplain"><code title="">text/plain</code>
       encoding algorithm</a>.
     </dl>
-
-   <li>
-    <p class=big-issue>...
   </ol>
 
+  <h5 id=url-encoded><span class=secno>4.9.16.1. </span>URL-encoded form data</h5>
+
   <p>The <dfn id=applicationx-www-form-urlencoded><code
    title="">application/x-www-form-urlencoded</code> encoding algorithm</dfn>
    is as follows:
@@ -28069,6 +28078,8 @@
    encoding. -->
   </ol>
 
+  <h5 id=multipart><span class=secno>4.9.16.2. </span>Multipart form data</h5>
+
   <p>The <dfn id=multipartform-data><code title="">multipart/form-data</code>
    encoding algorithm</dfn> is as follows:
 
@@ -28081,6 +28092,8 @@
    encoding. -->
   </ol>
 
+  <h5 id=plain><span class=secno>4.9.16.3. </span>Plain text form data</h5>
+
   <p>The <dfn id=textplain><code title="">text/plain</code> encoding
    algorithm</dfn> is as follows:
 
@@ -38481,6 +38494,7 @@
       <li>Network errors
      </ul>
     </div>
+    <!-- XXX should we define 205 processing here? e.g. reset all forms? -->
 
    <li>
     <p>Let <var title="">type</var> be <a href="#sniffed" title="Content-Type

Received on Friday, 12 September 2008 09:58:40 UTC