You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anchor tags cannot be implemented correctly in the current state of things. There are a few techniques to hack a way around, but none of them seem to cover all the following cases:
Paths with anchors should always lead to the anchor if reached multiple times (currently, only the first time works, even by refreshing the page)
Anchor tags urls should be shareable (users should be capable of bookmarking/sharing URLs, in a way that the URL will lead them back directly to the anchor)
AFAIK, there two solutions currently that partially support those requirements: vue-router Scroll behavior that does not support first requirement in a robust manner, and vue-scrollto that does not support second requirement since it's just scrolling without any sense of routing/url.
What does the proposed API look like?
The API is already there, using the hash field
<router-link :to="{name: 'SomeVue', hash:'#anchor'}">Link to anchor</router-link>
// or
<a href="/somevue#anchor>Link to anchor</a>
<div id="anchor">Anchor</div>
We only need to implement the proper behavior for supporting use cases presented above.
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
Anchor tags cannot be implemented correctly in the current state of things. There are a few techniques to hack a way around, but none of them seem to cover all the following cases:
AFAIK, there two solutions currently that partially support those requirements: vue-router Scroll behavior that does not support first requirement in a robust manner, and vue-scrollto that does not support second requirement since it's just scrolling without any sense of routing/url.
What does the proposed API look like?
The API is already there, using the hash field
We only need to implement the proper behavior for supporting use cases presented above.
The text was updated successfully, but these errors were encountered: