NTP Zombie Code Slayer III, The Saga Continues: Foreign Sessions

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 3ac878ef774ad4301d4eb104f570bd44562d00a0..11b3741bc3fda2975a03afa85445df113306b5c5 100644
--- a/chrome/browser/resources/history/other_devices.js
+++ b/chrome/browser/resources/history/other_devices.js
@@ -14,7 +14,6 @@
 /** @const */ var NB_ENTRIES_OTHER_ROWS_COLUMN = 0;
 
 // Histogram buckets for UMA tracking of menu usage.
-// Using the same values as the Other Devices button in the NTP.
 /** @const */ var HISTOGRAM_EVENT = {
   INITIALIZED: 0,
   SHOW_MENU: 1,
@@ -43,10 +42,6 @@ function recordUmaEvent_(eventId) {
 
 /**
  * Controller for the context menu for device names in the list of sessions.
- * This class is designed to be used as a singleton. Also copied from existing
- * other devices button in NTP.
- * TODO(mad): Should we extract/reuse/share with ntp4/other_sessions.js?
- *
  * @constructor
  */
 function DeviceContextMenuController() {
@@ -562,8 +557,7 @@ function load() {
   if (!loadTimeData.getBoolean('isInstantExtendedApiEnabled'))
     return;
 
-  // We must use this namespace to reuse the handler code for foreign session
-  // and login.
+  // TODO(dbeam): why is this call NTP-specific? Doesn't make any sense.
   cr.define('ntp', function() {
     return {
       setForeignSessions: setForeignSessions,