-
-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Problems with links occur when converting to PDF #2021
Comments
I have exactly the same problem here. Tried also with older plugin versions down to 6.10 with same result. |
I understand the cause. It seems to be caused by the current version of chrome when performing Preview → Export → Chrome (Puppeteer). I was able to confirm that the links worked fine after reinstalling the previous version of chrome. Your only option is to lock chrome to a version or wait for a fixed version to be released. |
Can you tell if it is then a conversion or a display issue? I was able to open the generated PDF correctly in FoxitReader, while both Chrome and Edge messed up all links. Or does Edge use Chrome for PDF display? |
I think it's a conversion issue. However, depending on the PC, the link may work properly even with the same version, which is a mystery. Links work fine in Adobe, but not in browsers like Chrome or Edge. |
I wrote a similar issue in #2014. https://issues.chromium.org/issues/347674894 The above issue in Chromium is now FIXED, so I set up Chrome Canary (129.0.6624.0) to check it. |
Thanks for the info!
|
Describe the bug
A clear and concise description of what the bug is.
If you preview with Markdown Preview Enhanced and convert it to PDF, the links within the page will be strange. It feels like it shifts irregularly.
However, during the preview stage, in-page links work fine.
This issue was discovered on July 4th. It was working fine until last week.
I restarted my PC and reinstalled VSCode, but it didn't work.
However, even after converting it to PDF, for some reason the links within the page only work properly when opened in Adobe.
After converting to PDF, in-page links did not work properly in VSCode's vscode-pdf, chrome, and edge.
Environment
The text was updated successfully, but these errors were encountered: