Summary: | [Fetch API] Add fetch API compile time flag | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | youenn fablet <youennf> | ||||
Component: | WebCore Misc. | Assignee: | youenn fablet <youennf> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | achristensen, commit-queue, twarlick | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 151937 | ||||||
Attachments: |
|
Description
youenn fablet
2015-12-14 09:07:26 PST
Created attachment 267368 [details]
Patch
Comment on attachment 267368 [details]
Patch
OK, but why the use of “API” here in the name of this? All the other features are also APIs but we don’t say “API” in their conditionals.
FETCH might be a bit too generic. Also, FETCH may apply to the fetch algorithm that is exposed by the fetch API. At some point, it might be worth implementing the fetch algorithm as a replacement/refactoring of current resource loader code. Comment on attachment 267368 [details] Patch Clearing flags on attachment: 267368 Committed r194140: <http://trac.webkit.org/changeset/194140> All reviewed patches have been landed. Closing bug. |