Skip to content
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.

change event has different semantics than platform change on <input> elements #9

Closed
sjmiles opened this issue Jul 27, 2014 · 0 comments
Labels

Comments

@sjmiles
Copy link
Contributor

sjmiles commented Jul 27, 2014

From MDN: "The change event is fired for , , and <textarea> elements when a change to the element's value is committed by the user. Unlike the input event, the change event is not necessarily fired for each change to an element's value." https://developer.mozilla.org/en-US/docs/Web/Events/change We are firing change event specifically on each each change to the value. It's probably better if we can match the platform semantics.

@frankiefu frankiefu self-assigned this Jul 31, 2014
@frankiefu frankiefu added the p1 label Aug 15, 2014
frankiefu added a commit to googlearchive/paper-radio-button that referenced this issue Aug 25, 2014
interaction. Use `core-change` event for old behavior (fired when the
checked state changes).

Reference: googlearchive/paper-checkbox#9
frankiefu added a commit to googlearchive/paper-toggle-button that referenced this issue Aug 25, 2014
interaction. Use `core-change` event for old behavior (fired when the
checked state changes).

Reference: googlearchive/paper-checkbox#9
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants