MD Settings: Use "change" event instead of "blur" for settings-input.

MD Settings: Use "change" event instead of "blur" for settings-input.

Update the pref on the "change" event instead of the "blur" event.

The "change" event is fired when the user presses the Enter key. It
also is notably not fired if the value stays the same and the input
is blurred.

BUG=622816
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2631863002
Cr-Commit-Position: refs/heads/master@{#443756}
Committed: https://chromium.googlesource.com/chromium/src/+/604d8749c2e91c437dc6e7e0e2d541fb28770527

[tommycli, 2017-01-13 23:13:06]

Description was changed from

==========
MD Settings: Use "change" event instead of "blur" for settings-input.

Update the pref on the "change" event instead of the "blur" event.

The "change" event is fired when the user presses the Enter key. It
also is notably not fired if the value stays the same and the input
is blurred.

BUG=622816
==========

to

==========
MD Settings: Use "change" event instead of "blur" for settings-input.

Update the pref on the "change" event instead of the "blur" event.

The "change" event is fired when the user presses the Enter key. It
also is notably not fired if the value stays the same and the input
is blurred.

BUG=622816
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[tommycli, 2017-01-13 23:55:50]

tommycli@chromium.org changed reviewers:
+ dbeam@chromium.org

[tommycli, 2017-01-13 23:55:50]

dbeam: PTAL.

I tried fairly hard to write a test for this, but
MockInteractions.pressAndReleaseKey and others don't seem to work on paper-input
correctly.

I did test this manually, and can verify that it triggers correctly on Enter,
but doesn't trigger on blur when the value hasn't changed. I think this will be
a good thing.

[Dan Beam, 2017-01-14 00:01:23]

lgtm

[tommycli, 2017-01-14 00:06:58]

The CQ bit was checked by tommycli@chromium.org

[commit-bot: I haz the power, 2017-01-14 00:07:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-14 01:14:51]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1484352418528330,
"parent_rev": "e6eeb70e1252bdbed947ed41d027d377f8093dc9", "commit_rev":
"604d8749c2e91c437dc6e7e0e2d541fb28770527"}

[commit-bot: I haz the power, 2017-01-14 01:15:42]

Description was changed from

==========
MD Settings: Use "change" event instead of "blur" for settings-input.

Update the pref on the "change" event instead of the "blur" event.

The "change" event is fired when the user presses the Enter key. It
also is notably not fired if the value stays the same and the input
is blurred.

BUG=622816
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

to

==========
MD Settings: Use "change" event instead of "blur" for settings-input.

Update the pref on the "change" event instead of the "blur" event.

The "change" event is fired when the user presses the Enter key. It
also is notably not fired if the value stays the same and the input
is blurred.

BUG=622816
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2631863002
Cr-Commit-Position: refs/heads/master@{#443756}
Committed:
https://chromium.googlesource.com/chromium/src/+/604d8749c2e91c437dc6e7e0e2d5...
==========

[commit-bot: I haz the power, 2017-01-14 01:15:43]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/604d8749c2e91c437dc6e7e0e2d5...