text-align justify broken with space-kerning
Reported by
karima...@gmail.com,
Feb 9 2017
|
|||||||||
Issue descriptionUserAgent: 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: Steps to reproduce the problem: 1. Go here to download the font with a test-page: https://dl.dropboxusercontent.com/u/1294856/jnnk_space.zip 2. Unzip the zip-file and open jameel-kern-test.html 3. Notice extra space visible at the beginning of every sentence from right despite the text being in RTL direction. 4. The issue is non-existing on other browsers such as FireFox, Edge etc. What is the expected behavior? Space-characters that are kerned should not be visible from the beginning of every sentence on the right side. What went wrong? Space-characters that are kerned should render as programmed in the font, and not lineup on the right side of every sentence. 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
,
Feb 10 2017
ccing the dev from 690288 to get more inputs on this issue.
,
Feb 10 2017
,
Feb 10 2017
,
Feb 10 2017
This bug is marked as duplicate and then closed. In fact its unrelated to other issue which actually had a workaround in CSS. This one has none and its a very real space-rendering bug in Chrome. I therefore kindly request developers to reopen the case for further investigation.
,
Feb 11 2017
Reopening as requested. eae@, I think this issue is filed as a separate bug from the issue 690288 , which karimarif@ wrote on #c4 on issue 690288 . The kerning itself is working as expected, but this is reporting a different issue (spaces), which resulted in different renderings from Edge/Firefox. If this is working as expected, could you describe why?
,
Feb 13 2017
Able to reproduce the issue on windows-7 using chrome stable version 56.0.2924.87 and canary 58.0.3010.0 This is regression issue broken in M35.Please find the bisect information as below Narrow Bisect:: =============== Good :35.0.1849.0 Bad:: 35.0.1851.0 Got changelog from Omahaproxy: ChangeLog: https://chromium.googlesource.com/chromium/src/+log/35.0.1849.0..35.0.1851.0?pretty=fuller&n=10000 Unable to find the suspect from above CL.Could some one from Dev team please help us to assigning to right owner. Thanks..
,
Feb 13 2017
,
Feb 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 13 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by kochi@chromium.org
, Feb 10 2017