Bug 37776

Summary:

REGRESSION: When using dvorak, keydown/keyup reports qwerty keyCodes

Product:

WebKit

Reporter:

marcos ojeda <subliminal>

Component:

WebCore Misc.

Assignee:

Alexey Proskuryakov <ap>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

ap, simon.fraser

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

Mac (Intel)

OS:

OS X 10.6

Attachments:

Description	Flags
A webpage that exhibits and logs this behavior on keyup.	none
proposed fix	darin: review+

marcos ojeda

Reported 2010-04-18 13:52:17 PDT

The other day when i was browsing ffffound, i noticed that pushing the C key (maps to J) to navigate down no longer worked. I assumed this was a webpage error, until i realized that pushing the actual J key caused the navigation to work again. I made an html page, which i am attaching, that adds an a keyup event to document and reports the event.keyCode and Sting.fromCharCode(event.keyCode) so you can see what i mean. Neither Safari, Chrome or Firefox have this problem, only webkit nightlies. So, again, the error is that when i push the F key on my keyboard on the attached page, webkit reports that i pushed F while every other browser reports (correctly) that i pushed U. Hope that helps, it's my first bug report, but i tried to make something to easily test this. best, --marcos

Attachments
A webpage that exhibits and logs this behavior on keyup. (654 bytes, text/html) 2010-04-18 13:53 PDT, marcos ojeda	no flags	Details
proposed fix (6.50 KB, patch) 2010-04-20 20:45 PDT, Alexey Proskuryakov	darin: review+	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.

marcos ojeda

Comment 1 2010-04-18 13:53:29 PDT

Created attachment 53632 [details] A webpage that exhibits and logs this behavior on keyup.

Alexey Proskuryakov

Comment 2 2010-04-18 15:00:44 PDT

This is a result of fixing bug 36616. We need to find a way to make both work, although I'm not yet sure how.

Alexey Proskuryakov

Comment 3 2010-04-18 15:01:17 PDT

<rdar://problem/7877716>

Alexey Proskuryakov

Comment 4 2010-04-18 15:15:25 PDT

Actually, it seems that IE remaps keycodes for (most?all?) Roman keyboards. So, we have the same problem with AZERTY, for example.

Alexey Proskuryakov

Comment 5 2010-04-20 20:45:31 PDT

Created attachment 53913 [details] proposed fix

Alexey Proskuryakov

Comment 6 2010-04-20 21:55:35 PDT

Committed <http://trac.webkit.org/changeset/57951>.

Simon Fraser (smfr)

Comment 7 2010-06-22 15:47:43 PDT

This caused bug 41016.

Note You need to log in before you can comment on or make changes to this bug.