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
You will note that the link to the fragment identifier above doesn't work if you click on the link above, but will work if you wait for ReSpec to do it's thing and then go to the Table of Contents and click on the "IRI" link. I'm guessing it's because when the browser hits the page, the fragment identifier doesn't exist because the ReSpec code hasn't run yet. Could we have a bit of code that runs after the entire document has been rendered to navigate to any fragment identifier that exists in the URL bar?
The text was updated successfully, but these errors were encountered:
We typically have "live" documents that represent the latest editor's draft, like so:
http://json-ld.org/spec/latest/json-ld-syntax/
Often, we would like to link people to a section of the document, like so:
http://json-ld.org/spec/latest/json-ld-syntax/#iris
You will note that the link to the fragment identifier above doesn't work if you click on the link above, but will work if you wait for ReSpec to do it's thing and then go to the Table of Contents and click on the "IRI" link. I'm guessing it's because when the browser hits the page, the fragment identifier doesn't exist because the ReSpec code hasn't run yet. Could we have a bit of code that runs after the entire document has been rendered to navigate to any fragment identifier that exists in the URL bar?
The text was updated successfully, but these errors were encountered: