[Windows] Produce correct DomKey for NumPad when combined with Shift/NumLock

ui/events/event.cc

Index: ui/events/event.cc
diff --git a/ui/events/event.cc b/ui/events/event.cc
index ca6704b6f8fa5b6e49888074b799c620b7bc90e2..7bb82a9a43f769b7e2010a9f1d3d8d21f5d07307 100644
--- a/ui/events/event.cc
+++ b/ui/events/event.cc
@@ -865,7 +865,8 @@ KeyEvent::KeyEvent(const base::NativeEvent& native_event)
   if (is_char_)
     key_ = DomKey::FromCharacter(native_event.wParam);
   else
-    key_ = PlatformKeyMap::DomCodeAndFlagsToDomKeyStatic(code_, flags());
+    key_ = PlatformKeyMap::DomCodeAndFlagsToDomKeyStatic(code_, key_code_,

[dtapuska, 2016/03/10 20:51:44]

This is certainly odd that we require the key_code_ to be passed in but as you
demonstrated the shift state is incorrect (thanks to native Windows events); so
I don't see how else we could do this.

[Wez, 2016/03/16 21:03:06]

So sad. ;(  Perhaps it would be cleanest to pass in the base::NativeEvent, and
let the PlatformKeyMap pull whatever data it needs out of that?  Passing the
partially-complete KeyEvent would also work, but then you're committed to
keeping the key_code_ field around, where in future it might be possible to kill
it & reconstruct it on-the-fly from the other fields & keymap.

+                                                         flags());
 #endif
 }