-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
beforeEach guard not changing URL after user uses back button #1850
Labels
bug
Something isn't working
has PR
This issue has already a PR with pending reviews
has workaround
A workaround has been found to deal with the issue
Comments
You are being redirected to the Home page because that’s what you return in the navigation guard |
The component being rendered is |
I'm having the exact same problem described in this issue. I don't understand why it was closed so soon |
I opened #2133 with a workaround. |
posva
added
bug
Something isn't working
has PR
This issue has already a PR with pending reviews
has workaround
A workaround has been found to deal with the issue
labels
Feb 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
has PR
This issue has already a PR with pending reviews
has workaround
A workaround has been found to deal with the issue
Reproduction
https://codesandbox.io/s/epic-dew-cgwffy
Steps to reproduce the bug
Expected behavior
After the router intercepts the route, the new URL should be the one I am returning on the
beforEach
callback.Actual behavior
The URL is staying as the one it was redirected from.
Additional information
In my actual app, no matter how many times I hit the back button, the URL stays on the route that the router redirected from i.e. the
from.fullPath
from thebeforeEach
guard.I am using version 4.2.1 on my app.
It seems it's the same as #916, and the temporal fix also works in this case. The implemented fix (#921) however, doesn't to solve my situation.
The text was updated successfully, but these errors were encountered: