-
Notifications
You must be signed in to change notification settings - Fork 3k
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
mWeb - Conversation - Edited comment doesn't appear greyed out #10766
Comments
Triggered auto assignment to @techievivek ( |
Just tested this on my phone and it seems to work! Maybe this is specific to a browser/platform: WhatsApp.Video.2022-09-02.at.10.22.07.AM.mp4 |
@PauloGasparSv I agree with you, I don't know why it didn't listen for the offline event. Please feel free to assign yourself to it if you want to work on it otherwise I will apply the |
@techievivek I'm not sure if that's a bug 😄 |
I am down with a fever today, I will check it tomorrow once I come online. Thanks |
I tested this locally and doesn't seem like it's an issue. Also, as @PauloGasparSv mentioned this is something particular to the emulator so I am closing this one for now. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Issue found when executing PR #9532
Action Performed:
and login with any account
Comment:
Issue reproduced occasionally
Expected Result:
The edited comment appears greyed out.
Actual Result:
The edited comment doesn't appear greyed out.
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.96.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug5713767_Record_2022-09-01-18-22-42.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: