RESOLVED FIXED 32602
Correctly report keyLocation as DOM_KEY_LOCATION_NUMPAD for numeric pad arrow key events on Mac
https://bugs.webkit.org/show_bug.cgi?id=32602
Summary Correctly report keyLocation as DOM_KEY_LOCATION_NUMPAD for numeric pad arrow...
Kinuko Yasuda
Reported 2009-12-16 02:11:32 PST
There're no layout tests for Numpad arrow key events as current implementation of our eventSender does not support sending numpad key events. Related issue for chromium/gtk: https://bugs.webkit.org/show_bug.cgi?id=28247
Attachments
Support key location argument in keyboard event methods for EventSender. (13.36 KB, patch)
2009-12-25 06:04 PST, Kinuko Yasuda
no flags
Support key location argument in keyboard event methods for EventSender. (13.46 KB, patch)
2009-12-28 03:32 PST, Kinuko Yasuda
no flags
Kinuko Yasuda
Comment 1 2009-12-25 06:04:19 PST
Created attachment 45486 [details] Support key location argument in keyboard event methods for EventSender.
WebKit Review Bot
Comment 2 2009-12-25 06:05:10 PST
style-queue ran check-webkit-style on attachment 45486 [details] without any errors.
Darin Adler
Comment 3 2009-12-25 20:14:04 PST
It's strange to call this "add a layout test" since it also changes the behavior of the platform layer. Is that new platform-layer code for the benefit of the layout test only, or does it affect actual browser behavior too?
Maciej Stachowiak
Comment 4 2009-12-28 01:52:35 PST
Comment on attachment 45486 [details] Support key location argument in keyboard event methods for EventSender. Please update the WebCore and WebKit ChangeLog to explain the the apparent behavior change. If the test will only pass on some platforms, please add it to the skipped list on other platforms. Please also retitle the bug and its mention in the ChangeLog to cite the behavior change, not just the added tests. For example, "Correctly report keyLocation as DOM_KEY_LOCATION_NUMPAD for numeric pad arrow key events" would be a better explanation. r- to address these issues.
Kinuko Yasuda
Comment 5 2009-12-28 02:21:23 PST
(In reply to comment #3) > It's strange to call this "add a layout test" since it also changes the > behavior of the platform layer. Is that new platform-layer code for the benefit > of the layout test only, or does it affect actual browser behavior too? That's right, sorry for confusing things. I was trying to do a few different things in the patch - I've filed another bug (https://bugs.webkit.org/show_bug.cgi?id=32983) and updated the bug summary to reflect the things better. (In reply to comment #4) > For example, "Correctly report keyLocation as DOM_KEY_LOCATION_NUMPAD for > numeric pad arrow key events" would be a better explanation. I'm going to separate the patch and update the explanations in the ChangeLog. Thanks for reviewing,
Kinuko Yasuda
Comment 6 2009-12-28 03:05:35 PST
*** Bug 32983 has been marked as a duplicate of this bug. ***
Kinuko Yasuda
Comment 7 2009-12-28 03:12:47 PST
Updating the bug summary and have merged 32983 back to this one (sorry for the confusion). I'm updating the patch as well shortly.
Kinuko Yasuda
Comment 8 2009-12-28 03:32:30 PST
Created attachment 45550 [details] Support key location argument in keyboard event methods for EventSender.
WebKit Review Bot
Comment 9 2009-12-28 03:35:59 PST
style-queue ran check-webkit-style on attachment 45550 [details] without any errors.
Maciej Stachowiak
Comment 10 2009-12-28 18:28:13 PST
Comment on attachment 45550 [details] Support key location argument in keyboard event methods for EventSender. r=me
WebKit Commit Bot
Comment 11 2009-12-28 22:33:30 PST
Comment on attachment 45550 [details] Support key location argument in keyboard event methods for EventSender. Clearing flags on attachment: 45550 Committed r52608: <http://trac.webkit.org/changeset/52608>
WebKit Commit Bot
Comment 12 2009-12-28 22:33:36 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.