After updating Chrome / Firefox browser to latest version PDF Viewer js doesn’t show barcodes / qrcodes.
In the browser console:
Warning: getOperatorList - ignoring errors during “GetOperatorList: page 0” task: “DataCloneError: Failed to execute ‘postMessage’ on ‘DedicatedWorkerGlobalScope’: function at() { [native code] } could not be cloned.”.
Hi,
Can you please send me the document you are using to reproduce this error.
Thanks!
Footer.pdf (17.5 KB)
Hi,
Please see attached the file in use.
It should be like this:
but doesn’t show barcode
Thanks
Having the same problem/message warning when uploded and viewed the PDF with build-in pdf.js viewer. PDF is showing up as a blank white pages while selecting some text, the content can be seen in the viewer.
Tested with
Firefox 90.0.2 (64-bit) - NOK
Chrome Version 92.0.4515.107 (Official Build) (64-bit) - NOK
Microsoft Edge Version 92.0.902.55 - NOK
Posting for reference:
Thanks everyone for the bug report. I can reproduce and will investigate!
Thanks for your patience,
Logan
Hi guys,
This error is coming from inside the pdf.js library we are using internally - I tested it out on the latest upstream version of pdf.js and it does not throw this warning. I tried merging the latest upstream version of pdf.js into our custom fork and it caused some issues that I am going to have to investigate.
This may take a bit of time so I am not going to fix this until after the upcoming 8.0 release, as that has top priority. I will keep you posted on this issue.
Thank you!
Logan
Hi Logan,
Document doesn’t loading in the VIEWER is the biggest issue for any customer.
So my question is, Whether 8.0 release will resolve this issue ?
If not then, This issue should be considered on top priority rather than any new release.
If yes then, In how many hours or days or weeks, 8.0 will be released ?
Because this issue cannot be keep open since long, hope you will understand my point.
Please revert when you gets online.
Warm Regards
Hi there,
As stated on our website, issues related to the PDF.js core are not technically supported by PDF.js Express, which is why I am making this a lower priority. It is also a lower priority because it only effects a small % of documents.
I will try a bit more today to see if I can find an easy fix, but if not then this will not be fixed in the initial 8.0 release but will be fixed in 8.0.1.
We plan on releasing 8.0 early next week.
Thanks!
Logan
Turns out I spoke too soon and I happened to stumble upon a fix. Chrome / firefox added an at()
function on arrays which broke some logic inside the pdf.js library.
I will push version 7.3.8 out today.
Thank you!
Logan
Hi Logan,
Thanks for the update. Will that resolve the Document Viewer issue, Right ?
Warm Regards,
Kartik
Correct, it fixes that warning and renders the PDF properly.
if you want, you can send me the document you are testing with and I can test it out before I release just as a sanity check.
That’s great… PFA of the same.
Please let me know if that works for you or not.
3429 Edward Don_ Inv- 0026893584 PO Bev.pdf (24.5 KB)
Warm Regards,
Kartik
Could you please confirm the same document on Internet Explorer and Safari as well?
Hey,
Document works in Safari FF and Chrome - we do not officially support IE11 but it should work there as well too.
Will push patch after code review.
Thanks!
Logan
Thanks for the update, please let me know here, as soon as you push new release, as integration at myside with testing on the live site, will take some efforts.
Hi,
Just pushed 7.3.8 which fixes the issues.
Thanks for the bug report and the sample documents everyone!
Logan
Things are working with Viewer now.
However on the separate note, I am facing an issues while loading the documents on Safari and IE-11, and that could be due to my code ECMA script transpile issues, however I am not sure.
Could you please guide me on the same? that would be big help and truely apreciated…!!
Hi Logan,
Can you please revert on my above message?
Warm Regards
Hi,
Express is heavily tested inside both IE11 and Safari, so the issue must be coming from your end.
Unfortunately I cannot be of help here unless you can prove that the issue is coming from inside PDF.js Express.
If you do find an issue with Express, please open a new bug report.
Thanks!