-
Notifications
You must be signed in to change notification settings - Fork 3.7k
mWeb - Incorrect navigation to confirm details page & discard changes popup briefly visible #67010
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
MarioExpensify
merged 3 commits into
Expensify:main
from
Krishna2323:krishna2323/issue/64107_2
Aug 4, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| type DiscardChangesConfirmationProps = { | ||
| getHasUnsavedChanges: () => boolean; | ||
| onCancel?: () => void; | ||
| }; | ||
|
|
||
| export default DiscardChangesConfirmationProps; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coming from #75014 BugZero checklist:
This PR caused a regression where users cannot discard unsaved changes in the description field on Android mWeb when using the browser back button.
Root Cause: The
onModalHidecallback added in this PR creates a race condition with theInteractionManager.runAfterInteractions()in theonConfirmhandler. The callback setsshouldNavigateBack.current = falseimmediately when the modal starts hiding, but the navigation logic is queued to run after animations complete. By the time the navigation logic executes, the flag has already been reset, causing an early return before navigation can occur.The Issue: When users confirm "Discard changes", the modal closes but they remain on the same page with their unsaved text still in the field.
Current Fix: The fix in #76492 addresses this by:
isConfirmedref to track whether user confirmed or cancelledshouldNavigateBack.currentwhen user cancelssetNavigationActionToMicrotaskQueue()to ensure proper execution timing