Adobe PDF printer hangs if NoScript is enabled

[cabbage]

When NoScript Firefox add-on is enabled, "Adobe PDF" printer hangs when trying to print a website to a PDF file.

My configuration:

NoScript 2.6.9.36
Firefox 40.0.3
Printer "Adobe PDF Converter" (part of Adobe Acrobat 11.0.0)

- when NoScript add-on is disabled entirely: printing to PDF file works fine

- when NoScript add-on is enabled: after target PDF file has been selected, the job goes into the print queue, but then the PDF printer and Firefox both hang, and I need to terminate Firefox. This happens even when scripts have been allowed globally. Other printers work fine though!

Any suggestions what NoScript settings I might have to tweak to bypass this problem? Would any additional information from my side help to resolve this issue? Many thanks for any helpful pointers!

[therube]

Anything related in Error Console (Ctrl+Shift+J)?

Any change if you disable all extensions except for NoScript?
Any change if you disable all extensions & all Plugins except for NoScript (& Adobe)?

And to be clear, this Acrobat itself, not Acrobat Reader?

[cabbage]

Thank you for your response!

And to be clear, this Acrobat itself, not Acrobat Reader?

Correct, the PDF printer was installed with Acrobat, not Adobe Reader.

Any change if you disable all extensions except for NoScript?
Any change if you disable all extensions & all Plugins except for NoScript (& Adobe)?

The only other Firefox extension that was enabled was HTTPS-Everywhere 5.1.1 - and this indeed seems to be part of the issue I'm observing!

After disabling HTTPS-Everywhere, but keeping NoScript enabled, printing to PDF files works fine - both with scripts globally allowed and scripts globally forbidden.
So it seems that printing via the Adobe PDF printer works fine with HTTPS-Everywhere alone enabled, and it works fine with NoScript alone enabled, but it hangs if both are enabled!

Anything related in Error Console (Ctrl+Shift+J)?

I can't see a clear difference between what shows up in the error console in the two cases...

What I plan to do next is strip the website source code to the minimal version that will still reproduce the problem, and then post the code here. If you have any thoughts on the issue meanwhile, please do let me know.