New issue
Advanced search Search tips

Issue 687886 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug

Blocked on:
issue skia:5228



Sign in to add a comment

Rendering issues with Kohinoor Bangla font at various font sizes

Reported by grigore....@gmail.com, Feb 2 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36

Steps to reproduce the problem:
Big size font render is wrong.

What is the expected behavior?

What went wrong?
Big size font render is wrong.
On appmart.pro on Hindi language.
Please see atached screenshots.

Did this work before? N/A 

Chrome version: 55.0.2883.95  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 24.0 r0

On safari Version 9.1.3 (11601.7.8) all is ok,
On Firefox Version 50.1.0 all is ok,


 
retina display error.png
983 KB View Download
non-retina display.png
498 KB View Download
Components: -UI Blink>Fonts
Hi,

If are need a video report I can provide.

Comment 3 by e...@chromium.org, Feb 2 2017

Cc: drott@chromium.org
Labels: Needs-Feedback
Hi, thanks for the report! Do you happen to use any font manager software?

Hi,

Nope, this bug was reproduced on multiple computers.
Labels: Needs-Milestone

Comment 6 by drott@chromium.org, Feb 3 2017

Reproducible here on 56.0.2924.76 on Sierra. 

Comment 7 by drott@chromium.org, Feb 3 2017

Cc: -drott@chromium.org kojii@chromium.org
Labels: -Needs-Feedback -Needs-Milestone M-57
Owner: drott@chromium.org
Status: Assigned (was: Unconfirmed)
Reproducible on ToT as well.

Reduction: http://codepen.io/anon/pen/wgjNwK 

<style>                                                                                                                                     
  .working {                                                                                                                                
   font-family: sans-serif;                                                                                                                 
   font-size: 3.999999em;                                                                                                                   
  }                                                                                                                                         
 .broken {                                                                                                                                  
   font-family: sans-serif;                                                                                                                 
   font-size: 3.9999999em;                                                                                                                  
   }                                                                                                                                        
</style>                                                                                                                                    
<div class="working">हमें</div>                                                                                                               
<div class="broken">हमें</div>

With fallback to the Kohinoor Devanagari font, on Retina display, at close to 4em, we fail to render the glyphs correctly. At this point, unsure why. At 8.1em, things start to work again.
Labels: -Type-Bug -Pri-2 Hotlist-Interop Pri-1 Type-Bug-Regression

Comment 9 by drott@chromium.org, Apr 4 2017

phistuck@, do you have other reproductions or comparison which shows that this is a regression?

Cc: bunge...@chromium.org
Labels: -Type-Bug-Regression Type-Bug
Labels: -Pri-1 Pri-2
Sorry, you are right, it is not a regression. Someone on chromium-discuss mentioned that they updated Chrome and it broke, so I updated this bug. But I can reproduce their case even in Chrome 27 on macOS (actually, it used to be even worse - 257px showed the same result).

Here is another case. This only happens in 128px - 256px font-sizes, but the outcome is the same as this, so I guess it is related.

data:text/html;charset=utf-8,<!doctype html><style> p { font-family: sans-serif; margin: 0; padding: 0; } .font-48 { font-size: 48px; line-height: 48px; } .font-72 { font-size: 72px; line-height: 72px; } .font-127 { font-size: 127px; line-height: 127px; } .font-128 { font-size: 128px; line-height: 128px; } .font-256 { font-size: 256px; line-height: 256px; } .font-257 { font-size: 257px; line-height: 257px; } </style> <p>In Google Chrome the Hindi type doesn't render correctly from 128px - 256px.</p> <p class="font-48">48px %E0%A4%B2%E0%A4%BE%E0%A4%87%E0%A4%9F</p> <p class="font-72">72px %E0%A4%B2%E0%A4%BE%E0%A4%87%E0%A4%9F</p> <p class="font-127">127px %E0%A4%B2%E0%A4%BE%E0%A4%87%E0%A4%9F</p> <p class="font-128">128px %E0%A4%B2%E0%A4%BE%E0%A4%87%E0%A4%9F</p> <p class="font-256">256px %E0%A4%B2%E0%A4%BE%E0%A4%87%E0%A4%9F</p> <p class="font-257">257px %E0%A4%B2%E0%A4%BE%E0%A4%87%E0%A4%9F</p>

Original discussion -
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-discuss/4u0a4RyMCU0
Actually, they did not write it, I got mixed up.
Hello,

I mentioned this issue on chromium-discuss and Phistuck pointed me to this board to add my findings to this bug report.

I am experiencing the same issue on Chrome Version 57.0.2987.133 (64-bit) / OSX 10.11.6

The code Phistuck pasted above comes from a codepen I created to isolate the issue. I stumbled upon the bug while working on a large type masthead for an international project we are about to launch.

It appears that sans-serif Hindi type between the sizes 128px - 256px will not render correctly. Only small fragments of the characters will render leaving the type unreadable. It's difficult to describe accurately so please see the attached screenshots for more detail.

Changing the browser zoom level will break any type that is visually within the 128 - 256px range. For example, if I have 127px type that is rendering correctly and I zoom in one step (110%), the 127px type will be visually closer to 140px and will only render small fragments of the type (broken). Changing the zoom back to 100% will 'fix' the broken type.

Codepen with test case: https://codepen.io/anon/pen/vxvwya?editors=1100

Screen Shot 2017-04-03 at 9.08.23 AM.png
329 KB View Download
Screen Shot 2017-04-03 at 8.47.27 AM.png
276 KB View Download
Thanks, milesryan@ for the additional test cases.

Is the font "Kohinoor Bangla" or "Kohinoor Devanagari"? If so, this may be the same as https://bugs.chromium.org/p/skia/issues/detail?id=5228 . For some yet unknown reason CoreGraphics seems to draw these incorrectly sometimes depending on how it is called.
I first encountered the issue when using Helvetica Neue. It seems to only be an issue with sans-serif fonts.
Looking at the codepen in comment #15 the requested font is Helvetica, but Helvetica doesn't have Hindi glyphs. The fallback font chosen on may machine is "Kohinoor Devanagari" (Inspect > Computed > Rendered Fonts).

This is probably the Skia bug mentioned in comment #17. For some reason it appears the glyphs are being drawn somewhat backwards and wonky for some reason (you just can't see that here because we don't let the glyphs draw outside their bounding box).
Ah yes, when I follow the same steps I can see that the Rendered Font is Kohinoor Devanagari. You are correct, this is related to the Skia bug mentioned.
Blockedon: skia:5228

Comment 22 by drott@chromium.org, May 11 2017

Summary: Rendering issues with Kohinoor Bangla font at various font sizes (was: Big size font render is wrong)

Comment 23 by drott@chromium.org, May 11 2017

Cc: drott@chromium.org ligim...@chromium.org
 Issue 720052  has been merged into this issue.

Comment 24 by drott@chromium.org, Jun 30 2017

Status: ExternalDependency (was: Assigned)
Fixed in mac os 10.13b2 according to https://bugs.chromium.org/p/skia/issues/detail?id=5228#c19
Status: Fixed (was: ExternalDependency)
I'm marking this fixed, since the original test case now works properly on 10.13. Note that the issue is still present in older versions of macOS.

Sign in to add a comment