-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Fix quoted text disappearing after edit #13536
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
eaad93b
Also replace the existing message so that we are comparing the same t…
stitesExpensify e42a721
DRY up filter code
stitesExpensify e1630c1
Merge branch 'main' of github.com:Expensify/App into stites-fixQuoteEdit
stitesExpensify d2f08c9
Merge branch 'main' of github.com:Expensify/App into stites-fixQuoteEdit
stitesExpensify 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 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
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.
@stitesExpensify coming from #13661, I don't believe this PR caused this original issue (because there's some issue with escaping spaces as well) but I am seeing that by passing HTML into

parser.replacewe're effectively treating the HTML like markdown, is that not correct?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.
Okay yes I can confirm, PR incoming
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 should resolve it: #13703
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 don't really understand the question TBH.
In this issue, the problem (at least I thought) was that we were comparing parsed HTML to unparsed HTML, so when the strings were the same it was failing because it was comparing
"to", which is why I parsed the original HTML so that we were comparing the same things.Looking at your screenshot, there are 3 different interpretations of the same HTML which seems super messy 😅 I think ideally we would want to just compare the
originalCommentHTMLto thehtmlForNewCommentbut even those are in different formats.