@BrendanEich when MDN says you should avoid using evt.keyCode (in favor of evt.code except NOT ALL BROWSERS SUPPORT IT), are they suggesting that one day keyCode will suddenly be broken? I thought the web was supposed to be "backwards compatible?"
-
-
Replying to @patrick99e99
I’m not involved in MDN. Ccing
@bz_moz in case he has a thought.1 reply 0 retweets 1 like -
Replying to @BrendanEich @patrick99e99
.keyCode was _always_ broken, as in returning different values in different browsers; no "suddenly" about it. The reason to use .key if it exists is that .key is actually specified sanely and likely to be interoperable across browsers. .keyCode is not and won't be.
1 reply 0 retweets 1 like -
To quote the UI events spec: "In practice, keyCode and charCode are inconsistent across platforms and even the same implementation on different operating systems or using different localizations. ...."
1 reply 0 retweets 0 likes
"... This specification does not define values for either keyCode or charCode, or behavior for charCode. In conforming UI Events implementations, content authors can instead use key and code."
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.