Issue metadata
Sign in to add a comment
|
list-style: inside full stop kerning |
||||||||||||||||||||||
Issue descriptionChrome Version: 64.0.3273.0 (Official Build) canary (64-bit) OS: macOS 10.12.6 The following two fragments render differently with regards to the kerning between the counter character and the full stop: <ol style="list-style: lower-greek inside; padding: 0; margin: 0;"> <li style="padding: 0; margin: 0;"></li> </ol> and: <p style="padding: 0; margin: 0;">α. </p> Note this doesn't happen with all counter styles: it notably doesn't reproduce with decimal or decimal-leading-zero, and for some doesn't reproduce at 96dpi (though does at higher dpi). As the early draft of Lists 3 says, "The contents of the ::marker are a text run containing the prefix of the <counter-style>, followed by the result of generating a counter representation for the <counter-style> and the value of the list-item counter on the originating element, followed by a text run containing the suffix of the <counter-style>".
,
Mar 6 2018
This is basically about issue 6122, but I'm not sure if I can read what are the expected behavior from the quoted text in #0. It says UA should create three separate runs, one for the prefix, one for the counter text, and one for the suffix. In our current layout engine, we don't support prefix, but we do create two runs; one for the counter text and another for the suffix. Because they're separate runs, we don't apply kerning between them due to issue 6122. We're looking forward to fix issue 6122 in LayoutNG, but when the spec says UA should split the text runs, and IIUC there's no mention about whether to apply kerning between separate text runs, should the kerning apply or not? IIUC, this isn't defined, but is about the quality of implementation, which we'd like to improve in LayoutNG. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by e...@chromium.org
, Nov 30 2017Status: Assigned (was: Untriaged)