web-features consumers report for 2025-10-01

[github-actions]

Chromestatus entries

• caret-shape used by https://chromestatus.com/feature/6106160780017664 (Add caret-shape CSS property feature #3453)
• feature-policy used by https://chromestatus.com/feature/6294138899136512 (Add features for permissions policy and feature policy #2661)
• feature-policy used by https://chromestatus.com/feature/5190687460950016 (Add features for permissions policy and feature policy #2661)
• feature-policy used by https://chromestatus.com/feature/5694225681219584 (Add features for permissions policy and feature policy #2661)

Source: chromestatus.com

Chromium use counters

• ReferenceTarget (draft) (Add the referencetarget feature #3376)
• ScopedViewTransitions (draft) (Scoped view transitions #3423)
• WasmBranchHinting (draft) (Add Wasm Branch Hinting #2744)
• WebAppManifestUpdate (draft) — Non-public thing? See: https://chromium-review.googlesource.com/c/chromium/src/+/6625093
• IncomingCallNotifications (draft) (Add feature for incoming call notifications #3466)
• WebInstallAPI (draft) (Add feature for app install API #3467)
• CrashReportStorageAPIInitialize (draft) (Add feature for crash reporting storage API #3468)
• WasmCustomDescriptors (draft) (Add Wasm Custom Descriptors #3244)

Source: webdx_feature.mojom

web-platform-tests

• mixin (Add feature for CSS mixins (@mixin, @contents, and @apply) #3465)
• viewport (Merge viewport/ into viewport-segments/ web-platform-tests/wpt#55429)

Source: WEB_FEATURES_MANIFEST.json

[ddbeck]

@foolip I was able to track something down for everything here but the WPT items. I think the process for each item in one of these reports should be:

• File a PR, if there are BCD keys or keys are very likely to exist soon (or link to an existing PR)
• File an issue (or link to an existing PR)

And check the items off, if they've been satisfied.

However, I wasn't sure how to do this for the WPT items. How do I use the new ID to learn something about why it was created in WPT? I don't really know what to do with the linked JSON.

[foolip]

For WPT, I'd work backwards from the tests by searching for feature:mixin on wpt.fyi:

https://wpt.fyi/results/?label=master&label=experimental&aligned&q=feature%3Amixin

So that's clearly about CSS mixins, and we should add a feature for https://drafts.csswg.org/css-mixins/#defining-mixins

https://wpt.fyi/results/?label=master&label=experimental&aligned&q=feature%3Aviewport is about viewport segments and looks like a mistakenly created directory in WPT. Fixed in web-platform-tests/wpt#55429.

[ddbeck]

This report is succeeded by #3455. I'm closing this one.