-
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
Web - Line breaks & Text from code editor do not appear correctly within chat #10086
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @ctkochan22 ( |
@ctkochan22 to fix this we should replace this line
with this {StyleUtils.convertToLTR(Str.htmlDecode(text))} because we map App/src/pages/home/report/ReportActionItemFragment.js Lines 99 to 104 in 151ec1a
this change start in this pr https://github.com/Expensify/App/pull/9834/files |
@ctkochan22 any updates here? |
The recommendation by @ahmdshrif looks good. Just making sure it doesn't conflict with the PR that introduced it |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
The user expects the text in chat preview to be exactly as copied.
Actual Result:
The text does not comply with the correct format for either case
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
Version Number: 1.1.86-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected] / Emilio98 or (Any email)
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
Bug5662750_PROD.mp4
Bug5662750_Code_editor_text_does_not_display_correctly.mp4
Bug5662750_Line_break_issue_in_chat_preview.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: