Status Update
Comments
ma...@google.com <ma...@google.com>
na...@google.com <na...@google.com> #3
After some brief poking around:
Relevant code in LayoutNode:
Ends up here:
If accessibility is off, looks like changing progress semantics a no op which would be a big improvement to performance.
Otherwise semantics does a remeasure / relayout, and walks the full semantics tree. This would likely have no immediate benefit if accessibility is turned on.
pr...@google.com <pr...@google.com> #4
Would this suggestion also avoid recomposing, which seems like it would still be a problem even if it's a no-op in the guts of semantic node code.
Description
Jetpack Compose version: 1.6.2
Jetpack Compose component used: compose.material3
Android Studio Build: Iguana 2023.2.1 rc2
Kotlin version: 1.9.22
Steps to Reproduce or Code Sample to Reproduce:
Third elevated button will change its colors to tonal button, because tonal button caches its values into wrong variable (dedicated to tonal button).
From the sources:
androidx.compose.material3.Button.kt