[Sync] Removing complexity around PROXY_TABS now that empty sessions are provided when disabled.

chrome/browser/resources/history/other_devices.js

Index: chrome/browser/resources/history/other_devices.js
diff --git a/chrome/browser/resources/history/other_devices.js b/chrome/browser/resources/history/other_devices.js
index 2ba6f76f246f08eecd50052be2461b93a57c2ee6..0a10191e0f7c0728249850012f6034644766c930 100644
--- a/chrome/browser/resources/history/other_devices.js
+++ b/chrome/browser/resources/history/other_devices.js
@@ -541,18 +541,12 @@ DevicesView.prototype.displayResults_ = function() {
 /**
  * Sets the menu model data. An empty list means that either there are no
  * foreign sessions, or tab sync is disabled for this profile.
- * |isTabSyncEnabled| makes it possible to distinguish between the cases.
  *
  * @param {Array} sessionList Array of objects describing the sessions
  *     from other devices.
- * @param {boolean} isTabSyncEnabled Is tab sync enabled for this profile?
  */
-function setForeignSessions(sessionList, isTabSyncEnabled) {
-  // The other devices is shown iff tab sync is enabled.
-  if (isTabSyncEnabled)
-    devicesView.setSessionList(sessionList);
-  else
-    devicesView.clearDOM();
+function setForeignSessions(sessionList) {
+  devicesView.setSessionList(sessionList);
 }
 
 /**