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
Navigating the table of contents does not add to browser history. You can click around all you want in there and when you go 'back', the browser will ignore everywhere you've been and take you to the URL you pasted into it to first load up the spec.
Following markdown links does not change the history location to where you are jumping from. For example if you start at the top of the document then scroll down (or followed a ToC entry, since they don't affect the history) then follow a markdown [text](url) link, then use the browser's back button, you'll be back at the top of the spec.
I find both of these a bit annoying since our spec is huge, and people tend to bounce around it. The workaround is to middle-click links, but that doesn't work on the table of contents.
I wish I could help, but JS isn't my thing. A bit of a google suggests that a history.pushstate() could address the first problem?
The text was updated successfully, but these errors were encountered:
Two things:
Navigating the table of contents does not add to browser history. You can click around all you want in there and when you go 'back', the browser will ignore everywhere you've been and take you to the URL you pasted into it to first load up the spec.
Following markdown links does not change the history location to where you are jumping from. For example if you start at the top of the document then scroll down (or followed a ToC entry, since they don't affect the history) then follow a markdown
[text](url)
link, then use the browser's back button, you'll be back at the top of the spec.I find both of these a bit annoying since our spec is huge, and people tend to bounce around it. The workaround is to middle-click links, but that doesn't work on the table of contents.
I wish I could help, but JS isn't my thing. A bit of a google suggests that a
history.pushstate()
could address the first problem?The text was updated successfully, but these errors were encountered: