P
PaulB
Guest
This issue has returned within the past week or two.
The Chrome team's stance is that keyboard events shouldn't be sending the specific key that the user pressed. Their explanation makes sense, and they've made it clear they have no intention of changing this behavior. Instead, they just send key code 229 (
I suspect Froala isn't handling this gracefully. If I hook up a physical keyboard to...
Read more
Continue reading...
The Chrome team's stance is that keyboard events shouldn't be sending the specific key that the user pressed. Their explanation makes sense, and they've made it clear they have no intention of changing this behavior. Instead, they just send key code 229 (
IME
). They may send a normal key code at times, but this shouldn't be relied upon.I suspect Froala isn't handling this gracefully. If I hook up a physical keyboard to...
Read more
Continue reading...