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

• Status: RESOLVED
• Resolution: FIXED
• Component: WebCore Misc.

[marcos ojeda]

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

[marcos ojeda]

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

[Alexey Proskuryakov]

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]

<rdar://problem/7877716>

[Alexey Proskuryakov]

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

[Alexey Proskuryakov]

Created attachment 53913 [details]
proposed fix

[Alexey Proskuryakov]

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

[Simon Fraser (smfr)]

This caused bug 41016.