Connect BackgroundFetch to the OfflineItemCollection

content/browser/background_fetch/background_fetch_context.cc

Index: content/browser/background_fetch/background_fetch_context.cc
diff --git a/content/browser/background_fetch/background_fetch_context.cc b/content/browser/background_fetch/background_fetch_context.cc
index 5506585dfe2f993d31be576d4f4ef9297179a3a1..4871ac072777c3795ddf8647511c3aa0dda76b69 100644
--- a/content/browser/background_fetch/background_fetch_context.cc
+++ b/content/browser/background_fetch/background_fetch_context.cc
@@ -101,4 +101,13 @@ void BackgroundFetchContext::DidFinishFetch(
   active_fetches_.erase(registration_id);
 }
 
+void BackgroundFetchContext::CancelDownload(
+    const std::string& registration_id) {}

[Peter Beverloo, 2017/03/29 14:32:12]

micro nit: lack of symmetry in the argument names in the .h/.cc

[harkness, 2017/03/30 12:42:35]

Done.

+
+void BackgroundFetchContext::PauseDownload(const std::string& registration_id) {
+}
+
+void BackgroundFetchContext::ResumeDownload(
+    const std::string& registration_id) {}

[Peter Beverloo, 2017/03/29 14:32:12]

nit: it'd be best to hook these up with the JobController already. (Or add a
TODO if you're worried about merge failures.) Ideally we'd just have
BackgroundFetchJobController::{Cancel,Pause,Resume}, super short and clear.

I guess we should change or extend GetActiveFetch() to also be able to return
inactive background fetches to accommodate for these methods?

[harkness, 2017/03/30 12:42:35]

My plan was to hook these up in the next CL to minimize merge conflicts since
there are such major changes elsewhere.

+
 }  // namespace content