Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(347)

Unified Diff: third_party/WebKit/Source/core/events/KeyboardEvent.cpp

Issue 2855613002: Removed |which| from KeyboardEvent and MouseEvent. (Closed)
Patch Set: Created 3 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/Source/core/events/KeyboardEvent.cpp
diff --git a/third_party/WebKit/Source/core/events/KeyboardEvent.cpp b/third_party/WebKit/Source/core/events/KeyboardEvent.cpp
index 53acf615e91e2cab349528d1430182ff7f3c83a7..440db4242406d4478ccf6a3d4698d7827ac57417 100644
--- a/third_party/WebKit/Source/core/events/KeyboardEvent.cpp
+++ b/third_party/WebKit/Source/core/events/KeyboardEvent.cpp
@@ -187,11 +187,11 @@ bool KeyboardEvent::IsKeyboardEvent() const {
return true;
}
-int KeyboardEvent::which() const {
+unsigned KeyboardEvent::which() const {
// Netscape's "which" returns a virtual key code for keydown and keyup, and a
// character code for keypress. That's exactly what IE's "keyCode" returns.
// So they are the same for keyboard events.
- return keyCode();
+ return (unsigned)keyCode();
}
void KeyboardEvent::InitLocationModifiers(unsigned location) {

Powered by Google App Engine
This is Rietveld 408576698