Bug with ext. URL links in PDF's generated from web page (browser)

[soewhaty]

SumatraPDF version

• Version [3.5.2, 64bit]

Describe the bug
Making a PDF from a web page used to work ok and puts the url of the page at the bottom left corner. So:

• Internal PDF links to pages in the PDF do work.
• mailto: links do work too
• However, the URL where the PDF was made from (usually in the bottom left corner) does not get recognized as a link in v3.5.2, it stays as static text. If I then open this exact same PDF in v3.1.2 64bit, the URL (in the bottom left corner) gets fully recognized as a link and it works just fine so it's clearly a thing to do specifically with v3.5.2.

To Reproduce
Steps to reproduce the behavior:

1. Go to any URL
2. Make a PDF of it
3. Scroll down to any page's bottom right/left corner
4. See the URL and verify if it acts as a link or not ... in v3.5.2 it doesn't, while in v3.1.2 it does ... same URL same PDF just opening it with 2 different versions of Sumatra .. that's all it takes to see the difference in behaviour

Expected behavior
That URL links at bottom of each PDF's page actually do work as links.

File that reproduces the problem
At random ... i.e. not with all files, so it basically also depends on which URL u make a PDF from, but my point is that at least with v3.1.2 this issue never appeared from any site whereas now with v3.5.2 sometimes it fails.

[GitHubRulesOK]

There were changes in URL handling but if it works for some and not others then they must be different and I am "guessing" without a sample different as internally absolute and relative so some secure and some less secure.

Without samples you need to try pre-release as only that versions behaviour can be changed.
As a workaround I have a custom external viewer for when I think 3.1.2 may handle pages differently so shown here.

[soewhaty]

I mean, for now I just switched back to v3.1.2 cos it still covers my needs well. Only reason I upped to the latest version was just to check it out n see what's new but I must admit that v3.1.2 and the versions around that were a touch faster at handling opening/tabbing-thru many many files in the same time so that behaviour I much needed. Another reason why I specifically stuch to v3.1.2 (and am coming back to it now) is cos for some reason closing tabs with mouse middle click would work stop working on some PCs/Screens ... whereas on v3.1.2 this precise behaviour has never caused an issue on any PC/screen/whatsoever ever..