Workspace - If admin located at the end of the list select admin warning appears cut off

[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 #20687

Action Performed:

Precondition - Admin is located at the end of Workspace members list;
There are 8+ members in the Workspace;

1. Open http://staging.new.expensify.com/
2. Open Settings
3. Click "Workspaces"
4. Click on Workspace from the precondition
5. Click on "Members"
6. Click on Admin member at the bottom of the list

Expected Result:

The warning that appears is completely visible - "You cannot remove yourself or the workspace owner"

Actual Result:

The warning that appears is cut off at the bottom so user have to scroll the list down a bit

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

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

Bug6101512_Recording__700.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[trjExpensify]

Hm, I'm not sure if this is a bug. @shawnborton should the page "jump" up so the error is in view? It just looks like the scroll position was maintained to me.

[shawnborton]

Yeah, I don't think this is a bug, let's close.

[trjExpensify]

Thank yah, kindly!