-
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
Chrome extension is broken #3167
Comments
I take my previous comment back: extension is broken and it does it on all documents. |
You can EDIT the issue contents. You can also use <del>something</del> to strikethrough it. In firefox, it shows: The chrome issue may be related to the #2719 PR? |
No, I left the original message on purpose since I strongly suspect this is a failure too. |
Chrome extension definitely broken and I get the same error on any PDF I try to load. On http://nodejs.org/trademark-policy.pdf that Firefox Aurora successfully loads Chrome Canary on OS X returns:
and for the Harpers PDF above
I get the same results on Chrome Canary and Dev on both OS X and Xubuntu Linux. |
The error points to line 35028 of pdf.js inside the getPdfManager function specifically on the var networkManager ... line
|
Ah - this is a problem with node make extension - #3127. node make chrome fixes the problem and I'm good to go. |
dup #3127 |
This pdf:
http://harpers.org/wp-content/uploads/HarpersMagazine-1994-07-0001729.pdf
fails in chrome plugin, instead of showing the document it shows the gray screen, even no error message.
Version from 1 month ago showed the error message complaining about some attribute.
The text was updated successfully, but these errors were encountered: