-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot view local files in Chrome extension with fetch API #9361
Comments
I don't think this is just a chrome specific issue. We can't use |
@mukulmishra18 When you talk about "Firefox", are you referring to the built-in viewer of Firefox? |
Yes, right. |
But the built-in viewer in Firefox doesn't use |
Oh! I got it. Sorry. |
The `fetch` API is only supported for http(s), even in Chrome extensions. Because of this limitation, we should use the XMLHttpRequest API when the requested URL is not a http(s) URL. Fixes mozilla#9361
The `fetch` API is only supported for http(s), even in Chrome extensions. Because of this limitation, we should use the XMLHttpRequest API when the requested URL is not a http(s) URL. Fixes mozilla#9361
The `fetch` API is only supported for http(s), even in Chrome extensions. Because of this limitation, we should use the XMLHttpRequest API when the requested URL is not a http(s) URL. Fixes mozilla#9361
I have built the latest version of the extension, and tried to open a local PDF file. It won't open, the console shows the following error:
To fix this, the Chrome extension must only use PDFFetchStream for http(s) schemes, and PDFNetworkStream for other schemes (file, ftp).
The text was updated successfully, but these errors were encountered: