Feature precenence for ligatures incorrect per CSS Fonts 3
Reported by
ch...@w3.org,
Mar 22 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Example URL: https://test.csswg.org/harness/test/css-fonts-3_dev/single/font-variant-05/format/html5/ Steps to reproduce the problem: 1. https://test.csswg.org/harness/test/css-fonts-3_dev/single/font-variant-05/format/html5/ 2. 3. What is the expected behavior? All characters on all lines should display as check marks. This test is using a special font to check which OpenType features are enabled or disabled. What went wrong? The first three lines have two crosses. Setting ‘font-variant-ligatures’ properties will override the same properties set in the @font-face rule. But properties set there and not explicitly turned off or on later remain set. Tests interaction of font-variant descriptor, font-variant-ligatures property, font-variant shorthand property & font-feature-settings low-level property for ligatures, in accordance with steps 1,2,4 and 6 of section 7.2 Feature precedence https://www.w3.org/TR/css-fonts-3/#feature-precedence Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? No Does this work in other browsers? No Firefox Chrome version: 67.0.3377.0 (Official Build) canary (64-bit) (cohort: Clang-64) Channel: n/a OS Version: 10.0 Flash Version:
,
Mar 22 2018
,
Mar 22 2018
Able to reproduce the issue on reported chrome version 67.0.3377.0 and on the latest stable 65.0.3325.181 using Windows 10, Ubuntu 14.04 and Mac 10.13.1. We are able to see first three lines have two crosses which is considered as Bad behaviour. As this is seen from M60(60.0.3072.0) considering it as Non-Regression and marking it as Untriaged. Hence requesting someone from Blink team to have a look into it and help in further triaging. Thanks!
,
Mar 22 2018
,
Mar 23 2018
Thanks for the report Chris! Looks like we're getting it wrong here in the last two cases.
,
Mar 26 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ch...@w3.org
, Mar 22 2018