You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an extension is installed via group policies in Chrome, a user cannot grant the extension access to local file URLs. The checkbox is simply not visible, and there is no way for admins to allow files: https://bugs.chromium.org/p/chromium/issues/detail?id=173640
So when the extension detects a PDF file, the following page is shown (from #6233):
But the user has no way of allowing this access. There should be some work-around to this problem, even if it is an <input type=file> to select the file (or a preference to disable interception of local files).
The text was updated successfully, but these errors were encountered:
Test case to exercise the different encodings:
1. Create a file "some file#@%M<br>%25 .pdf"
2. Build the extension with `gulp chromium` and load it in Chrome.
3. Go to `chrome://extensions/` and ensure that the
"Allow access to file URLs" is disabled.
4. Try to open the file from step 1 in Chrome (maybe reload once).
5. PDF.js should be showing a file chooser button.
6. Click on that button and select a different file.
Test: Check that a confirmation dialog pops up that warns about
a different file name. Cancel the dialog.
7. Click on the button again and select the original file.
Test: Check that the file opens as expected.
Test case to exercise the different encodings:
1. Create a file "some file#@%M<br>%25 .pdf"
2. Build the extension with `gulp chromium` and load it in Chrome.
3. Go to `chrome://extensions/` and ensure that the
"Allow access to file URLs" is disabled.
4. Try to open the file from step 1 in Chrome (maybe reload once).
5. PDF.js should be showing a file chooser button.
6. Click on that button and select a different file.
Test: Check that a confirmation dialog pops up that warns about
a different file name. Cancel the dialog.
7. Click on the button again and select the original file.
Test: Check that the file opens as expected.
When an extension is installed via group policies in Chrome, a user cannot grant the extension access to local file URLs. The checkbox is simply not visible, and there is no way for admins to allow files: https://bugs.chromium.org/p/chromium/issues/detail?id=173640
So when the extension detects a PDF file, the following page is shown (from #6233):
But the user has no way of allowing this access. There should be some work-around to this problem, even if it is an
<input type=file>
to select the file (or a preference to disable interception of local files).The text was updated successfully, but these errors were encountered: