ControlledEditor doesn't fire onChange upon Undo/Redo
See original GitHub issueUndo and redo typically change the contents of a ControlledEditor
but onChange
doesn’t fire. I see the code has an explicit check that prevents this which was added in 2.3.0, but it’s not clear why. Undo and redo can change the content of the editor just like any other operation, so onChange
should fire.
Issue Analytics
- State:
- Created 4 years ago
- Comments:21 (7 by maintainers)
Top Results From Across the Web
onchange wont fire after programmatically changing html ...
My problem, as I've read through other stack posts is that programmatically updating the value wont trigger onChange, thus I need to call ......
Read more >SCR19: Using an onchange event on a select element ... - W3C
The objective of this technique is to demonstrate how to correctly use an onchange event with a select element to update other elements...
Read more >The attribute for input tag"onchange" will not fire, but ...
onchange is only triggered when the control is out of focus. That means you have to click outside of the input field after...
Read more >How can I trigger an onchange event manually in javascript?
How can I trigger an onchange event manually in javascript? - You can dispatch events on individual elements using the dispatchEvent method.
Read more >input file'' onchange react - Industry Today
How do you show form input fields based on select value in React? www gob mx ... so the onChange doesnt fire, but...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome 🎉 🎉 happy to help 😃
@patrickshipe @seraph0x @RickeyWard @SivaKranthiKumar @jdroigk @jpeterson @travisdahl @rosslovas hello everyone 🙂
The problem is solved. A check has been missed during rewriting. Let’s thank @patrickshipe for a great catch.
The new version (v3.4.2) has already published 🎉 If it’s possible, please check it.
Thank you all for your support!