Re: [whatwg] including in form submissions

2012-02-22 Thread Jukka K. Korpela
2012-02-22 20:38, Cameron Jones wrote: I'm referring to the "for" attribute on which ties its value to the elements which went into the calculation. This would otherwise have to be done using event attributes. I don't see how that is supposed to simplify things. It's supposed to designate de

Re: [whatwg] Review and Browser Vendor Interest in Form Enhancement

2012-02-22 Thread Jake Verbaten
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 wrot

Re: [whatwg] including in form submissions

2012-02-22 Thread Cameron Jones
On Wed, Feb 22, 2012 at 6:26 PM, Jukka K. Korpela wrote: > 2012-02-22 20:13, Cameron Jones wrote: > >> It [the element] > >> does provide a greater degree of integration with the browser though. > > Is this a requirement, or just assumed features of implementation? Which of > the assumed benefits

Re: [whatwg] including in form submissions

2012-02-22 Thread Jukka K. Korpela
2012-02-22 20:13, Cameron Jones wrote: It [the element] > does provide a greater degree of integration with the browser though. Is this a requirement, or just assumed features of implementation? Which of the assumed benefits could not be achieved by adding a new value for the type attribute

Re: [whatwg] including in form submissions

2012-02-22 Thread Cameron Jones
On Wed, Feb 22, 2012 at 6:01 PM, Jukka K. Korpela wrote: > 2012-02-22 19:30, Cameron Jones wrote: > >> Updating  as form submittable element is included in a >> proposal to enhance http request processing under a w3c issue > > > This sounds like a pointless attempt at enhancing a pointless element

Re: [whatwg] Review and Browser Vendor Interest in Form Enhancement

2012-02-22 Thread Cameron Jones
On Wed, Feb 22, 2012 at 5:38 PM, Adam Barth 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 > > I've responded to repeated requests on public-html and public-html-comments

Re: [whatwg] including in form submissions

2012-02-22 Thread Jukka K. Korpela
2012-02-22 19:30, Cameron Jones wrote: Updating as form submittable element is included in a proposal to enhance http request processing under a w3c issue This sounds like a pointless attempt at enhancing a pointless element. Instead of , authors can use, and have been able to use since rat

Re: [whatwg] Review and Browser Vendor Interest in Form Enhancement

2012-02-22 Thread Adam Barth
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 wrote: > Hi, > > I've submitted a proposal to w3c issue 195 which stems from requests > to p

[whatwg] Review and Browser Vendor Interest in Form Enhancement

2012-02-22 Thread Cameron Jones
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 declarati

Re: [whatwg] including in form submissions

2012-02-22 Thread Cameron Jones
On Tue, Feb 21, 2012 at 10:48 PM, Ian Hickson wrote: > On Tue, 13 Sep 2011, Michael Gratton wrote: >> >> HTML5 does not provide a means of submitting form content that is >> otherwise rendered as normal text, i.e. not as a form control. The use >> cases for this are the same as for the element, b

Re: [whatwg] Document's base URI should use the document's *current* address

2012-02-22 Thread Justin Lebar
> From an author's point of view, there's no such thing as the > document's original URI and, unless you're a nerd, you've never heard > of the base URI.  There's just the document's URI, modified by > pushState. > > From this point of view, I'd say it's less surprising that relative > URIs would b