MD History: Move queryState to be managed by history-router

chrome/browser/resources/md_history/router.js

Index: chrome/browser/resources/md_history/router.js
diff --git a/chrome/browser/resources/md_history/router.js b/chrome/browser/resources/md_history/router.js
index 6b3cdd81087fadf44cab27556c91f9fc927e7f2b..36eacaa8a844154b95cbd53143fa9a13ae66a692 100644
--- a/chrome/browser/resources/md_history/router.js
+++ b/chrome/browser/resources/md_history/router.js
@@ -12,9 +12,30 @@ Polymer({
       notify: true,
     },
 
+    /** @type {QueryState} */
     queryState: {
       type: Object,
       notify: true,
+      value: function() {
+        // TODO(tsergeant: Move this initialization into query-manager.

[calamity, 2017/01/17 06:22:10]

Just wondering, why's this hard to do this patch?

[tsergeant, 2017/01/18 03:36:00]

It's an initialization order thing.

If queryState was initialized in query-manager (which initialises first), when
router initializes it will see the top-down command to set searchTerm to ''
before it sees the bottom-up command to set searchTerm to whatever is in the
URL. This means that query strings in the URL get ignored.

I'm honestly not 100% sure why this isn't a problem in the next patch. I'll dig
into it a bit more and let you know.

+        return {
+          // Whether the most recent query was incremental.
+          incremental: false,
+          // A query is initiated by page load.
+          querying: true,
+          queryingDisabled: false,
+          _range: HistoryRange.ALL_TIME,
+          searchTerm: '',
+          groupedOffset: 0,
+
+          set range(val) {
+            this._range = Number(val);
+          },
+          get range() {
+            return this._range;
+          },
+        };
+      },
     },
 
     path_: {