-
Notifications
You must be signed in to change notification settings - Fork 26.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using Navigator 2.0 and a RouteAware widget with RouteObserver, the widget is rebuilt after its route is popped #116994
Comments
Thanks for the report. Seeing same behavior upon running the provided code sample:
stable, master flutter doctor -v
|
P3 to match b/262398491 |
It will cause the non-top page to re-execute the build |
This issue is marked P1 but has had no recent status updates. The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub. Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks! |
Steps to Reproduce
Expected results:
When using a Navigator 2.0/Router route that launches a
RouteAware
widget, I don't expect it to be rebuilt after it is popped. It's different behavior than using a Navigator 1.0 route.Actual results:
The
RouteAware
widget shown via the Navigator 2.0 route gets rebuilt after it is popped.If you uncheck the "Use route observer?" checkbox, it doesn't get rebuilt when the route is popped.
Code sample
See https://dartpad.dev/?id=9c70e9ccba24e889d8a190a74671bb42
Logs
N/A, repro in DartPad
The text was updated successfully, but these errors were encountered: