[HOLD #23088 Safari-only] iOS - Truncation dots ... doesn’t appear after the word Line 2

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

---

Issue found when executing PR #22777

Action Performed:

1. Login to any account and open the FAB menu by pressing + icon.
2. Click Assign task.
3. Enter a title and the following description:
   Line 1
   Line 2
   Line 3

Expected Result:

Verify that truncation dots ... appear after the word Line 2

Actual Result:

Truncation dots ... doesn’t appear after the word Line 2

Workaround:

Unknown

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.42.17

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6132752_RPReplay_Final1689702132.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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

[allroundexperts]

This is not a bug. Rather, this is the native behaviour on iOS!

[melvin-bot]

@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...

[mallenexpensify]

iOS app isn't loading for me :( I was able to test on Safari and got the three dots, the only way I could do was by pasting though, if I tapped Return, it went to the next screen vs the next line.

This is not a bug. Rather, this is the native behaviour on iOS!

@aimane-chnaif , do you know why iOS is different for Safari and native app?

[aimane-chnaif]

@aimane-chnaif , do you know why iOS is different for Safari and native app?

mSafari is web and it's rendered with html tags, while text view on iOS native is rendered with native view (i.e. UILabel, UITextView).

As this happens only on iOS native, I think it's worthy of fixing. Most likely upstream issue.
If you agree, I am happy to help this issue as C+.

[melvin-bot]

@mallenexpensify Eep! 4 days overdue now. Issues have feelings too...

[mallenexpensify]

Added this to the below and putting on hold

• [Tracking] Safari-only bugs in NewDot #23088

[mallenexpensify]

Still on hold, might raise a 'safari-only' discussion soon-ish

[mallenexpensify]

Safari-only bug, on hold

[mallenexpensify]

Still on hold

• [Tracking] Safari-only bugs in NewDot #23088

[mallenexpensify]

still on hold..

[mallenexpensify]

Still held

[mallenexpensify]

Safari-only hold

[mallenexpensify]

Still held on safari-only...

[mallenexpensify]

Safari-only

[mallenexpensify]

Addressed today in #bug-zero internally.

[mallenexpensify]

Per internal discussion here, I'm going to close the safari-only issues and keep the tracking issue open. If/when we decide to work on these, we'll reopen them.