Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Rename onChange to onSomethingNotInTheSpecAlready
See original GitHub issueWe talked about not breaking expectations for an event that already exists. I think of our options, onValueChange was the best.
Issue Analytics
- State:
- Created 10 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Javascript select onchange='this.form.submit()' - Stack Overflow
My psychic debugging skills tell me that your submit button is named submit . Therefore, form.submit refers to the button rather than the...
Read more >onchange Event - W3Schools
The onchange event occurs when the value of an element has been changed. For radiobuttons and checkboxes, the onchange event occurs when the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
Top Related Hashnode Post
No results found
We shipped onChange so I’m closing this task out.
@yungsters I completely disagree. Our version of onChange is definitely what people want; it should just be named such that it is different from an event people already know.
That is, we’re not concerned with staying within the spec; we’re concerned with staying backwards-compatible with it. If we change onChange to behave differently, we’ve violated user expectations of how that event behaves, and it will be hard to earn that trust back.