Closed simonschaufi closed 8 years ago
So, magellan is designed to navigate to an element on a page based on id's, not absolute paths as that could cause problems with other things. I'm going to chalk this up to a CMS issue and not Foundation.
I think that Foundation should just grab the hash and don't care about what's in front of that. Could you please tell me what side effects this could have as I have no idea what you are talking about.
well, before (version 5) it was possible to make this workaround:
<li data-magellan-arrival="top">
<a href="/#top">Home</a>
</li>
but since the data-magellan-arrival was removed, this doesn't work any more.
Hi, try this instead of Magellan.
My CMS creates absolute links, even to sections. Instead of links like
<a href="#first">First Arrival</a>
it creates links like this:<a href="/#first">First Arrival</a>
How can we reproduce this bug?
<a href="/#first">First Arrival</a>
What did you expect to happen? I expected to scroll smoothly down
What happened instead? Instead i jumped immediately down to the target
Test case Sorry, making links absolute on codepen break the system - no demo...
Here is the code line that is making this problem: https://github.com/zurb/foundation-sites/blob/develop/js/foundation.magellan.js#L126