This feature seems to be marked at-risk due to implementation complexity. It isn't clear whether this would mean that to implement this, some features have to be less performant. Do you expect that this feature adds any performance problems?
I also had a question about the lack of Web Developer signals: are there any that you know of? Thanks! Vlad On Monday, June 16, 2025 at 10:44:09 AM UTC-4 Daniil Sakhapov wrote: > Contact emailssakha...@chromium.org > > ExplainerNone > > Specificationhttps://drafts.csswg.org/css-content/#content-property > > Summary > > counter() and counters() in alt text of 'content' property is useful to > provide more meaningful information to e.g. pseudo elements to improve > their accessibility. > > > Blink componentBlink>CSS > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> > > TAG reviewNone > > TAG review statusPending > > Risks > > > Interoperability and Compatibility > > It's currently "At risk" https://github.com/w3c/csswg-drafts/issues/10387 > > *Gecko*: No signal ( > https://github.com/mozilla/standards-positions/issues/1253) > > *WebKit*: No signal ( > https://github.com/WebKit/standards-positions/issues/515) > > *Web developers*: No signals > > *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 > > None > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, ChromeOS, 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 > > http://wpt.fyi/css/css-content/parsing/content-counter-valid.html > http://wpt.fyi/accname/name/comp_name_from_content.html > http://wpt.fyi/accname/name/comp_name_from_content_alt_counter_invalidation.html > > > > Flag name on about://flagsCSSAltCounter > > Finch feature nameNone > > Non-finch justificationNone > > Rollout planWill ship enabled for all users > > Requires code in //chrome?False > > Tracking bughttps://issues.chromium.org/issues/417488055 > > Estimated milestones > DevTrial on desktop 138 > DevTrial on Android 138 > > Anticipated spec changes > > Open questions about a feature may be a source of future web compat or > interop issues. Please list open issues (e.g. links to known github issues > in the project for the feature specification) whose resolution may > introduce web compat/interop risk (e.g., changing to naming or structure of > the API in a non-backward-compatible way). > None > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5185442420621312?gate=5133455599599616 > > 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/66360fae-b090-44f1-8743-307b046933bfn%40chromium.org.
