-
Notifications
You must be signed in to change notification settings - Fork 28
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
onchange or ontypechange? #22
Comments
We should really dump that what's new section: it's just badly duplicating what the commit history is for. |
(and confusing people in the process, clearly :) ) |
Btw, the authoritative stuff is always whatever is in the WebIDL. |
marcoscaceres
pushed a commit
that referenced
this issue
Nov 12, 2014
Removed What's New section (closes #22)
marcoscaceres
pushed a commit
that referenced
this issue
Nov 17, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The "what's new" section says onchange has been renamed to ontypechange. Later in the spec it's referred to as onchange. That appears to be a recent change. Which is it? Note that Chromium has already released with ontypechange months ago.
The text was updated successfully, but these errors were encountered: