Removed |which| from KeyboardEvent and MouseEvent.

third_party/WebKit/Source/core/events/UIEvent.idl

Index: third_party/WebKit/Source/core/events/UIEvent.idl
diff --git a/third_party/WebKit/Source/core/events/UIEvent.idl b/third_party/WebKit/Source/core/events/UIEvent.idl
index bbf6c4712950e1cae60146dbb2872efc755efca1..c54b901127dcf25b2ea2bf42eed7ffc8d7cc6382 100644
--- a/third_party/WebKit/Source/core/events/UIEvent.idl
+++ b/third_party/WebKit/Source/core/events/UIEvent.idl
@@ -35,5 +35,5 @@
                                [Default=Undefined] optional long detail);
 
     // FIXME: this belongs on the KeyboardEvent interface
-    [MeasureAs=UIEventWhich] readonly attribute long which;
+    [MeasureAs=UIEventWhich] readonly attribute unsigned long which;

[dtapuska, 2017/05/09 21:20:53]

Do we anticipate any issues with changing this from a long to an unsigned long?

[use mustaq_at_chromium.org, 2017/05/10 17:48:35]

Not really:
- For MouseEvent, which() currently returns non-zero positive integers.
- For KeyboardEvent, the returned values can be traced back to 16bit unsigned
values (Source/platform/KeyboardCodes.h or WebKeyboard.text[0]). Moreover, FF
already has "unsigned" as per the spec.

 };