Reduced test case:

* on OS X, change the keyboard layout to use Dvorak - QWERTY ⌘
* go to https://jsfiddle.net/v1gz5c5m/1/
* this is a page that logs the values for code, keyCode and key that are generated by Chromium on the keydown event

* you have to be very fast, as the keypress will trigger a browser reload, but please observe:

 * pressing Cmd+R => keyCode: 82 <--- this is correct as it is equal to 0x52 which is AFAIK the keyCode for the R key ( https://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx )

 * pressing Cmd+Option+R => keyCode: 80 <--- this is unexpected, it should be 82 again

Anyways, it is not clear to me if this is how this specific keyboard layout works or if this is a bug in Chromium (what the OP claims). In any way, we are stuck in VS Code.

Thank you for your awesome work!

I tried the jsfiddle in Safari and saw the same bug, maybe it dates back to the shared heritage in webkit?

Here is a fork of the fiddle with preventDefault so you don't leave the page:
https://jsfiddle.net/sf73k2a4/

+label:blink which is probably more suitable.

Why do you need to use keyCode? There are a number of situations where keyCode is broken are you able to get away from using keyCode and use key and code?

I can't speak for the vs code team, but they tried to change away from using keyCode for keyboard commands and it ended up breaking my keyboard layout for all commands (not just the ones with option held down):

https://github.com/Microsoft/vscode/issues/23986

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is the same behavior as in Safari and is actually the value returned to use from the operating system.

The code checks to see if it can convert the char to a windows key code and if it can't it looks at the character without modifiers applied and returns that. The OS is returning us this value and it isn't applying the Command map either so the value is turning out to be 80.

The NextAction date has arrived: 2017-06-15