Reset TinyMCE state in live DOM after blur #10721
Closed
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
aduth
reviewed
Oct 23, 2018
There was a problem hiding this comment.
Given that blur doesn't necessarily mean it's left the element (since it bubbles, vs. focusout), is there any chance a blur could occur within the field to produce an undesirable result?
Similarly, what about when a user navigates to/from a toolbar or link insertion/editing?
|
Original issue seems to be resolved. |
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.
Description
Fixes #8877.
This is an alternative approach to #8879. With the new RichText value, we can simply overwrite the live DOM on blur so that any TinyMCE is removed.
How has this been tested?
See #8877.
Screenshots
Types of changes
Checklist: