The font-synthesis CSS property controls whether user agents are allowed to synthesize oblique, bold and small-caps font faces when a font family lacks oblique, bold and small-caps faces, respectively.
Already shipped in other browsers, see below, no TAG review required.
Expected graceful degradation if an engine has so far not implemented this feature: if the font-synthesis: property is not understood by an engine, this means unintended synthesis can occur. That's expected and the reason why this property was designed.
WebKit: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=144180)
Web developers: No signals
None expected, feature already implemented in other browsers.
Same as any other CSS property, css_properties.json will be rolled to DevTools during development.
Yes, 36 new web tests pass: 16 new internal platform specific tests were added, 12 new WPT tests were added and 8 existing WPT tests are now passing.
No milestones specified
This intent message was generated by Chrome Platform Status.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAO7W_AmPR6X7evqGz9P7bkW2ysRmr%3DqP4ajgGA%2BjOGfsp_FrA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXyqaq60U%2BEzTWxYLhhZcW%3DyjZMetHjkgfmjpWibOWLxg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/948ab999-2298-be47-ecab-d9585ea31b22%40gmail.com.
> Looking at the font-synthesis-* tests in https://wpt.fyi/results/css/css-fonts?label=experimental&label=master&aligned, many pass in Firefox and Safari, but not all of them. Do all of these tests pass with the implementation now in Blink?
Yes, they do. Actually these tests had been added with the Chrome implementation and they are responsible for longhands for font-synthesis property which is not supported by other browsers yet.
> In the chromestatus entry I see "There are additional tests for system fonts with platform specific results, so we keep those as internal tests." Is the problem there that the tests rely on system fonts, or that there are platform-specific results? The latter is possible with WPT using the regular third_party/blink/web_tests/platform/ expectations. For system fonts, perhaps these tests could be written to pass if the fonts aren't present? If these are testharness.js tests, https://web-platform-tests.org/writing-tests/testharness-api.html#optional-features might be a path forward.
Yes, they rely on particular aspects of which fonts are available on the system. As the font-synthesis property, when applied to system fonts, is closely connected to font matching and identifying whether a true bold / true italic variant exists, it’d be hard to make those flexible in terms of a default passing when the font does not exist. They are ref tests for that purpose.
>Also, looking at https://developer.mozilla.org/en-US/docs/Web/CSS/font-synthesis#browser_compatibility I wonder if small-caps is going to be supported? If that table is correct it's not supported by Safari and it's only just now coming to Firefox.
Yes, small-caps support was also implemented in Blink (as longhand and as part of the shorthand). Also I’m not sure if that table is correct because Safari also supports ‘small-caps’ (only as a keyword in the shorthand) . They just have a bug in ref for this test: https://wpt.fyi/results/css/css-fonts/font-synthesis-06.html?label=experimental&label=master&aligned
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/28c6d529-d817-4d44-b710-2a40bfaeacc0n%40chromium.org.