Back in early April, I noticed something odd – no matter what I changes I made to our code for generating fonts, they would always appear the same in our tests’ HTML output as they did before the change.
I first assumed this was the IDE getting confused, but after clearing all of its caches and doing a full project rebuild the issue remained.
Next, I opened up the font files in OTMaster to see if they were different. They were! Furthermore, Firefox and Internet Explorer showed the changes with no problems, but Chrome, which I had been testing in, didn’t.
Of course, as it turns out, early April saw the release (and silent update) of Chrome 34, which unfortunately has introduced a font caching bug.
Click on Page A above, then come back here without closing it and click on Page B. You should see a square on both.
Now close both of the pages and repeat the process starting with Page B. This time both should show a triangle. (On occasion I’ve found that they’ll still both show a square.)
In any other browser, Page A should always be a square and Page B should always be a triangle.
The only difference between these pages is in the mapping values in the font – if a similar font is already open, Chrome will use that rather than reading the new font properly.
I’ve submitted a bug report, but for now I’m doing all of my Chrome testing on version 33. Big changes are coming to code for Chrome font rendering, so let’s see what version 35 brings!
Have you had any issues with Chrome? Let us know your thoughts.
Are you a Developer working with PDF files?
Our developers guide contains a large number of technical posts to help you understand the PDF file Format.
Do you need to solve any of these problems?
| Display PDF documents in a Web app |
| Use PDF Forms in a web browser |
| Convert PDF Documents to an image |
| Work with PDF Documents in Java |
