Fixed
Status Update
Comments
an...@google.com <an...@google.com>
ap...@google.com <ap...@google.com> #2
Hi. Thanks for reporting this. Fixed in alpha-04
No update yet.
Hi. Thanks for reporting this. Fixed in alpha-04
Description
It seems that onGloballyPositioned always requests remeasurement on recomposition.
When setting a new modifier we are doing:
and here
addedCallback
will always be true, becauseModifier.onGloballyPositioned
is always creating a new object on recomposition. Fixing this might require an API change asonGloballyPositioned
is currently inline, so we cannot use the lambda instance to check for modifier equality across recomposition.