(re-sent from @chromium.org address) Contact emailsdr...@chromium.org
ExplainerNone Specificationhttps://www.w3.org/TR/css-fonts-4/#font-face-src-parsing Summary CSS Fonts Level 4 provides additional means of selecting or filtering font resources. The tech() function was introduced, which allows passing in a list of font technologies that this respective font blob requires to function. Based on that, the UA will select the first suitable resource. I will hold shipping until one remaining clarification is reached on whether the keywords should be phrased in singular or plural form, compare item 3 in https://github.com/w3c/csswg-drafts/issues/7633. *Motivation* With COLRv1 font supports, it's now more important to give authors an opportunity to check feature support. Doing this in the tech() function in the src: descriptor of @font-face is one useful tool for incremental upgrade of the user experience. If the UA supports COLRv1 or other new font technologies, the richer font is loaded, otherwise fallback occurs. Blink componentBlink>Fonts <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFonts> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/666 TAG review statusIssues addressed Risks Interoperability and Compatibility *Gecko*: Positive https://github.com/mozilla/standards-positions/issues/563 *WebKit*: No signal *Web developers*: In discussions with partners before launching COLRv1, feature detection for COLRv1 was a requested functionality. The src: line tech() function is one way to achieve that. *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? Debuggability Limited debuggability but unchanged to before: @font-face declarations are viewable as source in DevTools, but otherwise no particular tooling support is provided. However this is unchanged from before, as this change only affects the syntax inside the @font-face src: line. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes, initial tests provided by Jonathan Kew from Mozilla, which I then updated, see https://github.com/w3c/csswg-drafts/issues/7633 and https://github.com/web-platform-tests/wpt/pull/35681 Flag nameCSSFontFaceSrcTechParsing (Blink RuntimeEnabledFeatures flag) Requires code in //chrome?No Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1216460 Estimated milestones 107 Anticipated spec changes See above, holding shipping until clarification is reached on singular or plural naming of features- keywords. Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5088679224147968 -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN6muBt-z-JzrBdL%3D%3DREQVASX_x74iPP2BRfw%2BWP82jP7qVdHA%40mail.gmail.com.
