On 1/30/15 1:30 AM, nsm.nik...@gmail.com wrote:
Well my work on getting FormData on workers was because Fetch uses it, and
there doesn't seem to have been demand for it on workers before.
That's fair, but it seems like exposing it separately, if it's going to
be ready before the rest of
On Fri, Jan 30, 2015 at 7:13 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/30/15 1:30 AM, nsm.nik...@gmail.com wrote:
Well my work on getting FormData on workers was because Fetch uses it, and
there doesn't seem to have been demand for it on workers before.
That's fair, but it seems like
Summary: The FormData interface allows sending forms directly via XHR. It has
previously been exposed on window. This intent is to expose it on workers and
allow the same usage, i.e:
- Creating FormData objects and adding string values or blobs to them
- Sending FormData objects via a call to
On Fri, Jan 30, 2015 at 8:34 AM, Xidorn Quan quanxunz...@gmail.com wrote:
Personally, I don't think it needs to be hidden behind a pref. Given that
FormData has been exposed on window, and the usage is mostly identical, I
suggest it be shipped directly.
- Xidorn
On Fri, Jan 30, 2015 at
Personally, I don't think it needs to be hidden behind a pref. Given that
FormData has been exposed on window, and the usage is mostly identical, I
suggest it be shipped directly.
- Xidorn
On Fri, Jan 30, 2015 at 9:10 AM, nsm.nik...@gmail.com wrote:
Summary: The FormData interface allows
On Thursday, January 29, 2015 at 6:41:53 PM UTC-8, Boris Zbarsky wrote:
On 1/29/15 5:10 PM, nsm.nik...@gmail.com wrote:
Pref: I intend to hide this behind dom.fetch.enabled, which also controls
the Fetch specification.
May I ask why? This seems like a totally reasonable thing to expose
On 1/29/15 5:10 PM, nsm.nik...@gmail.com wrote:
Pref: I intend to hide this behind dom.fetch.enabled, which also controls the
Fetch specification.
May I ask why? This seems like a totally reasonable thing to expose
independently of Fetch, and might be good to have it in a release before
7 matches
Mail list logo