New issue
Advanced search Search tips

Issue 487225 link

Starred by 5 users

Issue metadata

Status: WontFix
Closed: Oct 2015
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature

Sign in to add a comment

Form HTTP Extensions

Reported by, May 12 2015

Issue description

UserAgent: Mozilla/5.0 (X11; SunOS i86pc; rv:12.0) Gecko/20100101 Firefox/12.0

Example URL:

Steps to reproduce the problem:
The W3C Form HTTP Extensions specification is requested for implementation to enable the following features within HTML forms:

* Additional HTTP methods, eg: PUT, DELETE
* Configuration of HTTP headers
* Configuration of HTTP authentication login and logout


What is the expected behavior?

What went wrong?
Implementation of specification

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? No 

Chrome version:   Channel: n/a
OS Version: 
Flash Version:

Comment 1 by, May 12 2015

Re: additional HTTP methods, there has been considerable interest and conversation on this topic over on Stack Overflow:

The debate there might help jumpstart the conversation over here.
Labels: TE-NeedsFurtherTriage

Comment 3 by, Jul 13 2015

Labels: -Cr-Content Cr-Blink
Labels: -Cr-Blink Cr-Blink-Forms

Comment 5 by, Oct 26 2015

Labels: -Type-Bug Type-Feature
Status: WontFix
According to the specification, it's dead.

Comment 6 by, Oct 30 2015

The specification has been published as a W3C Note because the HTML Working Group's charter has expired and the W3C has chosen not to renew it. In these circumstances it is standard policy to publish specifications which have not reached Recommendation status as a Note:

The Form HTTP Extensions specification has been complete and published since May 2014. A specific call for implementation was sent out in February 2015 and received no responses from vendors:

The exit criteria for Recommendation status is for two independent and interoperable implementations of a specification. The only reason this specification has not achieved Recommendation status within the lifetime of the HTML WG is due to a lack of implementation from vendors. 

This same criteria of two implementations is used as the test for inclusion within both the W3C and WHATWG versions of HTML so, regardless of the W3C status of the extension specification, the functionality can be folded back into the mainline if chromium and another vendor choose to implement it.

The real question is - will chromium implement functionality to allow HTML methods PUT and DELETE to be declared within HTML forms?

Sign in to add a comment