-
Notifications
You must be signed in to change notification settings - Fork 471
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
In Safari, routing to <GmapMap> creates unintended window.history.state #485
Comments
Did you find a workaround for this @byeokim ? |
No, I couldn't. Are you experiencing the same issue, @Rombusevil? |
Have you tried wrapping your i.e. <keep-alive><router-view/></keep-alive> |
It solved the issue. Thank you for your suggestion. What about you, @Rombusevil ? |
It's works! I even checked all docs about vue & vue-router, and created so much DEMO to debug this issue these days. |
In Safari (both macOS and iOS versions), routing to a route containing
<GmapMap>
component for the first time, it works as expected. However, routing to the route for the second time using Safari's Back/Forward buttons, it doesn't work as expected: it creates additionalwindow.history.state
.Link to reproduction
https://jsfiddle.net/nuacb10j/
(if Google Maps JavaScript API key doesn't work, please try again with your own API key)
Steps to reproduce
At
/
,/foo
Expected behavior
Navigate to
/
Actual behavior
Navigate to
/foo
(another/foo
which was created after step 3)Additional infomation
/home
instead of/foo
works as expected. (/home
doesn't contain<GmapMap>
component)The text was updated successfully, but these errors were encountered: