Jayson Harshbarger

Update Again!! I am seeing it on the public version of https://pdfviewer.net/ in Firefox when toggled to bleeding edge (pdfjs v4.3.620).

This is closest I've found to a similar issue against pdfjs: https://github.com/mozilla/pdf.js/issues/16287 Since this only an issue (for me) on the `-alpha` versions I'm ok to close it for now....

Will bleeding edge be 4.4 when you publish? Do you see any difference between stable and bleeding edge with the PDF attached here: https://github.com/mozilla/pdf.js/issues/16287 ? This is the same instance...

When you have a 4.4 bleeding-edge version I'll be glad to test it.

One more data-point then I'll give it rest for today. I cloned pdfjs and tested my PDF using the webviewer on both master and v4.3.136. Saw no issues in either...

> In the meantime, version 20.5.2 has landed. Any news from your side? I've been on Vacation; just getting back nopw. I will let you know.

I DO see the issue with 20.5.2; both stable (PDF.js: 4.3.659) and bleeding edge (PDF.js: 4.4.567) I DO see the issue with 21.0.0-alpha.2; both stable (PDF.js: 4.4.698) and bleeding edge...

@stephanrauh is there a way to run the basic viewer in stephanrauh/pdf.js? `npx gulp server` does not work in your fork.

It's difficult to determine if the issue is pdfjs, your fork of pdfjs or ngx-extended-pdf-viewer since they are all different versions. I don't see the issue on the pdf.js viewer...

I'm at a loss. I've gone through all the changes in stephanrauh/pdf.js vs mozilla/pdf.js multiple times. I don't see anything that looks suspicious. I think the only way to get...