At first glance through WebKits changes it appears as if theyve significantly crippled the keypress event, is this the case?
Yehuda: People should not have been using the keypress event to get the character that was pressed. That’s because the keydown event only provides information about the actual key that was pressed (the A key, the right arrow, etc.), but does not tell the user what character will get added to (for instance) an input box. Since arrow keys do not get added as text, keydown provides all the information that is needed. There were a couple of quirks with using keydown in certain cases previously which are resolved by their changes that prevent keypress from getting called if keydown’s default handling is blocked. What this means is that if people were using keypress before (and relying on Safari’s native results for arrow keys, such as 63232), their code will break. However, this was a bad idea all along; people should use keydown to detect and block non-character keys. My mantra has always been: keydown/keyup if you want to know the key that was pressed; keypress if you want to know what te
Related Questions
- After a few hours of incubation, the behaviour of my cells changes significantly and the amount of media is reduced. What can I do against this strong evaporation?
- At first glance through WebKits changes it appears as if theyve significantly crippled the keypress event, is this the case?
- Can Wexxar case/tray packaging machines be retrofitted with new product changes?
