UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2734.0 Safari/537.36

Example URL:
https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html

Steps to reproduce the problem:
1. Go to https://dvcs.w3.org/hg/d4e/raw-file/tip/key-event-test.html
2. (Click "Show Options" and check the "keydown" of "preventDefault" for easier to test)
3. Press a multimedia key (e.g., media player key or play/pause key) or a browser navigation key (e.g., back, forward, etc).

What is the expected behavior?
These keypress should cause keydown and keyup events with proper KeyboardEvent.key value.

What went wrong?
No keyboard events are fired on Chrome Canary.

Looks like Chromium ignores the device information of WM_APPCOMMAND here:
https://code.google.com/p/chromium/codesearch#chromium/src/ui/views/win/hwnd_message_handler.cc&q=OnAppCommand&sq=package:chromium&type=cs&l=1258

> BOOL HWNDMessageHandler::OnAppCommand(HWND window,
>                                       short command,
>                                       WORD device,
>                                       int keystate) {
>   BOOL handled = !!delegate_->HandleAppCommand(command);

Firefox fixed this bug at: https://bugzilla.mozilla.org/show_bug.cgi?id=865561

Current code of Firefox is here:
https://dxr.mozilla.org/mozilla-central/rev/c3f5e6079284a7b7053c41f05d0fe06ff031db03/widget/windows/KeyboardLayout.cpp#1360,1376,1388,1393,1397-1398,1475,1480,1484-1485

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? Yes 

Chrome version: 52.0.2734.0  Channel: canary
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0