Closed lukepighetti closed 3 years ago
Tracking this for Nav 2.0 rewrite
Page A secondaryAnimation
should be visually paired with Page B animation
. This is what makes iOS routing so dynamic and compelling.
In other words, a Page's true secondaryAnimation should be pulled from the page that is being pushed over it, as that will match the motion of the push animation.
animation: left
animation: up
, Page A secondaryAnimation: left
animation: left
animation: up
, Page A secondaryAnimation: up
Any page should be able to have a transition for when it is presented/dismissed, or when it is covered/revealed (a page is presented on top of it).
Flutter semantics for this is
animation
andsecondaryAnimation
.Ref: https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/routes.dart#L947-L952