FooIbar
Add shared element transitions
Wow, seems both SET within navigations and downloadScreen grid/list switch works perfectly!
Btw, my telegram account gone again, and maybe I won't register a new one in a long time.
Everything looks good, seems we don't need https://issuetracker.google.com/issues/336449371?
Everything looks good, seems we don't need https://issuetracker.google.com/issues/336449371?
Yeah, could you help test if that snippet still behaves incorrectly?
Everything looks good, seems we don't need https://issuetracker.google.com/issues/336449371?
Yeah, could you help test if that snippet still behaves incorrectly?
Yes, the issue persists.
Everything looks good, seems we don't need https://issuetracker.google.com/issues/336449371?
Yeah, could you help test if that snippet still behaves incorrectly?
Yes, the issue persists.
Acked.
@revonateB0T I think we may only want shared element transitions for list <=> detail. The list <=> list and list <=> grid transitions feel distracting as there are too many moving parts. Like the M3 guide says https://m3.material.io/styles/motion/transitions/applying-transitions#b974d94c-bf80-4c54-8818-4a1d7eaa10ae
@revonateB0T I think we may only want shared element transitions for list <=> detail. The list <=> list and list <=> grid transitions feel distracting as there are too many moving parts. Like the M3 guide says https://m3.material.io/styles/motion/transitions/applying-transitions#b974d94c-bf80-4c54-8818-4a1d7eaa10ae
Well, maybe, list <=> grid is somewhat lag as there's so many moving items. But I suppose the multiple SET framework can be kept in case it's useful and we may need it one day.