RESOLVED WONTFIX177982
Add ObjC SPI equivalent to WKResourceCacheManagerClearCacheForOrigin 
https://bugs.webkit.org/show_bug.cgi?id=177982
Summary Add ObjC SPI equivalent to WKResourceCacheManagerClearCacheForOrigin
Alex Christensen
Reported 2017-10-05 17:35:37 PDT
Add ObjC SPI equivalent to WKResourceCacheManagerClearCacheForOrigin
Attachments
Patch (4.57 KB, patch)
2017-10-05 17:36 PDT, Alex Christensen 		no flags
DetailsFormatted DiffDiff
Patch (4.68 KB, patch)
2017-10-06 10:40 PDT, Alex Christensen 		achristensen: review-
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Alex Christensen
Comment 1 2017-10-05 17:36:58 PDT
Created attachment 322950 [details] Patch
Tim Horton
Comment 2 2017-10-05 21:55:22 PDT
Comment on attachment 322950 [details] Patch What's the excuse for this one being Mac only? :P
Jessie Berlin
Comment 3 2017-10-06 09:35:25 PDT
We will need this on both macOS and iOS - why is it macOS only?
Alex Christensen
Comment 4 2017-10-06 10:31:05 PDT
This SPI exists to help make the transition not have a change in behavior. This SPI should not become the new way of doing things. If we want to unite iOS and MacOS behavior, it should not be to this.
Alex Christensen
Comment 5 2017-10-06 10:40:22 PDT
Created attachment 323026 [details] Patch
Alex Christensen
Comment 6 2017-10-06 10:41:24 PDT
Comment on attachment 323026 [details] Patch There we go. I added a completion handler and made it available on iOS, too. I think it is a bad idea to make this so it can become adopted, but I'm not going to prevent it here.
Alex Christensen
Comment 7 2017-10-06 10:59:00 PDT
Comment on attachment 323026 [details] Patch Since we can still use WKResourceCacheManagerClearCacheForOrigin with an ObjC object toll-free-bridged, this is not blocking WKWebView adoption and I think it should not be committed. We can find a good solution for both platforms later.
Jeff Miller
Comment 8 2017-10-09 10:29:53 PDT
After further investigation, I don't think this is necessary at all. See <rdar://problem/23711777>.
Note You need to log in before you can comment on or make changes to this bug.