Repository navigation
Redesign snackbar API to not use routes #432
Description
I think snack bars should be a feature of a Scaffold. They probably shouldn't use routes at all.
According to the specs -- https://www.google.com/design/spec/components/snackbars-toasts.html#snackbars-toasts-specs -- they should not time out while another route (e.g. a dialog) is over them, they should reset their timeout when their parent route resumes being the current route, they should be displayed consecutively in time, etc.
Activity
HansMuller commentedon Nov 17, 2015
This sounds correct to me. Perhaps non-modal bottom sheets should also just be a scaffold feature?
Hixie commentedon Nov 17, 2015
Well, they need a StateRoute so that they can react to the back button (I don't think snack bars should react to the back button). But beyond that, maybe.
github-actions commentedon Aug 17, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.