43ad57e548b86daf50e0ebfde440fe431a41cb1e
Following four steps with RecyclerView - CardView - ImageView: a. fade in imageview in onBind: calling imageView.setTransientState(true) b. RecyclerView animate the item: calling cardView.setTransientState(true) c. fade-in finishes, calling imageView.setTransientState(false) d. RecyclerView animation finishes: calling cardView.setTransientState(false) After these four steps, RecyclerView unexpectedly has transient state. The problem is in step b, when calling cardView.setTransientState() it incorrectly calls parent.childHasTransientStateChanged(this, true) which causes RecyclerView's mChildCountWithTransientState increased to 2. And it's decreased to 1 in step d and stay as 1 forever. The child should only call childHasTransientStateChanged() when actual hasTransientState() changed. Bug: 64235615 Test: ViewTransientStateTest Change-Id: I99ed35cc9c49e54d36590d8f1d206501fd3288f2
Merge "frameworks/base: use proper nativehelper headers" am:
826eafd958 am: 5c091dc944 am: c840945a78
Merge "frameworks/base: use proper nativehelper headers" am:
826eafd958 am: 5c091dc944 am: c840945a78
Merge "proto: add system message descriptor for Wi-Fi wrong password notification" into oc-dr1-dev am:
7bd4b3912b
…
Merge "frameworks/base: use proper nativehelper headers" am:
826eafd958 am: 5c091dc944 am: c840945a78
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%