Repository navigation
[Due for payment 2026-03-30] [$250] [BACK BUTTON] mWeb - Back navigation - Device back button doesn't close FAB menu #70951
Description
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.16-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: NA
Email or phone of affected tester (no customers): sintayewhaylu01@gmail.com
Issue reported by: Applause Internal Team
Device used: Samsung A16/ Chrome
App Component: Workspace Settings
Action Performed:
- Navigate to staging.new.expensify.com
- Go to the Workspace
- Click the FAB
- Press the device's Back button
Expected Result:
The FAB menu should close (slide down) when the device's Back button is pressed.
Actual Result:
The FAB does not close, and the background navigates back.
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
Bug6950603_1758370166015.Recording_20250920_142133.mp4
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~021973744114182108173
- Upwork Job ID: 1973744114182108173
- Last Price Increase: 2026-01-21
- Automatic offers:
- daledah | Contributor | 110196362
Issue Owner
Current Issue Owner: @mallenexpensifyMetadata
Metadata
Labels
Type
Projects
- Status
Activity
melvin-bot commentedon Sep 21, 2025
Triggered auto assignment to @abekkala (
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.melvin-bot commentedon Oct 2, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021973744114182108173
[-][BACK BUTTON] [HOLD on #59245] mWeb - Back navigation - Device back button doesn't close FAB menu[/-][+][$250] [BACK BUTTON] [HOLD on #59245] mWeb - Back navigation - Device back button doesn't close FAB menu[/+]119 remaining items
melvin-bot commentedon Mar 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.41-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-03-30. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 23, 2026
@jayeshmangwani The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
melvin-bot commentedon Mar 23, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)jayeshmangwani commentedon Mar 30, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: This was neither implemented nor considered initially, so it does not originate from any specific PR.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: Not CRITICAL
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue: https://github.com/Expensify/Expensify/issues/618060
Regression Test Proposal
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-3d6e-afad-df66-9dfbdaaaadf4jayeshmangwani commentedon Mar 30, 2026
@mallenexpensify, the initial PR #80314 caused a regression, so we had to raise a second PR #82977. Therefore, the payment will be reduced to half ($125).
mallenexpensify commentedon Mar 30, 2026
Payment Summary
Contributor: @daledah due $125 via NewDot
Contributor+: @jayeshmangwani due $125 via NewDot
^ Test case created
laurenreidexpensify commentedon Apr 15, 2026
New Expensify Approved: @jayeshmangwani $125
quinthar commentedon May 12, 2026
Approved $125 for @daledah