[html5] r6051 - [e] (0) add a note to clarify interaction with rfc 2388 Fixing http://www.w3.org [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-05-03 12:23:00 -0700 (Tue, 03 May 2011)
New Revision: 6051

Modified:
   complete.html
   index
   source
Log:
[e] (0) add a note to clarify interaction with rfc 2388
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12065

Modified: complete.html
===================================================================
--- complete.html	2011-05-03 19:18:56 UTC (rev 6050)
+++ complete.html	2011-05-03 19:23:00 UTC (rev 6051)
@@ -51296,6 +51296,12 @@
     the <var title="">form data set</var>. Multiple entries with the
     same name must be treated as distinct fields.</p>
 
+    <p class=note>In particular, this means that multiple files
+    submitted as part of a single <code title=""><input type=file multiple></code> element
+    will result in each file having its own field; the "sets of files"
+    feature ("<code title="">multipart/mixed</code>") of RFC 2388 is
+    not used.</p>
+
     <p>The parts of the generated <code title="">multipart/form-data</code> resource that correspond to
     non-file fields must not have a <code><a href=#content-type>Content-Type</a></code> header
     specified. Their names and values must be encoded using the

Modified: index
===================================================================
--- index	2011-05-03 19:18:56 UTC (rev 6050)
+++ index	2011-05-03 19:23:00 UTC (rev 6051)
@@ -51324,6 +51324,12 @@
     the <var title="">form data set</var>. Multiple entries with the
     same name must be treated as distinct fields.</p>
 
+    <p class=note>In particular, this means that multiple files
+    submitted as part of a single <code title=""><input type=file multiple></code> element
+    will result in each file having its own field; the "sets of files"
+    feature ("<code title="">multipart/mixed</code>") of RFC 2388 is
+    not used.</p>
+
     <p>The parts of the generated <code title="">multipart/form-data</code> resource that correspond to
     non-file fields must not have a <code><a href=#content-type>Content-Type</a></code> header
     specified. Their names and values must be encoded using the

Modified: source
===================================================================
--- source	2011-05-03 19:18:56 UTC (rev 6050)
+++ source	2011-05-03 19:23:00 UTC (rev 6051)
@@ -57877,6 +57877,13 @@
     the <var title="">form data set</var>. Multiple entries with the
     same name must be treated as distinct fields.</p>
 
+    <p class="note">In particular, this means that multiple files
+    submitted as part of a single <code
+    title=""><input type=file multiple></code> element
+    will result in each file having its own field; the "sets of files"
+    feature ("<code title="">multipart/mixed</code>") of RFC 2388 is
+    not used.</p>
+
     <p>The parts of the generated <code
     title="">multipart/form-data</code> resource that correspond to
     non-file fields must not have a <code>Content-Type</code> header