diff options
| author | Adam Powell <adamp@google.com> | 2016-08-22 09:09:44 -0700 |
|---|---|---|
| committer | Adam Powell <adamp@google.com> | 2016-08-22 17:47:09 +0000 |
| commit | 64e1ba4398aad1b08a24b15a1d094eb2e9cc1e61 (patch) | |
| tree | d540935662be21c883852e42254c0c6ed8795022 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 051d6b74eb1acdf959f4ed23ec4b861d4dd41d90 (diff) | |
Only dispatch window visibility aggregation for targetSdk >= N
Some existing apps treat drawable visibility notifications as a signal
to crossfade from a placeholder to the new image for the purposes of
scrolling onscreen via a recycling collection view or similar. Since
dispatchVisibilityAggregated is now called for window visibility
changes and ImageView informs its drawable of the visiblity change,
the extra call triggers a repeat fade-in in some existing apps when
you return them to visibility.
These apps should pay attention to the second parameter of
Drawable#setVisible, which signals that animations should not restart
in response to a visibility change. Updating to targetSdkVersion=24+
will enable the new behavior.
Bug 30216207
Change-Id: I27ce9f09bc7544863f7f7980c273650949db21cc
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions