fix: review

Author: MrMuzyk

src/components/Modal/internalPopstateGuard.ts

@@ -1,9 +1,11 @@
 let isInternal = false;
 
+/** Returns true when the next `popstate` was triggered by our own `history.back()`, not a real user back navigation. */
 function isInternalPopstateInProgress(): boolean {
     return isInternal;
 }
 
+/** Runs `action` (e.g. `history.back()`) while flagging the resulting `popstate` as internal, so listeners can ignore it. */
 function withInternalPopstate(action: () => void) {
     isInternal = true;
     const clear = () => {

src/libs/Navigation/AppNavigator/ModalStackNavigators/index.tsx

@@ -65,7 +65,6 @@ const loadAttachmentModalScreen = () => require<ReactComponentModule>('../../../
 
 type Screens = Partial<Record<Screen, () => React.ComponentType>>;
 
-// Reimbursement Account flow animations glitch on low-end Android devices in Chrome mWeb https://github.com/Expensify/App/issues/87658 so we intentionally disable them
 const IS_MOBILE_CHROME = isMobileChrome();
 
 const REIMBURSEMENT_ACCOUNT_FLOW_SCREENS: Screen[] = [
@@ -143,6 +142,8 @@ const OPTIONS_PER_SCREEN: Partial<Record<Screen, PlatformStackNavigationOptions>
     [SCREENS.TWO_FACTOR_AUTH.SUCCESS]: {
         animationTypeForReplace: 'push',
     },
+    // Reimbursement Account flow animations glitch on low-end Android devices in Chrome mWeb so we intentionally disable them here.
+    // see https://github.com/Expensify/App/issues/87658
     ...(IS_MOBILE_CHROME ? Object.fromEntries(REIMBURSEMENT_ACCOUNT_FLOW_SCREENS.map((screen) => [screen, {animation: Animations.NONE}])) : {}),
 };