For a list that want to make the browser more secure, why do they want to remove the only line of defense against sites using fullscreen mode for phishing?
> Disable PDF reader
PDF.js has fewer security vulnerabilities than desktop PDF readers.
> Disable 'safe browsing' aka. Google tracking/logging
This seems like a really bad idea for most users
You can limit desktop readers with something like AppArmor (no network access, only allowed to read files, only allowed to open *.pdf files, etc). You can't (AFAIK) do that with PDF.js.
You just let through the vulnerability in PDF.js.
Also, no networking.
The point here is that the sandboxing needs to be watertight, or it's simply not effective. pdf.js runs in the JS sandbox, but here the file origin checking failed. Placing an OS-level sandbox around it doesn't help unless it is just as tight.
allow /**/*.pdf r,That's probably because there is one PDF.js and dozens of desktop PDF readers.
PDF.js sprouts CVEs at an alarming rate. It should be disabled until someone does a full-program security audit.