Update WebAPKs even if the WebAPK start URL has no Web Manifest part 2/3
The class name ManifestUpgradeDetector does not make sense in the context of the new ManifestUpgradeDetector#Callback. The new callback can be called up to twice: - Once after the initial page load. (Regardless of whether the page uses the correct Web Manifest) - Once after a page which uses the correct Web Manifest has finished loading. If a Web Developer removes the Web Manifest from their site, the second call is never done. This CL: - moves the check for "whether the fetched Web Manifest requires a WebAPK upgrade" into WebApkUpdateManager. - merges the manifest fetching parts of ManifestUpgradeDetector and ManifestUpgradeDetectorFetcher into a new class WebApkUpdateDataFetcher BUG=639536 Review-Url: https://codereview.chromium.org/2460253002 Cr-Commit-Position: refs/heads/master@{#437641}
Showing
This diff is collapsed.
Please register or sign in to comment