- From: <bugzilla@jessica.w3.org>
- Date: Tue, 05 Feb 2013 06:44:21 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18867 --- Comment #4 from Egor Khalimonenko <termi1uc1@gmail.com> --- I don't understand the desire to bring the same value to "key" and "char" properties. And I don't understand the desire to make our (js-developers) work harder. What are good reasons to modify "key" value when one of modifier key pressed? We have crtlKey, shiftKey and altKey for that. We have "char" property for the original input symbol. So why I need to write extra code to detect to key I need, while I have good-old "keyCode" value. So instead use the new API, I will continue to use the old one. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 5 February 2013 06:44:25 UTC