[Bug 23116] Form method attribute only accepts 'get' and 'post'

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23116

Robin Berjon <robin@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |robin@w3.org
         Resolution|---                         |WONTFIX

--- Comment #5 from Robin Berjon <robin@w3.org> ---
(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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 3 September 2013 11:18:20 UTC