You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using WinAnsiEncoding, which has an "at" value at the 64th index.
For the font Courier (the font that this is failing for), widthsByGlyphName has always been empty for this font. This means that the above line would evaluate to []["at"], which returned nothing in Chrome 91.
In Chrome 92, however, this actually returns the function / native code because the Array prototype (for that empty array) has an at method now. This is causing failures at a later point in the stack.
As a result, the overlaying text is not getting displayed to our users.
The text was updated successfully, but these errors were encountered:
Attach (recommended) or Link to PDF file here:
Configuration:
92.0.4515.107 (Official Build) (x86_64)
MacOs Big Sur version 11.3
2.4.456
false
Steps to reproduce the problem:
Sorry I don't have a PDF link to reproduce the issue but I can try to explain:
The breaking line of code is here:
pdf.js/src/core/evaluator.js
Line 3637 in 51f0a81
When using WinAnsiEncoding, which has an "at" value at the 64th index.
For the font Courier (the font that this is failing for), widthsByGlyphName has always been empty for this font. This means that the above line would evaluate to
[]["at"]
, which returned nothing in Chrome 91.In Chrome 92, however, this actually returns the function / native code because the Array prototype (for that empty array) has an at method now. This is causing failures at a later point in the stack.
As a result, the overlaying text is not getting displayed to our users.
The text was updated successfully, but these errors were encountered: