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)
Request for new functionality
View staffing
Description
Version used: 1.2.0-alpha02
show() and hide() don't affect the Fragment itself, but operate only on the View level to set the visibility of the View to VISIBLE / GONE, respectively.
This leads to cases where the Fragment is actually not visible (for example, an opaque view is over the top of your Fragment's view or you've set the visibility independently from FragmentTransaction), but isHidden() returns a value that is only related to whether you've called show() / hide() last.
This mismatch between what the Fragment level provides and what is actually happening at the View level means that this type of operation should exist on the level it operates on: solely at the View level.
Therefore the show() / hide() and isHidden() methods at the Fragment layer should be deprecated.