Bug 151937 - [META] Implement fetch API
Summary: [META] Implement fetch API
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on: 161190 161602 161654 171581 109199 112471 138968 152254 152384 153437 153787 153859 154536 154729 154820 154959 155111 155291 155359 155440 155637 155886 156753 156911 157837 158565 158728 158982 159056 159085 159115 159149 159221 159345 159404 159406 159413 159417 159507 159508 159554 159672 159676 159705 159714 159804 159808 159932 160028 160290 160292 160399 160404 160407 160444 160445 160452 160498 160546 160592 160593 160594 160595 161087 161130 161137 161147 161194 161228 161372 161382 161429 161431 161432 161434 161736 162281 162382 162559
Blocks: 160420 161902
  Show dependency treegraph
 
Reported: 2015-12-07 02:32 PST by youenn fablet
Modified: 2017-05-02 17:30 PDT (History)
12 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description youenn fablet 2015-12-07 02:32:07 PST
Adding support for https://fetch.spec.whatwg.org/#fetch-api would be nice.
Comment 1 David Kilzer (:ddkilzer) 2016-02-02 21:02:00 PST
<rdar://problem/22935125>
Comment 2 alex 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.
Comment 3 youenn fablet 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.
Comment 4 youenn fablet 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.
Comment 5 guillaume.esquevin 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
Comment 6 youenn fablet 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.