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.
State sometimes change twice after one change
See original GitHub issueDo you want to request a feature or report a bug?
BUG
What’s the current behavior?
https://jsfiddle.net/31tb8gyx/30/
Select some text and click bold button, and you will see the onChange event fired twice, and as a result, the history state of editor is undesierable.
This issue happens only when call e.preventDefault in onMouseDown handler, but without e.preventDefault, the editor would blur and user could not continue editing, which is also too bad.
- OS: MacOS
- Browser: Chrome
- Slate: 0.28.2
What’s the expected behavior?
No twice state change, no unnecessary rerender, the history state should be clean.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@chemzqm I’m still not clear on what you are talking about. If you change the
undohandler to beonMouseDown, then there’s no issue with undoing.@isubastiCadmus sounds like it’s definitely possible, I’d accept a PR that fixes that checking logic.