[MD Settings] Implement search in material design passwords.

chrome/browser/resources/settings/settings_page/settings_subpage.js

 // Copyright 2016 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-subpage' shows a subpage beneath a subheader. The header contains
  * the subpage title and a back icon. The back icon fires an event which
  * is caught by settings-animated-pages, so it requires no separate handling.
  */
 
 Polymer({
   is: 'settings-subpage',
 
   behaviors: [
     // TODO(michaelpg): phase out NeonAnimatableBehavior.
     Polymer.NeonAnimatableBehavior,
     Polymer.IronResizableBehavior,
   ],
 
   properties: {
     pageTitle: String,
+
+    /** Setting a |searchLabel| will enable search. */
+    searchLabel: String,
+
+    searchTerm: {
+      type: String,
+      notify: true,
+      value: '',
+    },
   },
 
   /** @private */
   onTapBack_: function() {
     // Event is caught by settings-animated-pages.
     this.fire('subpage-back');
   },
+
+  /** @private */
+  onSearchChanged_: function(e) {
+    this.searchTerm = e.detail;
+    this.notifyPath('searchTerm', this.searchTerm);

[dpapad, 2016/07/20 19:34:51]

Is the call to notifyPath necessary?
Given that we use "notify: true" for |searchTerm|, and that it is bound with a
2-way binding to the parent's |passwordFilter| it seems that it is not.

[hcarmona, 2016/07/20 21:06:07]

Not necessary. Removed.

+  },
 });