MD Settings: Listen to the Enter key in the Add User ChromeOS dialog.

chrome/browser/resources/settings/people_page/users_add_user_dialog.html

Index: chrome/browser/resources/settings/people_page/users_add_user_dialog.html
diff --git a/chrome/browser/resources/settings/people_page/users_add_user_dialog.html b/chrome/browser/resources/settings/people_page/users_add_user_dialog.html
index cc2180c3f442f8d48fa9862852ee8b7cd273f84c..c680ac93d730efd9716515d28737fd67e194f22f 100644
--- a/chrome/browser/resources/settings/people_page/users_add_user_dialog.html
+++ b/chrome/browser/resources/settings/people_page/users_add_user_dialog.html
@@ -1,6 +1,7 @@
 <link rel="import" href="chrome://resources/cr_elements/cr_dialog/cr_dialog.html">
 <link rel="import" href="chrome://resources/html/assert.html">
 <link rel="import" href="chrome://resources/html/polymer.html">
+<link rel="import" href="chrome://resources/polymer/v1_0/iron-a11y-keys/iron-a11y-keys.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/paper-button/paper-button.html">
 <link rel="import" href="chrome://resources/polymer/v1_0/paper-input/paper-input.html">
 <link rel="import" href="/settings_shared_css.html">
@@ -19,6 +20,8 @@
     <dialog is="cr-dialog" id="dialog">
       <div class="title">$i18n{addUsers}</div>
       <div class="body">
+        <iron-a11y-keys id="keys" keys="enter" on-keys-pressed="addUser_">

[michaelpg, 2016/11/29 02:54:10]

the Polymer example sets the "target" attribute so the key is registered on the
<paper-input>. if you don't do that, does the Enter key anywhere in the dialog
trigger addUser_? in particular, would Enter on the Cancel button trigger
addUser_?

[tommycli, 2016/11/30 15:48:34]

Hello. If there is no target attr set, the target element is the parent node --
and that works nicely for me:
https://github.com/PolymerElements/iron-a11y-keys/blob/master/iron-a11y-keys....

Since the Cancel button is not in the Body div but instead in the
button-container div, the Enter key is not captured for the cancel button. I
have manually confirmed this with console logs.

See here for another example of an element without the target attr set:
https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/site_s...

[michaelpg, 2016/11/30 18:02:19]

well gee, thanks Polymer for mentioning that in your docs....

Maybe it'd be clearer to put it inside the <paper-input>, then? or am I
bikeshedding now? anyway, main point is that this works as expected even if it's
not intuitive.

[tommycli, 2016/11/30 18:14:59]

Done.

+        </iron-a11y-keys>
         <paper-input id="addUserInput" label="$i18n{addUsersEmail}" autofocus
             on-input="validate_">
         </paper-input>