TinyMCE: Remove container assignment hack#8465
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Related: #3091
Related: #3093
This pull request seeks to remove a workaround introduced to the TinyMCE component, targeted at resolving an error which could occur when a block changed the tag name of its rendered RichText (#3091). This has since been resolved in TinyMCE and therefore the workaround is no longer necessary. An end-to-end test has been implemented to protect against the original regression.
Testing instructions:
Verify that switching levels of the Heading block does not produce an error.
Ensure that end-to-end tests pass: