Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(255)

Unified Diff: components/history/core/browser/history_model_worker.cc

Issue 2942773002: Task Scheduler API migration: change BrowserThreadModelWorker to SequencedModelWorker (Closed)
Patch Set: Updated more comments to reflect thread -> sequence migration. Created 3 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: components/history/core/browser/history_model_worker.cc
diff --git a/components/history/core/browser/history_model_worker.cc b/components/history/core/browser/history_model_worker.cc
index ad3f9911e7ab73cd71fd5d272a1c8d24b4db6024..7ae6d603873e3f165c7501e7f287137d00216033 100644
--- a/components/history/core/browser/history_model_worker.cc
+++ b/components/history/core/browser/history_model_worker.cc
@@ -63,7 +63,7 @@ syncer::ModelSafeGroup HistoryModelWorker::GetModelSafeGroup() {
return syncer::GROUP_HISTORY;
}
-bool HistoryModelWorker::IsOnModelThread() {
+bool HistoryModelWorker::IsOnModelSequence() {
// Ideally HistoryService would expose a way to check whether this is the
// history DB thread. Since it doesn't, just return true to bypass a CHECK in
// the sync code.

Powered by Google App Engine
This is Rietveld 408576698