[Mac] Pressing unsupported key should not generate keyevents

[Mac] Pressing unsupported key should not generate keyevents

On Mac with an external JIS PC keyboard, pressing "Convert",
"NonConvert" and "KanaMode" keys will always produce |NSFlagsChanged|
NSEvent with |keycode| == 255. Which will then cause blink to fire two
"keydown" events.

These three keys do not exist in Apple's Japanese keyboard, and there
is no way for us to distinguish them or get any useful information (and it requires hack to mock "keydown"/"keyup").

Safari generates two "keydown"s (with no useful information).
Firefox does not generate keyevents for these keys, this CL matches Firefox's bahavior.

BUG=601964
Committed: https://crrev.com/bac970b73d720af26ca715c1e001703217e2cfa3
Cr-Commit-Position: refs/heads/master@{#389878}

[chongz, 2016-04-26 19:57:01]

Description was changed from

==========
[Mac] Pressing unsupported key should not generate keyevents

On Mac with an external JIS PC keyboard, pressing "Convert",
"NonConvert" and "KanaMode" keys will always produce |NSFlagsChanged|
NSEvent with |keycode| == 255. Which will then cause blink to fire two
"keydown" events.

These three keys do not exist in Apple's Japanese keyboard, and there
is no way for us to distinguish them or get any useful information (and it
requires hack to mock "keydown"/"keyup").

Safari generates two "keydown"s (with no useful information).
Firefox does not generate keyevents for these keys, this CL matches Firefox's
bahavior.

BUG=601964
==========

to

==========
[Mac] Pressing unsupported key should not generate keyevents

On Mac with an external JIS PC keyboard, pressing "Convert",
"NonConvert" and "KanaMode" keys will always produce |NSFlagsChanged|
NSEvent with |keycode| == 255. Which will then cause blink to fire two
"keydown" events.

These three keys do not exist in Apple's Japanese keyboard, and there
is no way for us to distinguish them or get any useful information (and it
requires hack to mock "keydown"/"keyup").

Safari generates two "keydown"s (with no useful information).
Firefox does not generate keyevents for these keys, this CL matches Firefox's
bahavior.

BUG=601964
==========

[chongz, 2016-04-26 19:57:01]

chongz@chromium.org changed reviewers:
+ asvitkine@chromium.org

[chongz, 2016-04-26 20:00:14]

Hi asvitkine@, can you take a look at this CL please? (you are the owner of
*mac* stuff) 
Thanks!

[Alexei Svitkine (slow), 2016-04-26 20:03:00]

lgtm

[chongz, 2016-04-26 20:49:37]

The CQ bit was checked by chongz@chromium.org

[commit-bot: I haz the power, 2016-04-26 20:50:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1923023002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1923023002/1

[commit-bot: I haz the power, 2016-04-26 21:01:06]

Description was changed from

==========
[Mac] Pressing unsupported key should not generate keyevents

On Mac with an external JIS PC keyboard, pressing "Convert",
"NonConvert" and "KanaMode" keys will always produce |NSFlagsChanged|
NSEvent with |keycode| == 255. Which will then cause blink to fire two
"keydown" events.

These three keys do not exist in Apple's Japanese keyboard, and there
is no way for us to distinguish them or get any useful information (and it
requires hack to mock "keydown"/"keyup").

Safari generates two "keydown"s (with no useful information).
Firefox does not generate keyevents for these keys, this CL matches Firefox's
bahavior.

BUG=601964
==========

to

==========
[Mac] Pressing unsupported key should not generate keyevents

On Mac with an external JIS PC keyboard, pressing "Convert",
"NonConvert" and "KanaMode" keys will always produce |NSFlagsChanged|
NSEvent with |keycode| == 255. Which will then cause blink to fire two
"keydown" events.

These three keys do not exist in Apple's Japanese keyboard, and there
is no way for us to distinguish them or get any useful information (and it
requires hack to mock "keydown"/"keyup").

Safari generates two "keydown"s (with no useful information).
Firefox does not generate keyevents for these keys, this CL matches Firefox's
bahavior.

BUG=601964
==========

[commit-bot: I haz the power, 2016-04-26 21:01:07]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-26 21:02:50]

Description was changed from

==========
[Mac] Pressing unsupported key should not generate keyevents

On Mac with an external JIS PC keyboard, pressing "Convert",
"NonConvert" and "KanaMode" keys will always produce |NSFlagsChanged|
NSEvent with |keycode| == 255. Which will then cause blink to fire two
"keydown" events.

These three keys do not exist in Apple's Japanese keyboard, and there
is no way for us to distinguish them or get any useful information (and it
requires hack to mock "keydown"/"keyup").

Safari generates two "keydown"s (with no useful information).
Firefox does not generate keyevents for these keys, this CL matches Firefox's
bahavior.

BUG=601964
==========

to

==========
[Mac] Pressing unsupported key should not generate keyevents

On Mac with an external JIS PC keyboard, pressing "Convert",
"NonConvert" and "KanaMode" keys will always produce |NSFlagsChanged|
NSEvent with |keycode| == 255. Which will then cause blink to fire two
"keydown" events.

These three keys do not exist in Apple's Japanese keyboard, and there
is no way for us to distinguish them or get any useful information (and it
requires hack to mock "keydown"/"keyup").

Safari generates two "keydown"s (with no useful information).
Firefox does not generate keyevents for these keys, this CL matches Firefox's
bahavior.

BUG=601964

Committed: https://crrev.com/bac970b73d720af26ca715c1e001703217e2cfa3
Cr-Commit-Position: refs/heads/master@{#389878}
==========

[commit-bot: I haz the power, 2016-04-26 21:02:50]

Patchset 1 (id:??) landed as
https://crrev.com/bac970b73d720af26ca715c1e001703217e2cfa3
Cr-Commit-Position: refs/heads/master@{#389878}