New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove event.which property fill
#3235
Comments
4 tasks
8 tasks
mgol
added a commit
to mgol/jquery
that referenced
this issue
Jul 29, 2020
All supported browsers implement this property by themselves. The shim was only needed for IE <9. Fixes jquerygh-3235 Ref jquerygh-4755
|
PR: #4765 |
|
Why is this marked as a behavior change if all the browsers already support it? |
|
@dmethvin Sorry, I didn't notice this issue & your assignment before I made the PR. I reassigned the issue to myself. |
|
@mgol No problem, thanks for doing it! Should just be a case of deleting the |
mgol
added a commit
that referenced
this issue
Aug 26, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IE8 seems to be the last browser that didn't provide this natively. It's a bit tricky to test because it needs a real event and not a simulated one.
#3233 (comment)
See also gh-2337, if we're not filling the property and just passing it on I don't know that we need to formally deprecate it in jQuery or generate a Migrate warning. If browsers ever tried to deprecate it via a console warning, the pass-through we do when copying the property would be the responsibility of the caller. If anything I'd say we add a note in our docs to use
event.buttonorevent.buttonswhere possible.The text was updated successfully, but these errors were encountered: