MD Settings: First iteration of searching within settings.

chrome/browser/resources/settings/settings_ui/settings_ui.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.
 
 /**
  * @fileoverview
  * 'settings-ui' implements the UI for the Settings page.
  *
  * Example:
  *
@@ skipping 39 matching lines @@
   onIronActivate_: function(event) {
     if (event.detail.item.id != 'advancedPage')
       this.$$('app-drawer').close();
   },
 
   /** @private */
   onMenuButtonTap_: function() {
     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() ?
         'right' : 'left';
   },
 });