Generate located Windows keycodes for number pad keys under Ozone

Generate located Windows keycodes for number pad keys under Ozone

Makes Ozone's XKB keyboard layout support generate Windows keycodes
VKEY_NUMPAD0 through VKEY_NUMPAD9 for number pad keys, rather than
VKEY_0 through VKEY_9, to match the X11 behaviour.

BUG=574458
Committed: https://crrev.com/631eb39240d4f2f2bb9c764f1adc225e844791d5
Cr-Commit-Position: refs/heads/master@{#381709}

[kpschoedel, 2016-01-05 20:30:25]

Description was changed from

==========
Generate located Windows keycodes for number pad keys under Ozone

Makes Ozone's XKB keyboard layout support generate Windows keycodes
VKEY_NUMPAD0 through VKEY_NUMPAD9 for number pad keys, rather than
VKEY_0 through VKEY_9, to match the X11 behaviour.

BUG=574458
==========

to

==========
Generate located Windows keycodes for number pad keys under Ozone

Makes Ozone's XKB keyboard layout support generate Windows keycodes
VKEY_NUMPAD0 through VKEY_NUMPAD9 for number pad keys, rather than
VKEY_0 through VKEY_9, to match the X11 behaviour.

BUG=574458
==========

[kpschoedel, 2016-01-05 20:30:25]

kpschoedel@chromium.org changed reviewers:
+ dtapuska@chromium.org

[dtapuska, 2016-01-08 01:10:23]

lgtm

[dtapuska, 2016-03-17 14:15:56]

On 2016/01/08 01:10:23, dtapuska wrote:
> lgtm

are you going to land this?

[kpschoedel, 2016-03-17 14:21:07]

The CQ bit was checked by kpschoedel@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-03-17 14:21:25]

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

[kpschoedel, 2016-03-17 14:22:24]

On 2016/03/17 14:15:56, dtapuska wrote:
> are you going to land this?

Sorry, forgot it existed.

[commit-bot: I haz the power, 2016-03-17 14:53:58]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-03-17 14:53:59]

Dry run: This issue passed the CQ dry run.

[kpschoedel, 2016-03-17 14:55:32]

The CQ bit was checked by kpschoedel@chromium.org

[commit-bot: I haz the power, 2016-03-17 14:55:45]

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

[commit-bot: I haz the power, 2016-03-17 15:00:45]

Description was changed from

==========
Generate located Windows keycodes for number pad keys under Ozone

Makes Ozone's XKB keyboard layout support generate Windows keycodes
VKEY_NUMPAD0 through VKEY_NUMPAD9 for number pad keys, rather than
VKEY_0 through VKEY_9, to match the X11 behaviour.

BUG=574458
==========

to

==========
Generate located Windows keycodes for number pad keys under Ozone

Makes Ozone's XKB keyboard layout support generate Windows keycodes
VKEY_NUMPAD0 through VKEY_NUMPAD9 for number pad keys, rather than
VKEY_0 through VKEY_9, to match the X11 behaviour.

BUG=574458
==========

[commit-bot: I haz the power, 2016-03-17 15:00:46]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-17 15:02:21]

Description was changed from

==========
Generate located Windows keycodes for number pad keys under Ozone

Makes Ozone's XKB keyboard layout support generate Windows keycodes
VKEY_NUMPAD0 through VKEY_NUMPAD9 for number pad keys, rather than
VKEY_0 through VKEY_9, to match the X11 behaviour.

BUG=574458
==========

to

==========
Generate located Windows keycodes for number pad keys under Ozone

Makes Ozone's XKB keyboard layout support generate Windows keycodes
VKEY_NUMPAD0 through VKEY_NUMPAD9 for number pad keys, rather than
VKEY_0 through VKEY_9, to match the X11 behaviour.

BUG=574458

Committed: https://crrev.com/631eb39240d4f2f2bb9c764f1adc225e844791d5
Cr-Commit-Position: refs/heads/master@{#381709}
==========

[commit-bot: I haz the power, 2016-03-17 15:02:22]

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