Skip to content

Commit

Permalink
[e] (0) add missing feature note
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.whatwg.org/webapps@2635 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jan 6, 2009
1 parent 9fd7b9c commit d74018d
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 1 deletion.
9 changes: 8 additions & 1 deletion index
Expand Up @@ -21,7 +21,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
<h2 class="no-num no-toc" id=draft-recommendation-&mdash;-date:-01-jan-1901>Draft Recommendation &mdash; 1 January 2009</h2>
<h2 class="no-num no-toc" id=draft-recommendation-&mdash;-date:-01-jan-1901>Draft Recommendation &mdash; 6 January 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<dl><dt>Multiple-page version:</dt>
Expand Down Expand Up @@ -55623,6 +55623,13 @@ TODO (or delay):
and "base-sixteen", the order that 0-9 A-Z a-z is mentioned,
and the detail to which the spec explains how to interpret a
string as a hexadecimal number.
XXX * expose the form data set, either as an object (on which one can
invoke the JSON serialiser), or in the form of a method on
HTMLFormElement that returns the form data set serialised
according to a particular encoding (defaulting to the form's
enctype="" one, probably). This would allow forms to be used
with XHR-like systems without having to manually construct the
form data set the way that is done today.
-->


7 changes: 7 additions & 0 deletions source
Expand Up @@ -60755,6 +60755,13 @@ TODO (or delay):
and "base-sixteen", the order that 0-9 A-Z a-z is mentioned,
and the detail to which the spec explains how to interpret a
string as a hexadecimal number.
XXX * expose the form data set, either as an object (on which one can
invoke the JSON serialiser), or in the form of a method on
HTMLFormElement that returns the form data set serialised
according to a particular encoding (defaulting to the form's
enctype="" one, probably). This would allow forms to be used
with XHR-like systems without having to manually construct the
form data set the way that is done today.
-->

</body>
Expand Down

0 comments on commit d74018d

Please sign in to comment.