-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Prevent unnecessary content changes clearing redo actions #57028
Merged
dcalhoun
merged 3 commits into
trunk
from
fix/prevent-unnecessary-content-changes-clearing-redo-actions
Dec 14, 2023
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the specific line resulting in incorrectly clearing pending redo actions. Comparing a
RichTextData
instance (this.value
) against a string (contentWithoutRootTag
) never resulted in equality. Making the situation more complex is the fact that iOS and Android Aztec implementations behave differently when it comes to blur and selection events, which means this nuanced scenario only occurred on iOS.The rest of the added
toString
invocations separate from this line in the proposed changes are out of caution, not to address an explicitly observed issue. Transparently, it is unclear to me currently when/whereRichTextData
should be leverage and where Aztec's string-value-based communication might disrupt that by passing back a string. It could be that a better solution is to always leverageRichTextData
values in JavaScript and convert values received from Aztec from string toRichTextData
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear, the use of
toString
is fairly innocuous as bothString
andRichTextData
provide the method. So, regardless of which type is present, the method and comparison should succeed.If nothing else, we could use the proposed changes as a stopgap solution until we fully integrate the
RichTextData
type.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would be the best option for consistency. This way we'll ensure that
RichTextData
is the expected value of theRichText
component when used anywhere.In any case, I think there will still be some cases where we need to convert the value to a String. As an example, I noticed a couple of examples in RichText: pass value to store:
For reference, this is the implementation of
RichTextData.toString
:gutenberg/packages/rich-text/src/create.js
Lines 152 to 163 in 5cfdf66