MD History: Refresh the list when clearing browsing data

chrome/browser/resources/md_history/history.js

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // Send the history query immediately. This allows the query to process during
 // the initial page startup.
 chrome.send('queryHistory', ['', 0, 0, 0, RESULTS_PER_PAGE]);
 chrome.send('getForeignSessions');
 
 /** @type {Promise} */
@@ skipping 67 matching lines @@
   waitForAppUpgrade().then(function() {
     /** @type {HistoryAppElement} */($('history-app'))
         .setForeignSessions(sessionList, isTabSyncEnabled);
   });
 }
 
 /**
  * Called when the history is deleted by someone else.
  */
 function historyDeleted() {
+  waitForAppUpgrade().then(function() {
+    // Call into list-container to restore search state.
+    /** @type {HistoryListContainerElement} */($('history-app').$['history'])

[Dan Beam, 2016/08/04 00:30:46]

we really need a lint rule about thing.$.localId

everybody i've talked to has agreed to treat this basically like private state
but i keep seeing this

[tsergeant, 2016/08/04 01:25:55]

Yup, please avoid directly accessing local DOM of other elements. You can either
add a getter for the <history-list-container> to <history-app>, or add a new
method to <history-app> to handle this callback (which is basically what we do
elsewhere in this file, even though it's not ideal).

[Dan Beam, 2016/08/04 03:23:44]

https://codereview.chromium.org/2209053002/

[lshang, 2016/08/05 03:39:03]

Done.

+        .queryHistory(false);
+  });
 }
 
 /**
  * Called by the history backend after user's sign in state changes.
  * @param {boolean} isUserSignedIn Whether user is signed in or not now.
  */
 function updateSignInState(isUserSignedIn) {
   waitForAppUpgrade().then(function() {
     /** @type {HistoryAppElement} */($('history-app'))
         .updateSignInState(isUserSignedIn);
   });
 }