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
Browser Forward button not enabled #32248
Comments
This will be a new framework feature. Flutter was designed for native mobile where there's no such thing as "forward". |
We should prioritize this. We could certainly put in a forward stack to go along w/ the back stack. This is pretty core to how folks expect the web to work. |
After chatting briefly with @mdebbar we decided that this will be orders of magnitude easier to fix after we unfork the project. |
Any updates on this? |
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
This comment was marked as abuse.
i have same issue [!] Android toolchain - develop for Android devices (Android SDK version 28.0.3) [√] Chrome - develop for the web [√] Android Studio (version 3.3) [√] Android Studio (version 3.5) [√] VS Code (version 1.45.1) [√] Connected device (2 available) |
Hi, any update on this? |
@yjbanov Why was this labeled as P5 instead of P4? This is a pretty serious UX issue, as people have come to expect their browser forward button to work on all websites. Rather than treating it as a nice-to-have feature request, I'd like this to be treated with the severity of a bug, at the very least. A UX bug is still a bug. |
It's been pending since a long time. Any ETA for this ? |
This comment was marked as abuse.
This comment was marked as abuse.
Anything on this? |
Hi, Any update on this? |
Flutter cannot be used as a web page until this bug is fixed. |
This issue should be fixed if you use Router widget, see #63424 |
FYI might want to update the FAQ's that say this is not ready |
open this issue to keep track doc update |
assigning to myself, already working on updating FAQs and this specific question |
docs updated |
For me, this issue is still not closed. Some of us want to use Navigator 1.0 for the web with the onGenerateRoute, onUnknownRoute, and routes param. This is because Navigator 2.0 can be extremely difficult to implement in some cases However, using the Navigator 1.0 approach (which is supposed to be supported and not deprecated), the forward button is still not enabled which is a serious UX problem. Do we know if there is any workaround besides using Navigator 2.0? |
There is no planed work to support the forward button in nav 1, and I doubt we will spend time doing it in the future. Our current plan is to improve the usability of nav 2. See https://github.com/flutter/uxr/wiki/Navigator-2.0-API-Usability-Research |
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 |
Describe the bug
You can use the back button to step to the previous page in your Flutter app, but after pressing "back" the "forward" button does not become enabled on my browser.
To Reproduce
Steps to reproduce the behavior:
Open the Flutter Gallery app in your browser. Tap to navigate to any page. For example, "Style", then "colors". Hit the back button. The forward button does not become enabled after navigating to the new page.
Expected behavior
A clear and concise description of what you expected to happen.
I expect the forward button to become enabled after I navigate to the previous page.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: