New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: Fixed
Closed: Jun 2016
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression

issue 62400

Sign in to add a comment

In Google Chrome 52 or above this PDF shows garbled texts.

Reported by, Jun 6 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.10 Safari/537.36

Steps to reproduce the problem:

What is the expected behavior?
Japanese texts are shown.

What went wrong?
Only garbled texts are shown. I can not read it even though I am a Japanese.

Did this work before? Yes Version 51

Chrome version: 52.0.2743.10  Channel: n/a
OS Version: 6.3
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by, Jun 6 2016
is another example, where Google Chrome 52 shows garbled texts.
Labels: M-52
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Chrome Beta# 52.0.2743.24 and Chrome Dev# 53.0.2756.0 on Windows.
This is a Regression issue in M52, below is the info,
Chrome Good Build: 52.0.2738.0
Chrome Bad  Build: 52.0.2739.0

Suspecting Commint# 08e9434b6f4938517755815da37752b0cd906be7
Suspecting Review URL#
@dsinclair -- Could you plese look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Note: The pdf is seen without any garbage text on Mac and Linux.

Thank You.
Project Member

Comment 4 by, Jun 6 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit - Your friendly Sheriffbot
Blocking: 62400
Components: Internals>Plugins>PDF
This renders correctly if XFA is turned off but fails when enabled.
Labels: -M-53
Removing the milestone because XFA has been disabled.
Status: Started (was: Assigned)
May I add your example PDF to our corpus of test files?
Fix out for review:

It looks like the issue is, when XFA is enabled, we don't load up the font maps, so when we lookup the characters to get the glyphs to display we decide the font is not unicode and just return the character. We then display the incorrect glyph. Loading the font maps fixes the issue.
Status: Fixed (was: Started)

Sign in to add a comment