New issue
Advanced search Search tips

Issue 853061 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Make third-party extensions work on PDF viewer (plugin)

Reported by yuanyun....@gmail.com, Jun 15 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. Install chrome vimium from https://chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb?hl=en
2. Open one pdf in chrome
3.  Problem: chrome vimium's function not work at all.
More at: https://github.com/philc/vimium/issues/1976
There are some great extensions that we want it to work with chrome's pdf viewer.

For example, chrome vimium.

What is the expected behavior?

What went wrong?
There are some great extensions that we want it to work with chrome's pdf viewer.

For example, chrome vimium.

WebStore page: https://chrome.google.com/webstore/detail/vimium/dbepggeogbaibhgnhhndojpepiihcmeb?hl=en

Did this work before? No 

Chrome version: 66.0.3359.181  Channel: n/a
OS Version: OS X 10.12.6
Flash Version: Shockwave Flash 30.0 r0
 
Labels: Needs-Milestone
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET M-69 Target-69 FoundIn-69 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version 66.0.3359.181 and latest stable 67.0.3396.87  also on latest chrome 69.0.3460.0 using Mac 10.13.5, Ubuntu 14.04 and Windows 10.  
 
Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged.

Thanks! 
Owner: rdevlin....@chromium.org
Status: WontFix (was: Untriaged)
While I agree there's some use cases for this, unfortunately, this isn't something we're likely to change.  The PDF viewer is a component extension, and is thus whitelisted for powerful capabilities.  If an extension can inject into a PDF viewer context, it is able to access these private APIs, and wreak a lot of havoc on the user's machine.  This is the same reason that we don't allow extensions to inject on chrome:- scheme urls (like chrome://settings or chrome://downloads).

Note that I *think* if you really want this to work, you can use the extensions-on-chrome-urls flag: chrome://flags/#extensions-on-chrome-urls.  However, this isn't a fully supported flag, and will also open up dangerous attacks (described above).

Sorry we couldn't give you a better answer!
thanks for your response.

btw, I installed the same plugin in firefox 
https://addons.mozilla.org/en-US/firefox/addon/vimium-ff/

The Vimium plugin works in firefox, we can use Vimium functions when read pdf file in foirefox.

Sign in to add a comment