Change FaviconRequestHandler internal check for use of favicon server

We verify the upload state of SESSIONS instead of
HISTORY_DELETE_DIRECTIVES.

Bug: 980563
Change-Id: I9178c1df1f63de7ac8ad20f3470d89a14d8062dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1685384
Commit-Queue: Victor Vianna <victorvianna@google.com>
Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#675215}
diff --git a/chrome/browser/favicon/history_ui_favicon_request_handler_factory.cc b/chrome/browser/favicon/history_ui_favicon_request_handler_factory.cc
index 3212bfe..2c09a117a 100644
--- a/chrome/browser/favicon/history_ui_favicon_request_handler_factory.cc
+++ b/chrome/browser/favicon/history_ui_favicon_request_handler_factory.cc
@@ -33,8 +33,8 @@
 }
 
 bool CanSendHistoryData(syncer::SyncService* sync_service) {
-  return syncer::GetUploadToGoogleState(
-             sync_service, syncer::ModelType::HISTORY_DELETE_DIRECTIVES) ==
+  return syncer::GetUploadToGoogleState(sync_service,
+                                        syncer::ModelType::SESSIONS) ==
          syncer::UploadState::ACTIVE;
 }