Bug 151937
Summary: | [META] Implement fetch API | ||
---|---|---|---|
Product: | WebKit | Reporter: | youenn fablet <youennf> |
Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | alex, ap, calvaris, ddkilzer, edithmartinn, guillaume.esquevin, lzsoft.cja, ray, sam, tri, twarlick, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | 161602, 161654, 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, 161190, 161194, 161228, 161372, 161382, 161429, 161431, 161432, 161434, 161736, 162281, 162382, 162559, 171581, 232371, 246526 | ||
Bug Blocks: | 160420, 161902 |
youenn fablet
Adding support for https://fetch.spec.whatwg.org/#fetch-api would be nice.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
David Kilzer (:ddkilzer)
<rdar://problem/22935125>
alex
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
(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
(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
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
(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.