gdmi

Yea, I understood from the previous reply. I missed being specific, about that the one I saw was from dearPDF, not any other (at least in the debugger).
The update also appears to have fixed this, as I went to look at the other people pc’s there problem only persisted until after clearing cache (noticed it has a cached worker), so seems like both issues was from what I can judge fixed by the speedy update. Very impressive.

Hey

Thank you for the extremely speedy response. The update you released fixed the default behavior to work as intended.

As to the pdf.js, looking through the scripts on various parts of the sites, I only see the pdf.min.js (version 2.0.38) being used, but I didn’t encounter any other scripts that appear to be calling pdf.js. It should be mentioned that I have not seen the error on my own pcs, only colleagues.
Elementor does call the webpack, but a brief search didn’t reveal any PDF.