NEW 216559
Remove runtime setting for enabling/disabling the Cache API? 
https://bugs.webkit.org/show_bug.cgi?id=216559
Summary Remove runtime setting for enabling/disabling the Cache API?
Sam Weinig
Reported 2020-09-15 09:25:28 PDT
Remove runtime setting for enabling/disabling the Cache API. It should always be enabled at this point.
Attachments
Add attachment proposed patch, testcase, etc.
Sam Weinig
Comment 1 2020-09-17 18:16:56 PDT
Looking at the implementation, it looks like this feature was never implemented for WebKitLegacy and seems to be intertwined with the network disk cache in WebKit2. Antti, Chris, can you remind me why the disk cache logic was put into WebKit2? Is it something we could bring into WebCore at some point and use for both WebKitLegacy and WebKit2?
Antti Koivisto
Comment 2 2020-09-18 09:02:32 PDT
It was easier to make it WK2 only. It is not clear that risking breaking legacy clients by changing cache behavior is even desirable. The feature was introduced for WK2 clients with linked-on-or-after check. We have plenty of other APIs that are not supported in WK1, right?
Sam Weinig
Comment 3 2020-09-18 09:07:07 PDT
(In reply to Antti Koivisto from comment #2) > It was easier to make it WK2 only. It is not clear that risking breaking > legacy clients by changing cache behavior is even desirable. The feature was > introduced for WK2 clients with linked-on-or-after check. > > We have plenty of other APIs that are not supported in WK1, right? I don't know. We certainly don't have it well documented what works in WebKit1 vs. WebKit2, which seems lie a pretty big potential footgun waiting to happen.
Radar WebKit Bug Importer
Comment 4 2020-09-22 09:26:15 PDT
<rdar://problem/69374740>
Note You need to log in before you can comment on or make changes to this bug.