Status Update
Comments
nh...@chromium.org <nh...@chromium.org> #2
Tram, can you confirm that the behavior is correct if the modifier is moved to the composable inside the AnimatedPane?
nh...@chromium.org <nh...@chromium.org> #3
Hi Max, yes when the modifiers are moved to the composable inside the AnimatedPane, the PB animations are better than when the modifiers are in the AnimatedPane itself
go...@google.com <go...@google.com> #5
After some investigation, I can conclude this behavior is consistent with other animation "wrapper" composables, e.g. AnimatedVisibility
. Modifiers should indeed be applied to the children in order to properly participate in the animation.
nh...@chromium.org <nh...@chromium.org> #6
Let me make the priority of this issue aligned with the priority of the original issue (P0).
nh...@chromium.org <nh...@chromium.org> #7
torne@: Friendly ping. This is the CL we want to merge:
We admit this workaround is not clean. We plan to remove this workaround once the user migrates to the Java-based prerender API.
to...@google.com <to...@google.com> #8
Apologies, didn't see this request - this looks fairly safe to merge given that it's for an experimental opt-in API.
go...@google.com <go...@google.com> #9
I will review this for the March 18th refresh.
nh...@chromium.org <nh...@chromium.org> #10
Thank you!
Description
This is an M134 merge request from crbug/399478939. The following changes were detected on the parent issue:
To proceed with this merge request:
Safe Merge Criteria
Please only select Yes in the Safe Merge field if all the following apply:
Please contact the milestone owner if you have questions.
Owners: lmenezes (ChromeOS), srinivassista (Desktop US), danielyip (Desktop EMEA), govind (Mobile US), eakpobaro (Mobile EMEA)
*This merge request uses Chrome's new merge process. Find more information at go/chrome-merge-quickstart .