Room & Task - Text cursor is at the beginning of text when opening room description

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.25-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to a room.
3. Click on the room header.
4. Click Description.
5. Add a description and save it.
6. Click on the description field.

Expected Result:

The text cursor will be at the end of the text.

Actual Result:

The text cursor is at the beginning of the text.

This issue also happens in task description.

Workaround:

Unknown

Platforms:

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6583716_1724719137109.room.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @madmax330 (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[github-actions]

👋 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:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[puneetlath]

I'm demoting this as it doesn't seem worthy of blocking the deploy.

[Skalakid]

@puneetlath @IuliiaHerets I can't reproduce this issue on the latest staging:

Screen.Recording.2024-08-28.at.10.31.46.mov

[IuliiaHerets]

@Skalakid I can't reproduce on the latest build too

bandicam.2024-08-28.12-56-14-677.mp4

[IuliiaHerets]

@Skalakid The issue was reverted, QA team again can repro it, build - v9.0.31-12

Bug6597780_1725902364331.Description.mp4

[melvin-bot]

@madmax330 @dylanexpensify 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!

[Skalakid]

I can also reproduce it again. After testing the issue will be fixed by this PR inside the react-native-live-markdown library. Inside this PR I changed the way how often and in what way the input structure elements are being updated. Thanks to that the cursor position issues, when component just loads, are being fixed. Here we are bumping the library version in E/App

[melvin-bot]

@madmax330, @dylanexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[Skalakid]

Hey, the PR with the bump has been merged and I can't reproduce this issue now. Can you please verify this on your side, please?

Screen.Recording.2024-09-16.at.13.24.36.mov

[melvin-bot]

@madmax330, @dylanexpensify 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[dylanexpensify]

@IuliiaHerets can you confirm?

[IuliiaHerets]

@dylanexpensify Issue not reproducible now

20240918_195700.mp4

[melvin-bot]

@madmax330, @dylanexpensify Eep! 4 days overdue now. Issues have feelings too...