Arabic subtending marks (U+0600..U+0603) render incorrectly in the beginning of a line
Reported by
saadat.m...@gmail.com,
Aug 22 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Use any of the Arabic subtending marks (U+0600..U+0603) + proceeding digits in the beginning of a line in an HTML document. What is the expected behavior? The subtending marks should be rendered *under* the proceeding digits. What went wrong? The subtending marks are rendered *after* the proceeding digits. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 52.0.2743.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 The incorrect rendering is seen only when the subtending mark + proceeding digits are the starting characters of a line. In the middle or end of a line, they render correctly.
,
Jan 12 2017
Might be better classified as an internationalization issue. This probably though has to do with font rendering in blink. Tagging as such.
,
Jan 12 2017
,
Mar 22 2018
It's been a while. Any update on this? :)
,
Apr 24 2018
Arabic subtending marks also render incorrectly when used with CSS counters. An example is attached. That only difference with the original issue is that with CSS counters, the rendering is always incorrect and it doesn't matter whether the <subtending marks + proceeding digits of CSS counter> are in the start, middle, or end of the generated content. The example file renders correctly in Firefox 59, but not in Chrome 66.0.3359.117. |
|||
►
Sign in to add a comment |
|||
Comment 1 by msrchandra@chromium.org
, Aug 23 2016Components: UI>Localization
Labels: OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
121 KB
121 KB View Download