Hi Sejal,

It's great to the progress on this, I believe it's one of the most highly
upvoted font-related features.

https://chromestatus.com/feature/5102801981800448 still doesn't show up in
the list of features to review/approve, please feel free to reach out off
list if you can't find the right buttons to press.

Best regards,
Philip

On Wed, Jul 2, 2025 at 4:51 PM Daniel Bratell <bratel...@gmail.com> wrote:

> This does not show up on the API Owner dashboard in Chromestatus so maybe
> you have missed pushing it there? There are some other reviews that should
> be started there at the same time.
>
>
> /Daniel
>
>
> On 2025-07-02 07:04, 'Sejal Anand' via blink-dev wrote:
>
>
>
> The review for the font-variation-settings CL
> <https://chromium-review.googlesource.com/c/chromium/src/+/6582382>
> <https://chromium-review.googlesource.com/c/chromium/src/+/6582382>is
> currently underway. Due to notable differences in implementation and
> interoperability, I have created a separate Chrome status entry for it. If
> necessary, we can wait until the variation settings CL is merged.
>
> Thank you,
> Sejal
>
>
> ------------------------------
> *From:* 一丝 <yio...@gmail.com> <yio...@gmail.com>
> *Sent:* Monday, June 30, 2025 2:22 PM
> *To:* blink-dev <blink-dev@chromium.org> <blink-dev@chromium.org>
> *Cc:* Sejal Anand <sejalan...@microsoft.com> <sejalan...@microsoft.com>;
> Ragvesh Sharma's Organization (FTE) <ragvesh_org_...@microsoft.com>
> <ragvesh_org_...@microsoft.com>
> *Subject:* [EXTERNAL] Re: Intent to Ship: Support font-feature-settings
> descriptor in @font-face rule
>
>
> You don't often get email from yio...@gmail.com. Learn why this is
> important <https://aka.ms/LearnAboutSenderIdentification>
>
> Thanks for your work, this is a feature that Blink has been lacking for a
> long time, very much looking forward to it!
>
>
> Are you planning to ship the `font-variation-settings` together? We hope
> they can be released together.
>
> 在2025年6月29日星期日 UTC+8 15:57:03<sejal...@microsoft.com>
> <sejal...@microsoft.com> 写道:
>
>
>
> Contact emails
> sejal...@microsoft.com
>
> Explainer
> None
>
> Specification
> https://www.w3.org/TR/css-fonts-4/#font-rend-desc
>
> Summary
> 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.
>
> Blink component
> Blink>Fonts
> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EFonts%22>
>
> Motivation
> 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.
>
>
> Initial public proposal
> None
>
> TAG review
> None
>
> TAG review status
> Not applicable
>
> Risks
>
>
> Interoperability and Compatibility
>
>
> *Gecko*: Shipped/Shipping (
> https://bugzilla.mozilla.org/show_bug.cgi?id=1355366)
>
> *WebKit*: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=63618)
>
> *Web developers*: Positive (
> https://stackoverflow.com/questions/27486680/how-to-set-default-font-feature-settings)
> Over 30 users have indicated that they are affected by this issue and its
> related duplicates, as noted in
> https://issues.chromium.org/issues/40398871 and
> https://issues.chromium.org/issues/324519293
>
> *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?*
> None
>
>
> Debuggability
> Existing DevTools capabilities already cover this.
>
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ?
> Yes
>
> https://wpt.fyi/results/css/css-fonts/font-feature-settings-descriptor-02.html?label=master&label=experimental&aligned
>
> https://wpt.fyi/results/css/css-fonts?label=master&label=experimental&aligned&q=font-feature-settings-descriptor-binary.html
>
>
> Flag name on about://flags
>
>
> Finch feature name
> FontFeatureSettingsDescriptor
>
> Requires code in //chrome?
> False
>
> Tracking bug
> https://issues.chromium.org/issues/40398871
>
> Estimated milestones
> Shipping on desktop
> 139
> Shipping on Android
> 139
> Shipping on WebView
> 139
> Shipping on iOS
> 139
>
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5102801981800448?gate=5099341546782720
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com/>.
>
>
>
> --
> 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 visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PU5P153MB14158A2C9018D6DA22EA62F1D440A%40PU5P153MB1415.APCP153.PROD.OUTLOOK.COM
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/PU5P153MB14158A2C9018D6DA22EA62F1D440A%40PU5P153MB1415.APCP153.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>
> .
>
> --
> 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 visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/16078d9e-7d05-49f3-be85-3aaf6d4223a6%40gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/16078d9e-7d05-49f3-be85-3aaf6d4223a6%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYc5DXw12jErMUPhG3ic0bFfk8avt2L9R4DODzw7pGtBWg%40mail.gmail.com.

Reply via email to