[$250] Chat - Size of text cursor is smaller when returning to any chat via browser back button

[lanitochka17]

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: 1.4.58-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to FAB > Start chat
3. Create a group chat
4. Split bill in the group chat
5. Click on the split preview > Click any split member > Click Message
6. In 1:1 DM, click on the IOU preview
7. Click on the header subtitle to return to 1:1 DM
8. Click browser back button until app returns to the group chat in Step 3

Expected Result:

The size of text cursor will remain the same when returning to group chat via browser back button

Actual Result:

The size of text cursor is smaller when returning to group chat via browser back button

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Add any screenshot/video evidence

Bug6432037_1711744193996.20240330_042506.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01e868dd4a424eb130
• Upwork Job ID: 1776300146755960832
• Last Price Increase: 2024-04-05
• Automatic offers:
• paultsimura | Reviewer | 0

[melvin-bot]

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

[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.

[lanitochka17]

We think that this bug might be related to #vip-vsp

[lanitochka17]

@marcaaron 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

[marcaaron]

Seems possibly more related to markdown changes.

[marcaaron]

@thienlnam I asked for a re-test to see. It kinda feels like this would be broken everywhere (sorry if I end up wrong on that hunch).

[thienlnam]

Definitely possible - I'll add it to the main tracking list. But seems pretty harmless and I don't think needs to be a blocker

[marcaaron]

Cool. If you are not passionate about it. Then I'm gonna pop the label off.

[melvin-bot]

Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[marcaaron]

p.s. confirmed with QA that this is not limited to Group Chats.

[dylanexpensify]

@quinthar heads up, I added this to vip-vsb, but with LOW given it's lack of impact on usability. LMK if you disagree!

[nkdengineer]

@BartoszGrajdek @paultsimura this PR is ready for preview.

[melvin-bot]

@paultsimura @thienlnam @dylanexpensify @nkdengineer this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[dylanexpensify]

PR is merged Mel! Waiting for payment day

[paultsimura]

Waiting for payment day

I believe we still need a PR to bump the react-native-live-markdown version in the App, right @nkdengineer?

[dylanexpensify]

Ah nice, thanks @paultsimura! 👍

[nkdengineer]

@paultsimura this PR is ready for preview.

[paultsimura]

This was deployed to production on April 22, due payment 2024-04-29

[dylanexpensify]

Payment summary:

• Contributor: @nkdengineer $500
• Contributor+: @paultsimura $500

Please apply or request!

[BartoszGrajdek]

Hi! Can we get this issue closed? 😄 I'm trying to clean up the Live Markdown tracking issue right now :)

[thienlnam]

We don't close issues until we get them paid out - but we can remove this from the tracking issue

EDIT: I went ahead and cleaned up the main tracking issue here #36071

[dylanexpensify]

bump @nkdengineer!

[nkdengineer]

Hi @dylanexpensify, sorry for the delay, I've applied to the job https://www.upwork.com/jobs/~01e868dd4a424eb130

[dylanexpensify]

no worries, thanks!!

[dylanexpensify]

offer sent!

[nkdengineer]

Hi @dylanexpensify, this issue was created on Mar 30, and according to this announcement, issues created prior to the announcement date Apr 4 will remain the original price ($500).

If that's correct, could you help update the GH title and offers, thanks 🙇

[paultsimura]

@dylanexpensify in addition to @nkdengineer's comment above, it was quite a complex task involving an upstream fix in the Live Markdown package, so that note makes sense to me. WDYT?

[dylanexpensify]

Ah, thanks for the catch, agree. Updated offer, and will pay out $500 in Upwork

[paultsimura]

I've just applied for the job as well, thanks.

[dylanexpensify]

sounds great!

[paultsimura]

@dylanexpensify what's the payout plan on this? The payment day was a month ago, 2024-04-29

[dylanexpensify]

@paultsimura paid last week! But just sent bonus along!

[dylanexpensify]

@nkdengineer waiting for you to accept offer!

[nkdengineer]

@dylanexpensify I accepted the offer. But the offer was for $250 so I guess a bonus of $250 will be sent too.

Thanks 🙇

[dylanexpensify]

Correct! all done btw