I think some banks utilize some feature built in PDF Readers to PREVENT printing of “SENSITIVE” information in a PDF, by blocking parts with black bars.
The issue does not appear when printing using other software, like Adobe Reader or Microsoft Edge, to print the PDF. But it DOES occur with Firefox and Chrome. So it’s not a driver issue.
Is this a form of DRM? I want to know how it works whatever is causing it, and be able to REMOVE it from the PDF itself completely.
Why does Firefox obey this “DRM” crap, while Edge has the balls to ignore it?
And to make things even more complicated, I am able to print the PDF fine on another computer, using the exact same OS, browser, and printer. So it appears to be a specific setting or version of .e.g Firefox?
If only I had NAME for this, then I’d be able to search for it online.
Your whole comment is built on a mistaken premise.
It’s not. Edge can choose to behave differently than Chrome in individual points like this, so long as they still behave like Chrome for 99.9% of the web standards, webpage owners won’t really be able to block them without blocking Chrome, nor need to put in extra effort to support Edge.
(They could block Edge based on user-agent string, but Microsoft could change the user-agent string.)
Like, yeah, if it’s essential for a given webpage that this half-assed redaction feature works, then they might actually block access from Edge. But most webpage owners won’t notice that it doesn’t work, and even if individual webpages block Edge, Microsoft will hardly care.