Fix for #1376. Up to date history stack on 'editor change' #1906
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…en 'editor-change' events are fired.
|
Sorry for the delay -- thanks for the fix! |
|
No problem, thanks for merging and for a very nice editor! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for #1376 undo the first time,but the history.stack.redo.length = 0?
The destination stack is currently updated after any
editor-changeevents. This makes it hard to e.g. reactively enable/disable undo redo buttons. With this change, the stack is updated first, and the quill contents and selection is updated after, ensuring that the stack is up to date when any events are fired.