[KeyboardEvent] Use DOM |code| rather than Windows-based key code

ui/events/keycodes/keyboard_code_conversion.h

Index: ui/events/keycodes/keyboard_code_conversion.h
diff --git a/ui/events/keycodes/keyboard_code_conversion.h b/ui/events/keycodes/keyboard_code_conversion.h
index 8b92ba16394eaaebd48ccbacd86bed3ec453bc99..832701e4033fba38156b73badae31d7658475202 100644
--- a/ui/events/keycodes/keyboard_code_conversion.h
+++ b/ui/events/keycodes/keyboard_code_conversion.h
@@ -15,7 +15,7 @@ namespace ui {
 enum class DomCode;
 enum class DomKey;
 
-// Helper functions to get the meaning of a Windows key code in a
+// Helper functions to get the meaning of a  DOM |code| in a
 // platform independent way. It supports control characters as well.
 // It assumes a US keyboard layout is used, so it may only be used when there
 // is no native event or no better way to get the character.
@@ -29,7 +29,7 @@ enum class DomKey;
 // character according to US keyboard layout definition. Preferably, such
 // events should be created using a full KeyEvent constructor, explicitly
 // specifying the character and DOM 3 values as well as the legacy VKEY.
-//
+
 // TODO(kpschoedel): replace remaining uses of the ...FromKeyCode() functions
 // and remove them, to avoid future creation of underspecified key events.
 // crbug.com/444045
@@ -92,7 +92,6 @@ NonLocatedToLocatedKeyboardCode(KeyboardCode key_code, DomCode dom_code);
 // determined from a physical scan code, for example when a key event was
 // generated synthetically by JavaScript with only a VKEY value supplied.
 EVENTS_BASE_EXPORT DomCode UsLayoutKeyboardCodeToDomCode(KeyboardCode key_code);
-
 }  // namespace ui
 
 #endif  // UI_EVENTS_KEYCODES_KEYBOARD_CODE_CONVERSION_H_