spec/Overview.html 1.1595 2423 Define how <object> fits into form submi

Define how <object> fits into form submission. (whatwg r2423)

If the sandboxed plugins browsing context flag is set on the browsing context for which the object element's document is the active document, then the steps above must always act as if they had failed to find a plugin, even if one would otherwise have been used.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1595.html#sandboxPluginObject
Submittable elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1595.html#category-submit
4.8.5 The object element
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1595.html#the-object-element
src
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1595.html#dom-embed-src
data
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1595.html#dom-object-data
Resettable elements
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1595.html#category-reset
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 whose checkedness is false. The field element is an input element whose type attribute is in the Radio Button state and whose checkedness is false. 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. The field element is an object element that is not using a plugin. Otherwise, process field as follows: Let type be the value of the type DOM attribute of field. 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 elementhas an name attribute specified and value is not the empty string, let name be that value followed by a single U+002E FULL STOP (.) 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, the value x, and the type type. Append an entry in the form data set with the name namey and the value y, and the type type. 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 net 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 string, 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 whose selectedness is true, append an entry in the form data set with the name as the name, the value of the option element as the value, and type as the type. Otherwise, if the field element is an input element whose type attribute is in the Checkbox state or the Radio Button state, then then run these further nested substeps: If the field element has a value attribute specified, then let value be the value of that attribute; otherwise, let value be the string "on". Append an entr in the form data set with name as the name, value as the value, and type as the type. 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, the file (consisting of the name, the type, and the body) as the value, and type as the type. Otherwise, if the field element is an object element: try to obtain a form submission value from the plugin, and if that is successful, append an entry in the form data set with name as the name, the returned form submission value as the value, and the string "object" as the type. Otherwise, append an entry in the form data set with name as the name, the value of the field element as the value, and type as the type.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1595.html#constructing-form-data-set

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1594&r2=1.1595&f=h
http://html5.org/tools/web-apps-tracker?from=2422&to=2423

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1594
retrieving revision 1.1595
diff -u -d -r1.1594 -r1.1595
--- Overview.html 20 Nov 2008 02:03:33 -0000 1.1594
+++ Overview.html 20 Nov 2008 02:52:49 -0000 1.1595
@@ -12989,7 +12989,7 @@
   <a href=#reflect>reflect</a> the respective content attributes of the same
   name.<h4 id=the-object-element><span class=secno>4.8.5 </span>The <dfn><code>object</code></dfn> element</h4><dl class=element><dt>Categories</dt>
    <dd><a href=#embedded-content-1>Embedded content</a>.</dd>
-   <dd><a href=#form-associated-element>Form-associated element</a>.</dd>
+   <dd><a href=#category-listed title=category-listed>Listed</a>,  <a href=#category-submit title=category-submit>submittable</a>, <a href=#form-associated-element>form-associated element</a>.</dd>
    <dt>Contexts in which this element may be used:</dt>
    <dd>Where <a href=#embedded-content-1>embedded content</a> is expected.</dd>
    <dt>Content model:</dt>
@@ -13293,7 +13293,9 @@
   map</a>. The attribute must be ignored if the <code><a href=#the-object-element>object</a></code>
   element doesn't represent an image.<p>The <code title=attr-fae-form><a href=#attr-fae-form>form</a></code> attribute is used to
   explicitly associate the <code><a href=#the-object-element>object</a></code> element with its
-  <a href=#form-owner>form owner</a>.<p>The <code><a href=#the-object-element>object</a></code> element supports <a href=#dimension-attributes>dimension
+  <a href=#form-owner>form owner</a>.<p><strong>Constraint validation:</strong> <code><a href=#the-object-element>object</a></code>
+  elements are always <a href=#barred-from-constraint-validation>barred from constraint
+  validation</a>.<p>The <code><a href=#the-object-element>object</a></code> element supports <a href=#dimension-attributes>dimension
   attributes</a>.<p>The DOM attributes <dfn id=dom-object-data title=dom-object-data><code>data</code></dfn>, <dfn id=dom-object-type title=dom-object-type><code>type</code></dfn>, <dfn id=dom-object-name title=dom-object-name><code>name</code></dfn>, and <dfn id=dom-object-usemap title=dom-object-useMap><code>useMap</code></dfn> each must
   <a href=#reflect>reflect</a> the respective content attributes of the same
   name.<div class=example>
@@ -18680,7 +18682,7 @@
   elements</a> fall into several subcategories:<dl><dt><dfn id=category-submit title=category-submit>Submittable elements</dfn></dt>
 
    <dd>Denotes elements that can be used for <a href=#constructing-form-data-set>constructing the form data
-   set</a> when a <code><a href=#the-form-element>form</a></code> element is <a href=#concept-form-submit title=concept-form-submit>submit</a>.</dd>
+   set</a> when a <code><a href=#the-form-element>form</a></code> element is <a href=#concept-form-submit title=concept-form-submit>submitted</a>.</dd>
 
    <dt><dfn id=category-reset title=category-reset>Resettable elements</dfn></dt>
 
@@ -22841,11 +22843,16 @@
        <code><a href=#the-input-element>input</a></code> element whose <code title=attr-input-type><a href=#attr-input-type>type</a></code> attribute is in the <a href=#file-upload-state title=attr-input-type-file>File Upload</a> state but
        the control does not have any files selected.</li>
 
+       <li>The <var title="">field</var> element is an
+       <code><a href=#the-object-element>object</a></code> element that is not using a
+       <a href=#plugin>plugin</a>.</li>
+
       </ul><p>Otherwise, process <var title="">field</var> as follows:</p>
 
      </li>
 
-     <li><p>Let <var title="">type</var> be the value of the <code title="">type</code> DOM attribute of <var title="">field</var>.</li>
+     <li><p>Let <var title="">type</var> be the value of the <code title="">type</code> DOM attribute of <var title="">field</var>.</li> <!-- if the field is an <object>
+     element, this will get ignored. -->
 
      <li>
 
@@ -22933,6 +22940,14 @@
      body) as the value, and <var title="">type</var> as the
      type.</li>
 
+     <li><p>Otherwise, if the <var title="">field</var> element is an
+     <code><a href=#the-object-element>object</a></code> element: try to obtain a form submission
+     value from the <a href=#plugin>plugin</a><!-- using NPAPI's
+     NPP_GetValue() entry point with the NPPVformValue variable -->,
+     and if that is successful, append an entry in the <var title="">form data set</var> with <var title="">name</var> as the
+     name, the returned form submission value as the value, and the
+     string "<code title="">object</code>" as the type.</li>
+
      <li><p>Otherwise, append an entry in the <var title="">form data
      set</var> with <var title="">name</var> as the name, the <a href=#concept-fe-value title=concept-fe-value>value</a> of the <var title="">field</var> element as the value, and <var title="">type</var> as the type.</li>

Received on Thursday, 20 November 2008 02:56:16 UTC