[prev in list] [next in list] [prev in thread] [next in thread] 

List:       whatwg
Subject:    Re: [whatwg] Review and Browser Vendor Interest in Form Enhancement
From:       Jake Verbaten <raynos2 () gmail ! com>
Date:       2012-02-22 19:45:35
Message-ID: CAMCMjp3i7VXhsCmJObEfahyjZgj6uSfKtrd6K-OevJOeNk1eGg () mail ! gmail ! com
[Download RAW message or body]

Personally as a web developer this a feature of forms that I've missed when
I'm building my REST apis and then have to put in some kind of hidden input
for method overwrite.

I know of other developers that also agree that this is a wanted feature.

On Wed, Feb 22, 2012 at 5:38 PM, Adam Barth <w3c@adambarth.com> wrote:

> Last time I asked around, there didn't seem to be much demand for
> these features so I didn't implement the previous version that was in
> the HTML spec.
>
> Adam
>
>
> On Wed, Feb 22, 2012 at 9:33 AM, Cameron Jones <cmhjones@gmail.com> wrote:
> > Hi,
> >
> > I've submitted a proposal to w3c issue 195 which stems from requests
> > to provide support for additional HTTP methods on forms with specific
> > reference to clients without scripting support. The proposal is based
> > on extending the functionality of forms by exposing the abilities of
> > XHR to declarative markup.
> >
> > I'm keen to highlight the issue to solicit review and feedback on the
> > proposal, and to harvest some degree of the level of interest from
> > browser vendors as to the desirability of implementing the proposal.
> >
> > The proposal itself includes the rationale and details pertaining to
> > the changes. There has been some initial feedback on public-html
> > however i am yet to update the proposal with the recommendations.
> > These amount to:
> >
> > * Implement method attribute values as a blacklist instead of a whitelist
> > * Exclude CONNECT and TRACK methods in addition to TRACE as
> > blacklisted items for synchronicity with XHR specification
> > * Remove "_none" payload attribute state and replace functionality
> > with "disabled" attribute and state
> > * Look at replacing "_async_" form control field as a form submit
> > element attribute for form, button & input retargeting.
> >
> > Proposal:
> > http://www.w3.org/wiki/User:Cjones/ISSUE-195
> >
> > Issue 195:
> > http://www.w3.org/html/wg/tracker/issues/195
> >
> > Thanks,
> > Cameron Jones
>
[prev in list] [next in list] [prev in thread] [next in thread]