- From: Gérard Talbot <www-style@gtalbot.org>
- Date: Tue, 27 Mar 2018 22:17:01 -0400
- To: Chris Lilley <chris@w3.org>
- Cc: W3C www-style mailing list <www-style@w3.org>
Le 2018-03-27 22:07, Gérard Talbot a écrit : > Le 2018-03-27 10:01, Chris Lilley a écrit : >> Out of 575 tests, just*5 *do not meet CR exit criteria: >> https://test.csswg.org/harness/results/css-fonts-3_dev/grouped/filter/1/ > > >> *font-variant-05* >> https://test.csswg.org/harness/test/css-fonts-3_dev/single/font-variant-05/format/html5/ >> Zero passes > > Such test has 6 subtests. So, it's not exactly the failure of a single > test by itself. > > FWIW, Chromium 64 and Firefox 52.7.3 passes 3 of those 6 subtests. Correction. 5 subtests. 2 passes out of 5 subtests. Gérard > > [snipped] > >> *test_font_feature_values_parsing* >> https://test.csswg.org/harness/test/css-fonts-3_dev/single/test_font_feature_values_parsing/format/html5/ >> Zero passes. >> Automatic, 116 subtests >> > > Found 301 tests > 301 Pass > with Firefox 52.7.3. I get a lot of warnings (presumably testing > invalid property values) and 2 content security report errors. > > line 7: <meta content="tests that valid @font-feature-values rules > parse and invalid ones don't" name="assert"> > > That test is missing the invalid flag. > > Gérard > >> However, @font-feature-values is at-risk in Fonts 3 and already ported >> to Fonts 4. >> >> Gecko has a weird "SecurityError" and only runs one subtest. >> Chrome 67: 10 Pass, 106 Fail
Received on Wednesday, 28 March 2018 02:17:42 UTC