[WIP] Fix strange behavior after a closing modal restores focus on the Editor #1142
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
|
Clicking into the editor after modal close appears to be firing events. Closing for now. |
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.
Closes #1134
Yet unaddressed problem: After programmatically restoring focus, the Draft.js editor somehow stops updating its SelectionState. Further clicks in the Editor do not emit change events. The visible caret and the internal SelectionState remains out of sync until a new EditorState is created. This may be a Draft.js bug.
If there is no workaround, we may have to either:
a. Disable the
shouldReturnFocusAfterCloseonreact-modalModals 馃槵b. Reimplement the
shouldReturnFocusAfterClosebehavior so it works with Draft.js 馃槵馃槵