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
It's not possible without some fundamental changes at vscode. From the extension perspective, we receive a vscode.Uri passed to resolveCustomEditor in class vscode.CustomReadonlyEditorProvider. However, in the URI, no hash information is provided. It means that the extension has no way to know if the clicked link has a hash component or not.
I don't think it is an easy change on the vscode side. However, there is no easy or hard or dirty workaround to obtain the hash string otherwise.
Pre-checks*
The Missed*
page
hash for directly linking to a specific pagevscode-pdf
is not actively maintainedThe Solution*
filename.pdf#page=<pageNumber>
Anything Else?
pdf.js
: Expose fragment IDs in the URL mozilla/pdf.js#5258 (comment)vscode-pdf
:The text was updated successfully, but these errors were encountered: