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

New router [rc.1] - Browser back & forward buttons not working correctly #8524

Closed
dominique-mueller opened this issue May 7, 2016 · 5 comments

Comments

@dominique-mueller
Copy link

Current behavior

Currently I see two issues when navigating with the new router:

  • When pressing the browser back button, I get redirected to the previously opened page (so this works) - but the forward button of the browser is (always) greyed out and cannot be used. Is this a bug or a decision?
  • When I click on a router link which links to a another route using an absolute route path, and this route path is the same I'm already in, the route will not be reloaded (which is good) - but mysteriously the browser back button completely breaks and cannot be used any longer.

Expected/desired behavior

Well, it would be nice if the user just can use the browser navigation buttons in any Angular 2 application. Maybe this aspect just hasn't been developed yet?

Other information

Tested on both Chrome & Firefox (latest versions) with identical behaviour.

@neilhem
Copy link
Contributor

neilhem commented May 7, 2016

Seems like it will be fixed ASAP

@ravinderpayal
Copy link

Same problem here
StackOverflow Question

@AhsanAyaz
Copy link
Contributor

+1 ..

@jmurphzyo
Copy link

Also when using the back button it will only go back one route.

KiaraGrouwstra pushed a commit to KiaraGrouwstra/angular that referenced this issue Jun 10, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants