StoragePartitionHttpCacheDataRemover: Properly handle async result from both wasm and js caches
Both calls can't be invoked on the same step with the state machine as the callback, as two asynchronous (net::ERR_IO_PENDING) returns mean that the callback would be invoked twice, and it's not meant for that (what with one invocation queuing self-deletion...) Also improve testing somewhat to actually make sure the wasm stuff is deleted as well. Longer-term, this should probably be elsewhere, this method isn't generally used with NetworkService (see: crbug.com/892652) Bug: 892583 Change-Id: I61be72c19f4ec713a2c27e5c4be963f603f3df20 Reviewed-on: https://chromium-review.googlesource.com/c/1264917Reviewed-by:Joshua Bell <jsbell@chromium.org> Reviewed-by:
John Abd-El-Malek <jam@chromium.org> Commit-Queue: Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#597572}
Showing
Please register or sign in to comment