[$500] mWeb - Compose Box - The magnifying glass moves up when words are highlighted

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 1.3.93-0
Reproducible in staging?: Y
Reproducible in production?: N
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:

Issue found when executing PR #29434

Action Performed:

1. Open https://staging.new.expensify.com/
2. Log in with an expensifail account
3. Open any chat and paste an RTL text in the compose box, for example " مثال "
4. Write any word in English, for example, "Hello."
5. Highlight the word "Hello" and move the selection cursor all the way to the left to fully highlight the word "مثال" at the same time

Expected Result:

When English and Arabic words are highlighted at the same time, the magnifying glass should magnify the highlighted text and not move across the screen beyond the text

Actual Result:

When English and Arabic words are highlighted at the same time, the magnifying glass moves upward

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

Android: Native

Android: mWeb Chrome

Bug6256904_1698678666678.Record_2023-10-30-19-33-09.mp4

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~015947874fc7315d53
• Upwork Job ID: 1721635785637269504
• Last Price Increase: 2023-11-20

[melvin-bot]

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

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[OSBotify]

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

Triggered auto assignment to @srikarparsi (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[HardikChoudhary24]

I believe this behaviour is occurring due to the concatenation of the LTR marker \u2066 with the text containing RTL characters . This issue doesn't arise when we only enter LTR characters as we are not adding the LTR marker in this case. I'm unsure about how to fix this, as the LTR marker is necessary to ensure that RTL text renders from left to right.

[srikarparsi]

Messaged @neil-marcellini about it since it seems to be from this PR