MD WebUI: Improve tab focus behavior for toolbar search field

ui/webui/resources/cr_elements/cr_toolbar/cr_toolbar_search_field.html

Index: ui/webui/resources/cr_elements/cr_toolbar/cr_toolbar_search_field.html
diff --git a/ui/webui/resources/cr_elements/cr_toolbar/cr_toolbar_search_field.html b/ui/webui/resources/cr_elements/cr_toolbar/cr_toolbar_search_field.html
index c65855b1606af50a58edd2b9a740487ace383314..d0f994fcd1d7a40b1085bc506d91cd35e3fa1e48 100644
--- a/ui/webui/resources/cr_elements/cr_toolbar/cr_toolbar_search_field.html
+++ b/ui/webui/resources/cr_elements/cr_toolbar/cr_toolbar_search_field.html
@@ -82,11 +82,12 @@
         -webkit-margin-start: 18px;
       }
     </style>
-    <paper-icon-button id="icon" icon="cr:search"
-        title="[[label]]">
+    <paper-icon-button id="icon" icon="cr:search" title="[[label]]"
+        tabindex$="[[computeIconTabIndex_(narrow)]]">
     </paper-icon-button>
     <paper-input-container on-search="onSearchTermSearch_"
-        on-keydown="onSearchTermKeydown_" no-label-float>
+        on-keydown="onSearchTermKeydown_" on-keypress="onSearchTermKeypress_"

[dpapad, 2016/05/31 18:57:58]

It is confusing that onSearchTermKeydown_ is a reference to a private method of
the behavior. Since this method is used outside the behavior, I think it should
be public.

Also why are we using both keypress and keydown events here and not just stick
with one of the two?

[tsergeant, 2016/06/01 01:20:49]

Good point, done.
 
Keydown is used in the behavior because it wants to pick up the Escape key,
which does not fire keypress events.

Keypress is used in this CL because it doesn't want to pick up non-text keys
like Esc, Tab, Shift, etc, which all fire keydown events but not keypress
events. I've added a comment to explain this.

+        no-label-float>
       <label id="prompt" for="searchInput">[[label]]</label>
       <input is="iron-input" id="searchInput" type="search"
           on-blur="onInputBlur_" incremental></input>