[MD History] Unify query state in history-app.

chrome/browser/resources/md_history/app.html

Index: chrome/browser/resources/md_history/app.html
diff --git a/chrome/browser/resources/md_history/app.html b/chrome/browser/resources/md_history/app.html
index 3f42a738bcd2018d50d49b00a93dd1d9e1235db6..9a7294f73232dfe7b378ff60a5a1a01946bb49c6 100644
--- a/chrome/browser/resources/md_history/app.html
+++ b/chrome/browser/resources/md_history/app.html
@@ -38,14 +38,20 @@
         background: var(--md-toolbar-color);
       }
     </style>
-    <history-toolbar id="toolbar"></history-toolbar>
+    <history-toolbar id="toolbar" searching="[[queryState_.querying]]"
+        search-term="{{queryState_.searchTerm}}"
+        query-start-time="[[queryState_.queryStartTime]]"
+        query-end-time="[[queryState_.queryEndTime]]">
+    </history-toolbar>
 
     <div id="main-container">
       <history-side-bar id="history-side-bar" selected-page="{{selectedPage}}">
       </history-side-bar>
       <iron-pages id="content" attr-for-selected="id"
           selected="{{selectedPage}}">
-        <history-list id="history-list"></history-list>
+        <history-list id="history-list" querying="[[queryState_.querying]]"
+            searched-term="{{queryState_.info.term}}">

[tsergeant, 2016/05/13 03:41:06]

If I'm reading this correctly, this will set searchedTerm before the results
actually come from the backend?

Does this have any side effects? Eg, changing "100 results for Search 1" to "100
results for Search 2" before the results change.

Having searchedTerm be inconsistent scares me a little.

[calamity, 2016/05/18 01:41:52]

As discussed, this is set when the query returns.

+        </history-list>
         <history-synced-device-manager id="history-synced-device-manager">
         </history-synced-device-manager>
       </iron-pages>