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
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
After updating to 0.23.3 and looking at the changes I tested an anchor link only to find that instead of scrolling or snapping to the anchor on page it went to the root domain with the anchor see screen.
What version were you running before when that link was working? For quite some time, you have had to specify an entire path in links, even ones intended to by anchor links to the same page. See, e.g., this PR, which fixes a link on the Svelte docs site, at which time that site was using Sapper 0.12.
I've updated from 0.23 however i havent ever tested this before, the only issue is I have no control over the links in the content as they are pulled from a cms. Should sapper not attempt to replicate default browser behaviour here?
After updating to 0.23.3 and looking at the changes I tested an anchor link only to find that instead of scrolling or snapping to the anchor on page it went to the root domain with the anchor see screen.
Perhaps related to #472 and/or #341
The text was updated successfully, but these errors were encountered: