23116 2013-08-31 14:06:43 +0000 Form method attribute only accepts 'get' and 'post' 2013-09-03 17:25:23 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified All All CLOSED WONTFIX P3 normal --- 1 eldmannen dave.null cmhjones mike public-html-admin public-html-wg-issue-tracking robin synodinos public-html-bugzilla oldest_to_newest 92780 0 eldmannen 2013-08-31 14:06:43 +0000 As per chapter 4.10.19.5 Form submission The 'method' attribute of the 'form' element only accepst the values 'get' and 'post'. It does not support other valid and standard HTTP request methods such as PUT and DELETE which are useful when building RESTful web applications and services. 92815 1 synodinos 2013-09-02 11:38:10 +0000 These seem to have been dropped in 2010 [1] because of lack of use cases [2]. Do you have any use cases to suggest? [1] http://www.w3.org/TR/2010/WD-html5-diff-20101019/#changes-2010-06-24 [2] http://lists.w3.org/Archives/Public/public-html/2010Sep/0209.html 92822 2 eldmannen 2013-09-02 12:56:03 +0000 == Use case for DELETE == A page has a list of favorites/bookmarks. Next to each bookmark is a 'input' element of type 'submit'. When submitted, it submit a DELETE /Bookmark/123 request. The server removes the bookmark for that user from the database, and returns a page stating "Bookmark removed". <form action="/Bookmark/123" method="delete"> <input type="submit" value="Delete" /> </form> == Use case for PUT == User clicks on "Edit profile". User changes text, and presses the submit button. Server updates the user's profile with the new data and returns a confirmation. <form action="/Profile/" method="put"> <textarea name="profile" cols="80" rows="10"></textarea> <input type="submit" value="Update profile" /> </form> 92828 3 synodinos 2013-09-02 15:29:25 +0000 Isn't this covered by XHR Level 2 which all browsers support? (In reply to comment #2) > == Use case for DELETE == > A page has a list of favorites/bookmarks. > Next to each bookmark is a 'input' element of type 'submit'. > > When submitted, it submit a DELETE /Bookmark/123 request. > > The server removes the bookmark for that user from the database, and returns > a page stating "Bookmark removed". > > <form action="/Bookmark/123" method="delete"> > <input type="submit" value="Delete" /> > </form> > > > == Use case for PUT == > User clicks on "Edit profile". > User changes text, and presses the submit button. > Server updates the user's profile with the new data and returns a > confirmation. > > <form action="/Profile/" method="put"> > <textarea name="profile" cols="80" rows="10"></textarea> > <input type="submit" value="Update profile" /> > </form> 92830 4 eldmannen 2013-09-02 17:36:09 +0000 (In reply to comment #3) > Isn't this covered by XHR Level 2 which all browsers support? Oh, yes it is, according to § 4.7.1 http://www.w3.org/TR/XMLHttpRequest2/#the-open-method It supports CONNECT, DELETE, GET, HEAD, OPTIONS, POST, PUT, TRACE, and TRACK. I didn't think of this. Then it is possible to use XHR so it is less needed for forms. Although, it might be useful for forms too if the above use cases are rational and sane (they might not be?). 92852 5 robin 2013-09-03 11:18:18 +0000 (In reply to comment #4) > I didn't think of this. Then it is possible to use XHR so it is less needed > for forms. Although, it might be useful for forms too if the above use cases > are rational and sane (they might not be?). EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: none Rationale: It could indeed be interesting in theory, but in practice and as indicated in the message quoted in #1 it would require figuring out the interaction model and how to set some headers along the way. Without those, the addition isn't very useful. In fact, even with those the chances are pretty big that the default interaction won't be what developers want, and people will have to resort to XHR anyway. XHR works well for this, so the need is met. 92854 6 cmhjones 2013-09-03 11:44:53 +0000 There is an active change proposal for additional form methods, registered under issue 195 - see here for details: http://www.w3.org/html/wg/tracker/issues/195 For a completed extension specificaion see: http://cameronjones.github.io/form-http-extensions/index.html Please send feedback and/or comments to public-html or public-html-comments.