MD Settings: fix incorrect behavior with Enter on bluetooth item's icon-button.

chrome/browser/resources/settings/bluetooth_page/bluetooth_device_list_item.js

Index: chrome/browser/resources/settings/bluetooth_page/bluetooth_device_list_item.js
diff --git a/chrome/browser/resources/settings/bluetooth_page/bluetooth_device_list_item.js b/chrome/browser/resources/settings/bluetooth_page/bluetooth_device_list_item.js
index 5f0dee2bdde2c6d898c54f88284cb7e8b9f86980..048908d6c0e965dd87820fafb6bdd92301b182b2 100644
--- a/chrome/browser/resources/settings/bluetooth_page/bluetooth_device_list_item.js
+++ b/chrome/browser/resources/settings/bluetooth_page/bluetooth_device_list_item.js
@@ -21,6 +21,24 @@ Polymer({
     },
   },
 
+  listeners: {
+    'keydown': 'onKeyDown_',
+  },
+
+  /**
+   * This is necessary, otherwise pressing enter will first trigger iron-list's
+   * keydown handler and intefere with icon-button's on-tap behavior.
+   * @param {!Event} event
+   * @private
+   */
+  onKeyDown_: function(event) {
+    if (event.key == 'Enter' &&
+        Polymer.dom(event).rootTarget ==
+            this.$$('button[is="paper-icon-button-light"]')) {
+      event.stopPropagation();
+    }
+  },

[dschuyler, 2017/06/20 18:46:51]

When we have a chance, I'd like to chat about whether this should be made into a
behavior (stevenjb@'s suggestion), or if it's really a one-off. And if it's a
one-off, I'd like to explore (or push for) adjusting the UI here so that it
doesn't need special handling.

[scottchen, 2017/06/20 19:17:19]

I think we might've talked about this before, but basically I had to do this in
FocusRowBehavior to avoid iron-list's Enter-key listener causing problems, but
FocusRowBehavior can't be applied here, because the behavior assumes the row
itself should not focusable (which is not the case here).

So possible solutions:
1) tweak focus-row-behavior to optionally allow the row itself to be focused
(maybe based on a flag?) and behave accordingly, then apply the behavior here.
2) make the UI such that "row itself is focusable & actionable, but also has
focusable & actionable controls as children"  is not a thing.

Also as a side note, I personally feel like network/bluetooth's row behavior is
weird, because pressing the Enter key on a focused row does completely different
things (i.e. connects if not already connected, or goes to a subpage if it is
connected).

[stevenjb, 2017/07/10 22:48:53]

Can this be done more simply like:

<button ... on-keydown="doNothing_">

doNothing_: function(event) {
  event.stopPropagation();
}

?

[scottchen, 2017/07/12 19:12:49]

Looks like yes we can! PTAL.

+
   /**
    * @param {!Event} event
    * @private