[C+ Checklist Needs Completion] [$250] "Mark as unread" popup is very hard to toggle when using it on the first chat in list

[mitarachim]

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: v9.2.9-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): applausetester+en@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Macbook Pro 2023 / Sequoia 15.2
App Component: Chat Report View

Action Performed:

Precond: User has a lot of chats in the list

1. Access New Expensify Desktop app and sign into a valid account
2. Right click on the first chat of the list (The popup will show at the top of the page)
3. Try to toggle the "Mark as unread/read" button

Expected Result:

User can toggle the button with ease

Actual Result:

The button is very hard to toggle, only when you get to the third chat in the list does it work normally

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug6941090_1757560464784.Mark_as_unread_is_very_hard_to_click.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021967615992722225358
• Upwork Job ID: 1967615992722225358
• Last Price Increase: 2025-09-22

Issue Owner

Current Issue Owner: @greg-schroeder

[melvin-bot]

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

[Eskalifer1]

Proposal

Please re-state the problem that we are trying to solve in this issue.

"Mark as unread" popup is very hard to toggle when using it on the first chat in list

What is the root cause of that problem?

This happens because the upper part of the application is defined with the dragArea attribute, which allows you to drag the application with the mouse on the desktop, and all elements in this area are not clickable.

The part with “Inbox” has this parameter set to true. Therefore, regardless of the index, all elements above or below the element with this tag will not be clickable.

App/src/components/Navigation/TopBar.tsx

Line 39 in 5cd9a99

dataSet={{dragArea: true}}

What changes do you think we should make in order to solve the problem?

We need to add the parameter dataDragArea: false for this menu:

dataSet={{dragArea: false}}

App/src/pages/home/report/ContextMenu/BaseReportActionContextMenu.tsx

Lines 339 to 342 in b12e658

	<View
	ref={contentRef}
	style={wrapperStyle}
	>

PS: we can only add this for certain menu items, not for the entire menu, if necessary

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

What alternative solutions did you explore? (Optional)

We can remove dragArea: true from the Inbox section if necessary, but I don't think that's a good solution
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[bernhardoj]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Mark as unread is not clickable.

What is the root cause of that problem?

This is the same issue as #44928 which is already fixed before in PopoverWithoutOverlay component. But in this case, the context menu now uses a Modal component which doesn't have the fix yet.

The root cause is explained here, but in short, the draggable area becomes not clickable and the mark as unread is within that area.

What changes do you think we should make in order to solve the problem?

We need to add dataSet={{dragArea: false}} to the modal.

App/src/components/Modal/BaseModal.tsx

Lines 426 to 429 in b12e658

	<ModalComponent
	// Prevent the parent element to capture a click. This is useful when the modal component is put inside a pressable.
	onClick={(e) => e.stopPropagation()}
	onBackdropPress={handleBackdropPress}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021967615992722225358

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 (External)

[ahmedGaber93]

Reviewing today