151937 – [META] Implement fetch API

youenn fablet

Reported 2015-12-07 02:32:07 PST

Adding support for https://fetch.spec.whatwg.org/#fetch-api would be nice.

David Kilzer (:ddkilzer)

Comment 1 2016-02-02 21:02:00 PST

alex

Comment 2 2016-02-20 13:40:49 PST

I see this changeset from three weeks ago: http://trac.webkit.org/changeset/195954 but Nightly isn't yet exposing fetch on window. Is there a roadmap for this, or does it need to be enabled in some way to test it out? Thanks.

youenn fablet

Comment 3 2016-02-21 23:36:26 PST

(In reply to comment #2) > I see this changeset from three weeks ago: > > http://trac.webkit.org/changeset/195954 > > but Nightly isn't yet exposing fetch on window. Is there a roadmap for this, > or does it need to be enabled in some way to test it out? Thanks. Hi, Fetch is not yet implemented. Fetch API is not yet implemented. Request and Headers constructs are being exposed. The roadmap is to expose Response (very soon hopefully) Then will come the time of fetch, probably not supporting all options at the beginning.

youenn fablet

Comment 4 2016-08-24 06:14:57 PDT

(In reply to comment #2) > I see this changeset from three weeks ago: > > http://trac.webkit.org/changeset/195954 > > but Nightly isn't yet exposing fetch on window. Is there a roadmap for this, > or does it need to be enabled in some way to test it out? Thanks. It should now be exposed by default on Window and Worker since http://trac.webkit.org/changeset/204705.

guillaume.esquevin

Comment 5 2016-11-03 08:10:26 PDT

Now that fetch is exposed on window, how can I see the data that are received through a fetch response ? The corresponding pane is empty in the devtools, which is a real issue for me and forces me to launch Chrome to develop

youenn fablet

Comment 6 2016-11-03 08:28:15 PDT

(In reply to comment #5) > Now that fetch is exposed on window, how can I see the data that are > received through a fetch response ? Except than get it through JS API, you cannot atm. > The corresponding pane is empty in the devtools, which is a real issue for > me and forces me to launch Chrome to develop We have some bugzilla tracking specific bits (see bug 160286, bug 162384). Please let us know if you have some specific requirements/specific information you would like to see.