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
When linking to a specific page in a PDF file using a page specifier gets changed in the Quartz website output, removing the = between page and the page number.
It seems #page=[page number] for PDFs is widely supported on modern desktop browsers. Mobile support seems a bit lower, depending on the source, especially on iOS devices.
Additionally, the #page=[page number] seems to be ignored if the PDF has been opened previously. In that case, it tends to head to the last viewed page. This seems to be intended browser caching behavior.
I'll open a pull request shortly to correct this issue.
I'll have to look into the caching behavior later if we decide to override page linking. Although I suppose implementing this behavior might be confusing for users as it is different from the default.
When linking to a specific page in a PDF file using a page specifier gets changed in the Quartz website output, removing the
=
betweenpage
and the page number.To reproduce
In a Markdown file with contents:
the contents gets transformed to:
Note the missing
=
betweenpage
and5
in the output HTML.Expected behavior
Expected output would be the full link without changing the URL.
node
Version: 21.6.2npm
version: 10.5.0The text was updated successfully, but these errors were encountered: