We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi 👋
We were trying to use the Change Event on the PikadayInput Component et we were surprised to see the event triggered on data-down.
When debugging the issue, we can follow easily the stack trace down to these codes blocks:
ember-pikaday/src/modifiers/pikaday.js
Line 59 in 9a3fae6
ember-pikaday/vendor/pikaday.js
Line 832 in 9a3fae6
As the W3C Specs point out, the Change Event is to be triggered only on user conscious input (leaving a non-validated input, checking a radio button, selecting/changing the date of a date input, etc...). https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/change_event https://html.spec.whatwg.org/multipage/input.html#concept-input-apply
Is it a wrong use on your side of Pikaday's Api or rather on their implementation?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi 👋
We were trying to use the Change Event on the PikadayInput Component et we were surprised to see the event triggered on data-down.
When debugging the issue, we can follow easily the stack trace down to these codes blocks:
ember-pikaday/src/modifiers/pikaday.js
Line 59 in 9a3fae6
ember-pikaday/vendor/pikaday.js
Line 832 in 9a3fae6
As the W3C Specs point out, the Change Event is to be triggered only on user conscious input (leaving a non-validated input, checking a radio button, selecting/changing the date of a date input, etc...).
https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/change_event
https://html.spec.whatwg.org/multipage/input.html#concept-input-apply
Is it a wrong use on your side of Pikaday's Api or rather on their implementation?
The text was updated successfully, but these errors were encountered: