You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Web - Chat - Console error shows up when creating a new line on italic mark down #39265
Version Number: 1.4.58.0 Reproducible in staging?: Yes Reproducible in production?: No 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 Expensify/Expensify Issue URL: Issue reported by: Applause Internal Team Slack conversation:
Action Performed:
1.Go to staging.new.expensify.com/
2.Go to any chat
3.Enter _ text _ (without space)
4.Move the cursor to before the second _
5.Create a new line
Expected Result:
No console error
Actual Result:
The cursor moves to the beginning of the text. The new line is only revealed when pressing down key on keyboard. Console error also shows up
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
@anmurali FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
This is the exception. @thienlnam is this something a contributor can fix or do we need to take it internal? I am not totally sure.
cursorUtils.js:54 Uncaught TypeError: Failed to execute 'setStart' on 'Range': parameter 1 is not of type 'Node'.
at c (cursorUtils.js:54:19)
at p (parserUtils.js:156:5)
at m (parserUtils.js:183:9)
at MarkdownTextInput.web.js:147:24
at MarkdownTextInput.web.js:236:16
at Object.De (react-dom.production.min.js:54:317)
at Be (react-dom.production.min.js:54:471)
at react-dom.production.min.js:55:35
at Fr (react-dom.production.min.js:105:68)
at qr (react-dom.production.min.js:106:380)
This can be fixed externally, but might require changes in react-native-live-markdown repository. @BartoszGrajdek Is this something you're interested in taking, or do you want us to take it external here?
@anmurali@thienlnam this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
melvin-bot commentedon Mar 29, 2024
Triggered auto assignment to @amyevans (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Mar 29, 2024
Triggered auto assignment to @anmurali (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.github-actions commentedon Mar 29, 2024
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
m-natarajan commentedon Mar 29, 2024
We think this bug might be related to #vip-vsb
m-natarajan commentedon Mar 29, 2024
@anmurali FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
6 remaining items
anmurali commentedon Apr 9, 2024
This is the exception. @thienlnam is this something a contributor can fix or do we need to take it internal? I am not totally sure.
thienlnam commentedon Apr 9, 2024
This can be fixed externally, but might require changes in react-native-live-markdown repository. @BartoszGrajdek Is this something you're interested in taking, or do you want us to take it external here?
melvin-bot commentedon Apr 12, 2024
@anmurali @thienlnam this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
thienlnam commentedon Apr 16, 2024
Bump on this #39265 (comment) @BartoszGrajdek
anmurali commentedon Apr 30, 2024
Brought this to slack here
thienlnam commentedon May 8, 2024
This appears to be resolved, I can't reproduce it anymore
Screen.Recording.2024-05-08.at.12.25.34.PM.mov