You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Nested frames (fragments) disappear when their parent frame (fragment) is animated #6659
Describe the bug
Nested frames (i.e. fragments) disappear when their parent is animated. Related to #6641 but the problem is not specific to TabView and is more general. Caused by https://issuetracker.google.com/issues/36970570 -- arcane issue that Google somehow marked as obsolete & won't fix.
To Reproduce
Tap "navigate to some page" -- notice how the "Players" part of the page disappears immediately instead of transitioning away with the rest of the view.
changed the title [-]Nested frames (fragments) disappear when their parent is animated[/-][+]Nested frames (fragments) disappear when their parent frame (fragment) is animated[/+]on Dec 4, 2018
The fix you implemented where you dispose the current fragment on onUnloaded has bad consequences for apps with map for example.
Doing so create unecessary OpenGL redrawing (becuase the mapview is recreated on every pause/resume).
PLus running the sample app i actually cant see any issue as explaned here.
I will create a PR to remove that behavior fix. Hoping for you guys to accept it.
Closing in favor of #7772, which tracks the overhaul of Android page navigation transitions, including nested fragments that disappear while their parent animates. Several partial fixes have landed since (#6677, #8793). Please add current repros there.
Activity
[-]Nested frames (fragments) disappear when their parent is animated[/-][+]Nested frames (fragments) disappear when their parent frame (fragment) is animated[/+]manoldonev commentedon Mar 8, 2019
Reopening this issue as it could occur in a similar scenario but when navigating backwards from a nested-frame page.
To reproduce:
Sample Project:
Archive.zip
Note this problem can only be observed after #7011 is merged
farfromrefug commentedon May 5, 2020
The fix you implemented where you dispose the current fragment on
onUnloadedhas bad consequences for apps with map for example.Doing so create unecessary OpenGL redrawing (becuase the mapview is recreated on every pause/resume).
PLus running the sample app i actually cant see any issue as explaned here.
I will create a PR to remove that behavior fix. Hoping for you guys to accept it.
NathanWalker commentedon Oct 23, 2026
Closing in favor of #7772, which tracks the overhaul of Android page navigation transitions, including nested fragments that disappear while their parent animates. Several partial fixes have landed since (#6677, #8793). Please add current repros there.