bug: react-router, page kept for swipe-back stays visible on top when its ionPage outlet is re-entered at a different page in iOS mode
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 50/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- react, typescript
- Área
- frontend
Línea de trabajo
Start by reading StackManager.handleOutOfScopeOutlet and the view lookup logic in findViewItems, which the report identifies as the cause. Reproduce the route sequence in the linked example: Step 1 → Step 2 → Home → Settings → Step 1, then compare iOS and md modes. Done means only the page matching the current pathname remains visible when the nested outlet is re-entered.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Prerequisites
- I have read the Contributing Guidelines.
- I agree to follow the Code of Conduct.
- I have searched for existing issues that already report this problem, without success.
Ionic Framework Version
v9.x
Current Behavior
In iOS mode, an ionPage child outlet can end up with two visible pages. The page that
was active when the user left the outlet is never hidden. When the user later returns to
a different page in the same outlet, the old page stays on screen and covers the new one.
The URL is correct, but the user sees the wrong page. No error is thrown. In the DOM,
neither page is hidden:
<ion-router-outlet class="ion-page …">
<div class="ion-page can-go-back" data-testid="step-1" style="z-index: 101;">…</div>
<div class="ion-page can-go-back" data-testid="step-2" style="z-index: 101;">…</div>
</ion-router-outlet>
The page that comes later in the DOM is drawn on top. In md mode the same navigation
works.
Expected Behavior
Only the page for the current pathname is visible in the outlet. The page that was
active when the user left the outlet is hidden when another page in that outlet enters.
Steps to Reproduce
- Clone the reproduction, check out
swipe-preserved-page-visible, then run
npm installandnpm run dev. - Open
/onboarding/step1. The green Step 1 page is shown. (Each page has its own
background color: Step 1 green, Step 2 red, Home blue, Settings purple.) - Press Next. The app pushes
/onboarding/step2(red). - Press Finish. The app pushes
/home(blue), outside the onboarding outlet. - Press Settings. The app pushes
/settings(purple). - Press Back to Step 1. The app pushes
/onboarding/step1. - Observe: the URL is
/onboarding/step1, but the red Step 2 page is shown. The status
bar at the bottom reports
Visible onboarding pages: step-1, step-2 ← BUG: more than one.
It reproduces on every run (5/5 in Chromium, 3/3 in WebKit). Open
/onboarding/step1?mode=md and repeat the steps to compare: in md mode, the green Step 1
page is shown alone (3/3 runs).
The route shape is:
setupIonicReact({ mode: 'ios' });
<IonRouterOutlet>
<Route path="/onboarding/*" element={
<IonRouterOutlet ionPage>
<Route path="step1" element={<Step1 />} />
<Route path="step2" element={<Step2 />} />
</IonRouterOutlet>
} />
<Route path="/home" element={<HomePage />} />
<Route path="/settings" element={<SettingsPage />} />
</IonRouterOutlet>
All navigation uses router.push(path, 'forward').
Code Reproduction URL
https://github.com/ptmkenny/ionic-react-router-6-test/tree/swipe-preserved-page-visible
Ionic Info
Ionic:
Ionic CLI : 7.2.1 (/home/node/.npm/_npx/f6fddb685269761d/node_modules/@ionic/cli)
Ionic Framework : @ionic/react 9.0.10
Capacitor:
Capacitor CLI : 8.0.0
@capacitor/android : not installed
@capacitor/core : 8.0.0
@capacitor/ios : not installed
Utility:
cordova-res : not installed globally
native-run : 2.0.1
System:
NodeJS : v26.13.0 (/usr/local/bin/node)
npm : 11.20.0
OS : Linux 6.18
Additional Information
I used AI (Opus 5.5) to prepare this issue report and reproduction.
Root cause
StackManager.handleOutOfScopeOutlet has a branch for ionPage outlets whose parent
outlet has swipeGesture === true, which iOS mode enables by default. When the outlet
goes out of scope, this branch keeps every child view mounted, so a swipe back can show
them, and returns. It does not hide the active child page: only the parent outlet hides
the ionPage outlet as a whole.
When the outlet comes back in scope at a different child route, nothing hides that page:
- Finish pushes
/home. The onboarding outlet takes the swipe-preservation branch.
Step 2 stays mounted and not hidden. - Back to Step 1 pushes
/onboarding/step1.findViewItemsresolves the entering
view (Step 1) but no leaving view. It looks the leaving view up by
routeInfo.lastPathname(/settings) and thenrouteInfo.prevRouteLastPathname
(/home). Both belong to the parent outlet, so neither matches a view in this one. - With no leaving view, the transition shows Step 1 and hides nothing. Step 2 has been
visible since the user left the outlet, so both pages are visible.
The extra Settings step is needed only because of the prevRouteLastPathname
fallback. Going straight from Home back to Step 1 leaves prevRouteLastPathname at
/onboarding/step2, so Step 2 is found as the leaving view and hidden. Any two
navigations outside the outlet before returning trigger the bug.
AI-generated fix
Fix commit: https://github.com/ptmkenny/ionic-framework/commit/3d4f4ace71ada7810c654a1b7136d10f28366d07
(branch: https://github.com/ptmkenny/ionic-framework/tree/swipe-preserved-page-visible)
- Lenguaje dominante
- TypeScript
- Estrellas
- 52.8k
- Forks
- 13.3k
- Merge medio
- 3 d 1 h
- PR fusionados (30 d)
- 86
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ionic-team/ionic-framework
-
bug: input-otp, backspace in an empty box only moves focus instead of clearing the previous boxPosiblemente ocupada @sarankumar1325 la tomó hace 23 días. Abiertopackage: core type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
ionic-team/ionic-framework#31639 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug: vue swipe cancellation throws when the previous page is missingPosiblemente ocupada @dandoingdev la tomó hace 46 días. Abiertopackage: vue type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ionic-team/ionic-framework#31514 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug: ion-searchbar input is always labelled "search text"; aria-label on the host is not forwardedPosiblemente ocupada @HappyKnuckles la tomó hace 41 días. Abiertoa11y package: core type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
ionic-team/ionic-framework#31492 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug: IonTabs throws when a Fragment contains one IonRouterOutletPosiblemente ocupada @Benziza la tomó hace 82 días. Abiertopackage: react type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ionic-team/ionic-framework#31410 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
bug: angular swipe-back gesture crashes in StackController.startBackTransition when the stack is popped before the gesture is capturedPosiblemente ocupada @officialasishkumar la tomó hace 9 días. Abiertopackage: angular type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
ionic-team/ionic-framework#31291 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de ionic-team/ionic-framework
Issues similares
-
ready-for-ai
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
umbraco/Umbraco-CMS-MCP-Dev#647 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
HelloAOLab/seed-bible#2173 ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
hocinehacherouf/liberarr#77 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
LibreChat-AI/LibreChat#18225 ·
Los mantenedores suelen responder en 1 día
-
b-ber/build/epub b-ber/themes
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
triplecanopy/b-ber#790 ·
Los mantenedores suelen responder en 1 día