Skip to content
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

Closed
efortuna opened this issue Apr 4, 2019 · 22 comments
Closed

Browser Forward button not enabled #32248

efortuna opened this issue Apr 4, 2019 · 22 comments
Labels
a: fidelity Matching the OEM platforms better c: new feature Nothing broken; request for a new capability customer: crowd Affects or could affect many people, though not necessarily a specific customer. P3 Issues that are less important to the Flutter project platform-web Web applications specifically

Comments

@efortuna
Copy link
Contributor

efortuna commented Apr 4, 2019

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):

  • OS: mac
  • Browser Chrome 73.0.3683.86
  • Dart Version 2.2.1-dev.2.0.flutter-None on "macos_x64"
  • Flutter Web commit SHA: 04e53468fd60f6d7613a0745fba2dc14eac676c9
@yjbanov
Copy link
Contributor

yjbanov commented Apr 11, 2019

This will be a new framework feature. Flutter was designed for native mobile where there's no such thing as "forward".

@kevmoo
Copy link
Contributor

kevmoo commented Apr 16, 2019

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.

@yjbanov
Copy link
Contributor

yjbanov commented Apr 17, 2019

After chatting briefly with @mdebbar we decided that this will be orders of magnitude easier to fix after we unfork the project.

@kevmoo kevmoo transferred this issue from another repository May 7, 2019
@kevmoo kevmoo added the platform-web Web applications specifically label May 7, 2019
@yjbanov yjbanov added a: fidelity Matching the OEM platforms better c: new feature Nothing broken; request for a new capability labels May 23, 2019
@yjbanov yjbanov added this to the Goals milestone May 23, 2019
@Levi-Lesches
Copy link
Contributor

Any updates on this?

@andesappal

This comment was marked as abuse.

@andesappal

This comment was marked as abuse.

@kf6gpe kf6gpe added the P2 Important issues not at the top of the work list label May 29, 2020
@mahmoudsalah37
Copy link

mahmoudsalah37 commented Jun 5, 2020

i have same issue
[√] Flutter (Channel beta, 1.18.0-11.1.pre, on Microsoft Windows [Version 10.0.18363.836], locale en-US)
• Flutter version 1.18.0-11.1.pre at C:\flutter\flutter
• Framework revision 2738a11 (3 weeks ago), 2020-05-13 15:24:36 -0700
• Engine revision ef9215ceb2
• Dart version 2.9.0 (build 2.9.0-8.2.beta)

[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at C:\flutter\sdk
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = C:\flutter\sdk
• Java binary at: C:\flutter\android-studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b01)
X Android license status unknown.
Try re-installing or updating your Android SDK Manager.
See https://developer.android.com/studio/#downloads or visit visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed
instructions.

[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 3.3)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 34.0.1
• Dart plugin version 182.5215
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[√] Android Studio (version 3.5)
• Android Studio at C:\flutter\android-studio
• Flutter plugin version 34.0.4
• Dart plugin version 191.6183.88
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b01)

[√] VS Code (version 1.45.1)
• VS Code at C:\Users\Mahmoud salah eldin\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.11.0

[√] Connected device (2 available)
• Web Server • web-server • web-javascript • Flutter Tools
• Chrome • chrome • web-javascript • Google Chrome 83.0.4103.97

@yjbanov yjbanov added P3 Issues that are less important to the Flutter project and removed P2 Important issues not at the top of the work list labels Jun 16, 2020
@sujithkanna
Copy link

Hi, any update on this?

@iapicca iapicca added customer: crowd Affects or could affect many people, though not necessarily a specific customer. passed first triage labels Jul 3, 2020
@12people
Copy link

12people commented Jul 8, 2020

@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.

@Akashmathwani
Copy link

It's been pending since a long time. Any ETA for this ?

@andesappal

This comment was marked as abuse.

@ochmist
Copy link

ochmist commented Aug 17, 2020

Anything on this?

@Hixie Hixie removed this from the None. milestone Aug 17, 2020
@ch-muhammad-adil
Copy link

Hi, Any update on this?

@ghost
Copy link

ghost commented Sep 15, 2020

Flutter cannot be used as a web page until this bug is fixed.
I would appreciate it if you could correct it.

@chunhtai
Copy link
Contributor

This issue should be fixed if you use Router widget, see #63424

@steeling
Copy link

FYI might want to update the FAQ's that say this is not ready

https://flutter.dev/docs/development/platform-integration/web#how-are-forward-and-backward-buttons-presented-in-the-web-ui

@chunhtai
Copy link
Contributor

open this issue to keep track doc update

@mariamhas mariamhas self-assigned this Feb 24, 2021
@mariamhas
Copy link

assigning to myself, already working on updating FAQs and this specific question

@mariamhas
Copy link

docs updated

@jpv123
Copy link

jpv123 commented Apr 19, 2021

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?

@chunhtai
Copy link
Contributor

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

@github-actions
Copy link

github-actions bot commented Aug 2, 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 -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
a: fidelity Matching the OEM platforms better c: new feature Nothing broken; request for a new capability customer: crowd Affects or could affect many people, though not necessarily a specific customer. P3 Issues that are less important to the Flutter project platform-web Web applications specifically
Projects
None yet
Development

No branches or pull requests