New issue
Advanced search Search tips

Issue 690288 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Kering of space-character is not working in Chrome

Reported by karima...@gmail.com, Feb 9 2017

Issue description

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

Example URL:

Steps to reproduce the problem:
1. Go here to download the font with a test-page:
https://dl.dropboxusercontent.com/u/1294856/jnnk.zip
2. Unzip the zip-file and open jameel-kern-test.html
3. Highlight any text, right-click and choose inspect.
4. Kerning is on by default, yet the space-character between words is not kerning.
5. The issue is non-existing on other browsers such as FireFox, IE, Edge

What is the expected behavior?
Space-character between words should kern as programmed in the font.

What went wrong?
Space-character is not kerning at all. Chrome is ignoring kerning feature on that particular unicode-character.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 56.0.2924.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

 
Chrome.jpg
422 KB View Download
Firefox.jpg
229 KB View Download
Labels: Needs-Triage-M56

Comment 2 by kochi@chromium.org, Feb 9 2017

Components: -Blink Blink>Fonts Blink>Layout
Labels: -OS-Windows OS-All
Status: Untriaged (was: Unconfirmed)
The provided repro case (jnnk.zip) works on Linux as well - it's
generic to webfont and its rendering.  I'm not sure kerning belongs
to layout or font, so assigning both components. Feel free to change
to the correct component.

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

Status: WontFix (was: Untriaged)
Chrome disables kerning for space characters to improve performance by default, this was an intentional decision to balance performance and appearance.

When kerning is explicitly turned on using "font-kerning: normal;" or the "text-rendering" mode is changed to either "optimizeLegibility" or "geometricPrecision" the optimization is disabled and kerning for space is respected.

Adding either of those three properties makes the page render the same in Chrome as it does in Firefox.

font-feature-settings are transparent to chrome and are not used to make decisions like this. We might want make "font-feature-settings: 'kern' 1;" trigger the same behavior but realistically that is not something we'll do in the near to mid-term.

For now please use one of the following style rules to get the desired behavior:

font-kerning: normal;
text-rendering: optimizeLegibility;
text-rendering: geometricPrecision;


Thanks for help. Making above changes in CSS did bring back kerning for space-character but unfortunately it's still not rendering as expected. All the kerned-spaces are now moved to the right side of sentences. Is it expected behavior or a very serious text-rendering bug? Check snapshot to reproduce the bug.
Chrome_kerning.jpg
650 KB View Download

Comment 5 by e...@chromium.org, Feb 10 2017

Cc: e...@chromium.org
Issue 690644 has been merged into this issue.
I would note here that the text shown in these screenshots is in Urdu language which has an RTL (Right to Left) direction script.

Sign in to add a comment