[$125] mWeb - Chat - Keyboard remains opened when opening the "Flag as offensive" page.

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.97-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome
App Component: Chat Report View

Action Performed:

1. Open the staging.new.expensify.com website.
2. Open any chat where messages from another user can be found.
3. Open the keyboard if it´s not opened yet.
4. Long tap on any message from another user and select "Flag as offensive"
5. Check the keyboard behaviour when redirected to the "Flag as offensive" page.

Expected Result:

Keyboard should not be opened again when user is navigated to "Flag as offensive" page.

Actual Result:

Keyboard remains opened when flagging a comment as offensive and landing on a new page.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6740316_1739343065567.Flg.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021889826227174733114
• Upwork Job ID: 1889826227174733114
• Last Price Increase: 2025-02-12
• Automatic offers:
• twilight2294 | Contributor | 106148397

Issue Owner

Current Issue Owner: @twilight2294

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

[twilight2294]

Proposal

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

Keyboard remains opened when opening the "Flag as offensive" page

What is the root cause of that problem?

We are not dismissing the keyboard before navigating to the flag as offensive page:

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

Lines 642 to 644 in 5ddef34

	if (closePopover) {
	hideContextMenu(false, () => Navigation.navigate(ROUTES.FLAG_COMMENT.getRoute(reportID, reportAction?.reportActionID, activeRoute)));
	return;

This causes the keyboard to remain open

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

We need to dismiss the keyboard first before navigating like we did here:

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

Lines 265 to 268 in 5ddef34

	hideContextMenu(false, () => {
	KeyboardUtils.dismiss().then(() => {
	navigateToAndOpenChildReport(reportAction?.childReportID, reportAction, originalReportID);
	});

            if (closePopover) {
                hideContextMenu(false, () => {
                    KeyboardUtils.dismiss().then(() => {
                        Navigation.navigate(ROUTES.FLAG_COMMENT.getRoute(reportID, reportAction?.reportActionID, activeRoute));
                    })
                });
                return;
            }

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

N/A this is a simple bug of keyboard dismisal

What alternative solutions did you explore? (Optional)

[twisterdotcom]

Agree, weird. Going to make it $125 here though.

[melvin-bot]

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

[melvin-bot]

Upwork job price has been updated to $125

[melvin-bot]

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

[dangrous]

can take care of internal review on this one when ready

[twilight2294]

Agree, weird. Going to make it $125 here though.

@twisterdotcom any specific reason to lower the bounty, I guess the standard $250 would be fine here :))

Similar issues had the same bounty:

• [$250] Keyboard shows up briefly while switching to reaction emoji picker from context menu causing flickering #54813
• [Due for payment 2025-02-28] [$250] Keyboard opens with composer autofocused when modifying an expense and go back to the report #55485

So i guess $250 would be fine for this one too :))

[twisterdotcom]

I guess we don't really have a standardised approach here, but IMO this is a lower value thing for us to fix as it doesn't actually prevent the app from being used and it's not a common flow. Both of the above issues are far more common or important flows.

[getusha]

@twilight2294's proposal looks good to me. I think i've seen this issue before on a different page, @twilight2294 do you think you can find similar issue on other pages & fix it here to possibly raise the bounty? what do you think @twisterdotcom?

🎀 👀 🎀 C+ Reviewed.

[melvin-bot]

Triggered auto assignment to @carlosmiceli, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[melvin-bot]

📣 @twilight2294 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[twilight2294]

@twilight2294 do you think you can find similar issue on other pages & fix it here to possibly raise the bounty?

Yes works for me !!!, @twisterdotcom would it be okay to increase the bounty if we fix the issue on other pages?

[twisterdotcom]

Yes, absolutely. I will add a $125 bonus on after. Please keep me honest on that @getusha and @twilight2294 as we get there though.

[melvin-bot]

@carlosmiceli, @dangrous, @twisterdotcom, @getusha, @twilight2294 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[twilight2294]

Thanks @twisterdotcom , raising the PR today

[melvin-bot]

@carlosmiceli, @dangrous, @twisterdotcom, @getusha, @twilight2294 Whoops! This issue is 2 days overdue. Let's get this updated quick!

[carlosmiceli]

Not overdue, @twilight2294 has a PR up.

[melvin-bot]

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

[dangrous]

@getusha @twilight2294 how are we looking on the PR?

[twilight2294]

PR is here:

• Fix: Keyboard remains opened when opening the "Flag as offensive" page #57309

[twilight2294]

I only opened the PR for review 2 days back, sorry for the delay

[dangrous]

Cool, thank you! @getusha have you had a chance to review?