-
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
"The provided value 'moz-chunked-arraybuffer' is not a valid enum value... " #6306
Comments
This should have been fixed by #5531 are you using a pdf.js newer than that? |
I can conform the
However it is merely a warning Chrome displays during feature detection and doesn't indicate any sort of error. #5531 only remove feature detection for Chrome and Firefox build but not generic viewer so it doesn't really solve the warning for generic viewer. |
@CodingFabian the feature detection bit still occurs if |
Wait, why this is closed? I'm still getting the warning
on Chrome 44.0.2403.130 (64-bit) with pdf.js 1.1.377. |
See #5531 |
I'm using pdf.js-dist 1.1.377 and still get this warning. I'll debug this in a bit. |
You will get the warning but only once -- it will feature test ability to load data in chunks. |
I understand. I guess it's all working as expected then, and everyone can ignore the warning. It's really quite funny though that there should be one. |
There seems to be a lot to discuss, I reopen it. Sorry about what I've done. |
@qingzhengzhuma I think it's fine to close this issue. We still have a warning here (which I would consider an issue indeed), but we're looking at #6126 (comment) as a possible fix, we can discuss everything over there. |
Any updates on this warning? im still getting it... |
@lenichols This was fixed in #5531. Which version of PDF.js are you using? |
I am using Pre-built v1.3.91 and also getting the warning |
Ah, that is right. There is no warning in the Chrome extension, because that code is removed during the build. But it is present in a generic build because it is not known upfront Firefox, or some other browser is used. Just ignore that warning. |
I'm using v1.4.124 of pdf-dist from npm, and the warning |
getting same warning with v1.4.131..... |
@timvandermeij This message seems to bother a lot of people. Should we add a simple conditional check for Chrome (e.g. |
@Rob--W I agree that the message is not ideal. We want to avoid browser-specific code in the |
Working version of @Rob--W's suggestion which prevents the warning. pdf.worker.js - line: 8769
|
I'm still getting this warning... Using chrome 53 and latest pdf.js beta |
Still getting this warning on Chrome v55.0.2883.87 |
+1 |
3 similar comments
+1 |
+1 |
+1 |
locking the conversation (mostly because of +1's) |
Addressed by #8768 |
When I use PDF.js open a chinese document in chrome, part of contents in some pages are missed. the console tells "The provided value 'moz-chunked-arraybuffer' is not a valid enum value of interface XMLHttpRequestResponseType."(webL10n/l10n.js,L829) and "The provided value 'moz-chunked-arraybuffer' is not a valid enum value of interface XMLHttpRequestResponseType."(pdf.worker.js,L1649), the chrome version is 43.0.2357.132.
The text was updated successfully, but these errors were encountered: