RESOLVED FIXED 160452
[Fetch API] Activate fetch api runtime flag by default 
https://bugs.webkit.org/show_bug.cgi?id=160452
Summary [Fetch API] Activate fetch api runtime flag by default
youenn fablet
Reported 2016-08-02 08:47:29 PDT
It may be time to activate fetch API runtime flag by default.
Attachments
Patch (3.05 KB, patch)
2016-08-02 08:48 PDT, youenn fablet 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2016-08-02 08:48:52 PDT
Created attachment 285112 [details] Patch
Alex Christensen
Comment 2 2016-08-02 08:54:05 PDT
almost. Let's land a few of your other patches first.
Alex Christensen
Comment 3 2016-08-05 09:14:04 PDT
Comment on attachment 285112 [details] Patch let's do this
WebKit Commit Bot
Comment 4 2016-08-22 02:55:32 PDT
Comment on attachment 285112 [details] Patch Clearing flags on attachment: 285112 Committed r204705: <http://trac.webkit.org/changeset/204705>
WebKit Commit Bot
Comment 5 2016-08-22 02:55:37 PDT
All reviewed patches have been landed. Closing bug.
youenn fablet
Comment 6 2016-08-22 09:20:59 PDT
Since fetch API requires readablestream but not writablestream, and since writablestream is less mature and stable than readable stream, bug 161044 is adding a separate compile flag for readablestream and writablestream. This allows shipping one and not the other. Note also that fetch API without streams API is not very well tested.
Note You need to log in before you can comment on or make changes to this bug.