-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2023-06-01] [$1000] Web - Chat - In offline mode, on deleting any latest message, if last message has & sign in it, app displays it as & in LHN #17658
Comments
Triggered auto assignment to @anmurali ( |
Bug0 Triage Checklist (Main S/O)
|
Reproduced |
Job added to Upwork: https://www.upwork.com/jobs/~01206f24c549758b9a |
Current assignee @anmurali is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt ( |
Triggered auto assignment to @youssef-lr ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.In offline mode, on deleting any latest message, if last message has & sign in it, app displays it as & in LHN What is the root cause of that problem?This is caused because there is a bug in But when we are doing reverse html to string we are not unescaping it: This is also visible when we add new comment. In optimistic data, we are generating this: When we delete and generate optimistic data, we are using App/src/libs/ReportActionsUtils.js Line 160 in dd827e9
and since it is offline it is keeping optimistic data and showing its value. What changes do you think we should make in order to solve the problem?We should update What alternative solutions did you explore? (Optional) |
@alitoshmatov Thanks for the proposal. The RCA is correct. The fix is almost correct. We should call 🎀 👀 🎀 C+ reviewed cc @youssef-lr |
Proposal looks to be working. However, I was curious about what we do differently when setting the report's Also, for this solution to work, we also need to update this line to use What do you think @s77rt? |
@youssef-lr I agree with you. I am confused as when to use I also didn't understand why they didn't use |
@youssef-lr There have been a number of bugs related to html <-> text encoding and by the looks of it we are not exactly done with those 😅 so I'm not sure why we are using both
I think we should fix still fix
I don't think this is necessary. I think you based this assumption on this line but this piece of code is actually misleading. We should either: 1. Get HTML -> Decode it - OR - 2. Get TEXT (and use it directly). So in that case we should not have bothered calling That point ^ actually raises another concern, in Sorry for the lengthy comment. Here is the plan:
What do you think? cc @pecanoro as you worked on similar bugs before. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Even removing |
Are you sure, because I tested it and confirmed. Previously Further |
@therealsujitk |
Even if you test it with that, it first get's escaped in the |
You can test it by commenting the |
@alitoshmatov @s77rt do we need a follow up PR to fix the regression? |
We have this #20443. |
Not overdue. |
@youssef-lr, @anmurali, @s77rt, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Not overdue. This is on hold for payment (Jun 23rd same as #19789) |
#19789 is closed, and this one is ready to proceed. |
@pecanoro Another friendly bump |
Payments:
|
Hi @s77rt, I think you meant @dhanashree-sawant 😅 |
Oops my bad. Sorry @dhairyasenjaliya for the false positive 😅 |
No issue all good 😁 |
Hi @anmurali, Thanks! Offer accepted. |
Accepted |
@youssef-lr, @anmurali, @s77rt, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Same here |
@anmurali Can you approve the offers, please? 🤗 |
Everyone's been paid. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
App should not convert
&
to&
; in offline mode in LHNActual Result:
App converts
&
to&
; in offline mode in LHN if we delete the message after itWorkaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.1.3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Recording.2520.mp4
and.sign.displayed.wrong.in.LHN.in.offline.mode.mp4
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681808180603719
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: