Re: ISSUE-195: form-http-req - Chairs Solicit Alternate Proposals or Counter-Proposals

On Thu, Mar 22, 2012 at 10:45 AM, Cameron Jones <cmhjones@gmail.com> wrote:
> On Wed, Mar 21, 2012 at 10:47 PM, Edward O'Connor <eoconnor@apple.com> wrote:
>> Hi,
>>
>> Maciej wrote, on behalf of the chairs:
>>
>>> 'Enhance http request generation from forms'
>>> The current status for this issue:
>>>
>>> http://www.w3.org/html/wg/tracker/issues/195
>>> http://dev.w3.org/html5/status/issue-status.html#ISSUE-195
>>>
>>> So far, we have one Change Proposal submitted:
>>>
>>> http://www.w3.org/wiki/User:Cjones/ISSUE-195
>>>
>>> At this time the Chairs would also like to solicit additional Change
>>> Proposals (possibly with "zero edits" as the Proposal Details), in case
>>> anyone would like to advocate the status quo or a different change than
>>> the specific one in the existing Change Proposals.
>>
>> Please consider this zero edit Change Proposal for ISSUE-195:
>>
>>         http://www.w3.org/html/wg/wiki/User:Eoconnor/ISSUE-195
>>
>>
>> Thanks,
>> Ted
>>
>
> Hi Ted,
>
> Your counter proposal references some aspects of my initial proposal
> which are due to be updated based on accepted feedback. This is
> specifically around the accepted methods which will be updated to
> remove support for CONNECT and allow any other method name effectively
> changing the specification of methods to a blacklist from a whitelist.
>
> I can address your other points subsequently, but will proceed to
> update my proposal with the resolution from feedback whereby you might
> want to amend your proposal given its new state.
>
> Will notify via the list when i've completed the changes.
>
> Thanks,
> Cameron Jones

I've updated the proposal with the following changes:

1. Form method accepts any value excluding the following blacklist:
CONNECT, TRACE, TRACK
2. Replaced "_none" payload attribute state with the extension of the
"disabled" attribute to <output> and <object> for obtaining the same
functionality and limiting the ability to restrict form submission
elements to this single flag.
3. Replaced "_async_" form control field with a form submission
attribute on <form>, <input> and <button> allowing for initiation of
a/sync requests defined by the submission element.

Thanks,
Cameron Jones

Received on Thursday, 22 March 2012 16:24:31 UTC