[Awaiting checklist completion] Members - Cursor is not disabled when hovered over Select all checkbox

[nlemma]

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: 9.2.97-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #77776
Email or phone of affected tester (no customers): sdsoidjnosnjdsodsjno@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new workspace.
3. Go to workspace settings > Members.
4. Hover over Select all checkbox.

Expected Result:

Cursor will appear disabled when hovered over Select all checkbox when there is only group admin.

Actual Result:

Cursor is not disabled and appears as a hand when hovered over Select all checkbox when there is only group admin.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7044728_1767983974049.4.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dukenv0307

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #77776

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[melvin-bot]

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

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #77776 - "Make SelectionListWithModal use new SelectionList" by @zfurtak (High confidence)
Related Issues: None found

Recommendation: REVERT

This PR migrated multiple pages (including WorkspaceMembersPage) to use the new SelectionList component, but introduced a regression in the "Select all" checkbox disabled state handling.

📋 Detailed Analysis

Evidence

1. The issue is staging-only (not reproducible on production), and PR Make SelectionListWithModal use new SelectionList #77776 is on the current staging deploy checklist
2. PR Make SelectionListWithModal use new SelectionList #77776 migrated WorkspaceMembersPage to use the new SelectionList/SelectionListWithModal
3. The issue specifically occurs in workspace members settings, which is one of the pages migrated in this PR

Root Cause

The bug occurs when there is only one member in a workspace (the group admin):

In WorkspaceMembersPage.tsx (line 388):

isDisabledCheckbox: !(isPolicyAdmin && accountID !== policy?.ownerAccountID && accountID !== session?.accountID)

When there is only the admin, all members have isDisabledCheckbox: true (they cannot be selected).

In BaseSelectionList.tsx (lines 117-144):
The dataDetails calculation only adds items to disabledIndexes when item.isDisabled is true, but NOT when item.isDisabledCheckbox is true:

const isItemDisabled = isDisabled || (!!item?.isDisabled && !isItemSelected(item));
if (isItemDisabled) {
    acc.disabledIndexes.push(idx);
}
const totalSelectable = data.length - disabledIndexes.length;

In ListHeader.tsx (line 51):

const allDisabled = dataDetails.data.length === dataDetails.disabledIndexes.length;

Since items with isDisabledCheckbox: true are not counted in disabledIndexes, the "Select all" checkbox is not marked as disabled, even though no items can be selected. This causes the Checkbox component to not apply the styles.cursorDisabled style, resulting in a hand cursor instead of a disabled cursor.

Why Revert?

• Clean migration PR that can be reverted without conflicts
• The regression affects a core UX pattern across multiple workspace pages
• A revert allows time to properly fix the SelectionList logic to handle isDisabledCheckbox correctly