commit | fad6942ba975d99d0f1a4fbece0b913bb354472d | [log] [tgz] |
---|---|---|
author | Richard Li <richard.li@intel.com> | Fri Nov 09 02:26:41 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Nov 09 02:26:41 2018 |
tree | abfb5199b234a3ebf92645dc25c0925485952027 | |
parent | a139bcca1919064e41cbac2925a79bf810016964 [diff] |
[OnionSoup] Remove content::SWFetchRequest in background_fetch/ folder The target of this CL is removing content::SWFetchRequest and use blink::mojom::FetchAPIRequest instead. To keep a minor size of CL, the operation is restricted in content/browser/background_fetch/. The final goal is removing content::SWFetchRequest completely. As a part of work of moving fetch_api_request.mojom, the roadmap is as follow: 1. Remove content::RequestContextType. Use blink.mojom.RequestContextType instead. --------- CL:1229704 2. Remove content::ServiceWorkerFetchRequest. Use blink.mojom.FetchAPIRequest instead. --------(CL:1288084 and This CL) 3. Remove blink::WebURLRequest::RequestContext. Use blink.mojom.RequestContextType instead. --------- CL:1242301 4. Remove blink::WebServiceWorkerRequest. Use blink.mojom.FetchAPIRequest instead. 5. Remove blink::WebReferrerPolicy. Use blink::mojom::ReferrerPolicy instead. --------- CL:1212345 6. Remove content::Referrer, blink::Referrer Use blink::mojom::Referrer instead. Once all the above tasks get done, fetch_api_request.mojom can be moved into third_party/blink/public/mojom/fetch/. Bug: 789854 Change-Id: I9b442b3329293b21d483f468c3b4264526104b85 Reviewed-on: https://chromium-review.googlesource.com/c/1312673 Commit-Queue: Richard Li <richard.li@intel.com> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Reviewed-by: Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#606707}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .