MD Settings: Implement search URLs.

chrome/browser/resources/settings/settings_ui/settings_ui.html

Index: chrome/browser/resources/settings/settings_ui/settings_ui.html
diff --git a/chrome/browser/resources/settings/settings_ui/settings_ui.html b/chrome/browser/resources/settings/settings_ui/settings_ui.html
index 854d575bfa544ad6216044e45a355dfe569d19e7..b0e43104e377c49853d3ac4683ed5b4b9083e1ed 100644
--- a/chrome/browser/resources/settings/settings_ui/settings_ui.html
+++ b/chrome/browser/resources/settings/settings_ui/settings_ui.html
@@ -92,6 +92,7 @@
         on-cr-toolbar-menu-tap="onMenuButtonTap_"
         spinner-active="[[toolbarSpinnerActive_]]"
         menu-label="$i18n{menuButtonLabel}"
+        on-search-changed="onSearchChanged_"

[tommycli, 2016/11/01 21:05:26]

nit: it seems like this event should be called on-search-query-changed? Can be
separate CL, just nitpicking.

[dpapad, 2016/11/01 22:02:02]

The native HTML <input type="search"> element is firing a simple 'search' event.
We chose 'search-changed' for the shared cr-search-field element, since unlike
the native element, it only fires if the value actually changed. I think is fine
since it is shorter than 'search-query-changed' without being too cryptic
hopefully.

[tommycli, 2016/11/01 22:05:47]

Acknowledged.

         show-menu>
     </cr-toolbar>
     <app-drawer swipe-open>
@@ -109,7 +110,8 @@
       <settings-main prefs="{{prefs}}"
           toolbar-spinner-active="{{toolbarSpinnerActive_}}"
           page-visibility="[[pageVisibility_]]"
-          advanced-toggle-expanded="{{advancedOpened_}}">
+          advanced-toggle-expanded="{{advancedOpened_}}"
+          search-query="[[searchQuery_]]">
       </settings-main>
     </paper-header-panel>
   </template>