pdfium not fully blocked on Linux

[diracdeltas]

STR:

1. try the repro steps from PDFs fail to load if behind basic auth #1788 on Linux
2. notice that instead of prompting you to download the PDF, it loads in Chrome's PDF viewer (pdfium)

[darkdh]

component is also showing enable in both `brave://extensions` and `brave://net-internals/#modules`

[yrliou]

Seems like it is not always happening because I could not reproduce it on 0.55.22 using Ubuntu 18.04. Chromium PDF Viewer is disabled for me and the STR would prompt me to download the PDF.

[bbondy]

Can anyone reproduce this with c71 and beyond?

[diracdeltas]

It was repro'ed by anonymous on Linux with 0.55.x master. I do not know of anyone who has tested this on c71 and above.

[tildelowengrimm]

@kjozwiak Can you check to see if this still repros?

[kjozwiak]

This is what I'm seeing when using 0.57.7 Chromium: 71.0.3578.53 under Ubuntu 18.04 x64 VM:

What basically happens is that when I initially authenticate, it uses Chrome's PDF viewer (pdfium), however re-loading it again after the authentication loads the PDF within PDFJS. Chrome's PDF viewer (pdfium) seems to be enabled under brave://extensions as well.

[diracdeltas]

@yrliou based on what @kjozwiak posted above, it appears the original bug is still in c71

[bbondy]

upping this to p2

[fmarier]

Based on brave/brave-core#980 (comment), I don't think we can disable PDFium entirely. I'll have to dig into why it gets picked up for PDFs behind auth.

[fmarier]

By following the repro steps, I was able to see PDFium in these versions:

• Version 0.57.8 Chromium: 71.0.3578.53 (Official Build) beta (64-bit)
• Version 0.57.18 Chromium: 71.0.3578.80 (Official Build) (64-bit)

but not in these ones:

• Version 0.58.9 Chromium: 71.0.3578.53 (Official Build) dev (64-bit)
• Version 0.58.11 Chromium: 71.0.3578.80 (Official Build) beta (64-bit)
• Version 0.58.21 Chromium: 71.0.3578.98 (Official Build) (64-bit)

So as far as I can tell, this problem was fixed in 0.58.

[srirambv]

Moving to Not actionable milestone as its already fixed and release channel migration has already completed.