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

Navigo triggers resolve for hash with hash navigation disabled #57

Closed
sergiopvilar opened this issue Oct 26, 2016 · 10 comments · Fixed by #58
Closed

Navigo triggers resolve for hash with hash navigation disabled #57

sergiopvilar opened this issue Oct 26, 2016 · 10 comments · Fixed by #58

Comments

@sergiopvilar
Copy link
Contributor

Hey, I'm having a problem with Navigo.

I have this url:
http://localhost:3000/users/foo#section1

In this page I have some tabs (section1, section0) when I click any of the tabs and the url changes to, for instance, http://localhost:3000/users/foo#section1 Navigo triggers the resolve even with the hash navigation disabled.

@krasimir
Copy link
Owner

So is it like the URL is not changed but you get your handler called?

@sergiopvilar
Copy link
Contributor Author

@krasimir only the hash changes and still yet I get the route resolved.

@krasimir
Copy link
Owner

I see. That's a bug. I'll try providing a fix.

@sergiopvilar
Copy link
Contributor Author

@krasimir I have some use cases:

  1. The url changes from a hash to another
  2. The url changes from no hash to a hash
  3. The url changes from a hash to no hash

krasimir pushed a commit that referenced this issue Oct 30, 2016
@krasimir
Copy link
Owner

@sergiovilar can you please try 3.3.2 version.

@sergiopvilar
Copy link
Contributor Author

@krasimir Just readed your commit and tested here. The * handler still get triggered by hash change when hash navigation is disabled.

@sergiopvilar
Copy link
Contributor Author

notFound handler also gets resolved when I am in this url: http://localhost:3000/some#tab1 and changes to http://localhost:3000/stores#tab0.

@krasimir
Copy link
Owner

krasimir commented Nov 7, 2016

@sergiovilar second try. Can you please the new 3.3.3 version.

@sergiopvilar
Copy link
Contributor Author

@krasimir works like a charm, thank you!

@JurajVajda
Copy link

Hi @sergiovilar what is your workaround this issue, i have the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants