As CSS allows fine control over font features using 'font-feature-settings' at the element level, Chromium-based browsers currently lack support for these properties within '@font-face' declarations. This feature supports the string-based syntax for font-feature-settings as defined in CSS Fonts Level 4. Invalid or unrecognized feature tags will be ignored per specification. No binary or non-standard forms are supported. As OpenType fonts become more widely adopted, this enhancement will improve typographic control, reduce redundancy, and support a more scalable, modern approach to web design.
CSS already provides a 'font-feature-settings' property for controlling OpenType features at the element level. However, Chromium does not currently support it within @font-face declarations, unlike Firefox and Safari. This limitation prevents developers from configuring font behavior during font loading, forcing redundant declarations across individual components or elements. Supporting these descriptors in Chromium would let developers define font behavior once—at the source—improving consistency, reducing repetition, and making it easier to verify applied settings through DevTools.