Normalize which using keyCode and charCode #502
Closed
+6
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is there a good reason why this isn't being done already?
keyandcharare mentioned in the code, butcharhas since been deprecated in the standard andkeyrelies on the browser to implement, leavingwhichas the only cross-browser solution for now. There doesn't seem to be a full-featured polyfill either that could be recommended as a substitute forkey-support.IE8 and older browsers don't support
which, but onlykeyCodeandcharCode, seeing as we have the synthetic events, normalizing behavior according to (old) standards should be better than pushing it onto the developer.I propose that this PR be closed and that this solution be used instead #607