Fix RichText controls in 6.2.2 and 6.3 #2545
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
AnthonyLedesma
changed the title
AnthonyLedesma
changed the title
EvanHerman
approved these changes
Aug 7, 2023
Contributor
EvanHerman
left a comment
EvanHerman
left a comment
There was a problem hiding this comment.
Looks good on my end with 6.2.2 and 6.3! 👍
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
Rich text controls were not functional in 6.2.2 after changes were introduced in #2538.
Changes here allow for backward compatibility and also resolve 'selection state' bugs with the Rich Text controls. Now we can persist the text controls for the Rich Text captions as expected.
Screenshots
Types of changes
Backward compat.
How has this been tested?
Tested manually.
Acceptance criteria
Should resolve RichText issues in both 6.2.2 and 6.3.
Checklist: