Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Maintenance work
View staffing
Description
Currently, the main
FragmentManager
saves all of the fragment state including the child fragment managers in one big bundle. This seems to be "fine" right now, but it is incorrect and does not follow our hierarchy pattern. Instead of everything being in one big bundle, each fragment manager in the hierarchy should save its own state, and the bundle created there should be saved as part of the state of its parent fragment, all the way up to the mainFragmentManager
.As we get closer to implementing the single fragment lifecycle, it is possible that this could have an impact.