MD Settings: First iteration of searching within settings.

chrome/browser/resources/settings/settings_ui/settings_ui.js

Index: chrome/browser/resources/settings/settings_ui/settings_ui.js
diff --git a/chrome/browser/resources/settings/settings_ui/settings_ui.js b/chrome/browser/resources/settings/settings_ui/settings_ui.js
index a503726438cd103b8d12ce034275deb1589a6cc7..162a0f0b758530cb8dbbc0ce42d635127fdd8061 100644
--- a/chrome/browser/resources/settings/settings_ui/settings_ui.js
+++ b/chrome/browser/resources/settings/settings_ui/settings_ui.js
@@ -57,6 +57,13 @@ Polymer({
     this.$$('app-drawer').toggle();
   },
 
+  /** @override */
+  ready: function() {
+    this.$$('cr-toolbar').addEventListener('search-changed', function(e) {

[michaelpg, 2016/07/04 19:23:56]

is it possible to type something in the search field before <settings-ui> is
ready?

[dpapad, 2016/07/06 18:24:55]

The cr-toolbar fires a bogus event during its initialization (seems like a bug
but have not investigated further). That bogus event was causing the callback to
fire before <settings-ui> was ready, so adding the listener here (instead of
adding it in HTML) fixes the issue.

On a related note, the fact that Polymer happily calls functions on a Polymer
element before that element's ready() method has been called seems like a bug to
me, but I am guessing it is WAI.

+      this.$$('settings-main').searchContents(e.detail);
+    }.bind(this));
+  },
+
   /** @private */
   directionDelegateChanged_: function() {
     this.$$('app-drawer').align = this.directionDelegate.isRtl() ?