Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 6c747f802dcc8bad6b521de8433f02980b60357b
Author: jbwoods <jbwoods@google.com>
Date: Thu Mar 28 14:30:45 2019
Remove hardware layer for Fragment animations affecting alpha
FragmentManager changes the View's layer type to
View.LAYER_TYPE_HARDWARE for animations. This is unnecessary (for
reasonably modern devices) and we should leave the decision of layer
types to the user.
Removed the code that deals with changing the View's layer type.
Test: ran fragment tests.
Tested fragment animations in app on Q and API 16
BUG: 129486478
Change-Id: I4820d3b2193b1b2429cd23f6e8ed726547972215
M fragment/src/main/java/androidx/fragment/app/FragmentManagerImpl.java
https://android-review.googlesource.com/936613
https://goto.google.com/android-sha1/6c747f802dcc8bad6b521de8433f02980b60357b
Branch: androidx-master-dev
commit 6c747f802dcc8bad6b521de8433f02980b60357b
Author: jbwoods <jbwoods@google.com>
Date: Thu Mar 28 14:30:45 2019
Remove hardware layer for Fragment animations affecting alpha
FragmentManager changes the View's layer type to
View.LAYER_TYPE_HARDWARE for animations. This is unnecessary (for
reasonably modern devices) and we should leave the decision of layer
types to the user.
Removed the code that deals with changing the View's layer type.
Test: ran fragment tests.
Tested fragment animations in app on Q and API 16
BUG: 129486478
Change-Id: I4820d3b2193b1b2429cd23f6e8ed726547972215
M fragment/src/main/java/androidx/fragment/app/FragmentManagerImpl.java
il...@google.com <il...@google.com> #3
We've fixed this internally and it'll be available in a future build of Fragments (but not the upcoming 1.1.0-alpha06).
da...@gmail.com <da...@gmail.com> #4
This bug seems to be partially back in Android 15. Setting hardware layer in fragment doesn't make difference.
Description
Version used: 1.1.0-alpha05
FragmentManager unconditionally changes the View's layer type to View.LAYER_TYPE_HARDWARE, resetting it to LAYER_TYPE_NONE when the animation is over. We shouldn't change the layer type at all (and it is totally unnecessary on reasonably modern devices) and leave the decision of layer type to users.