(Though the I2P thread <https://groups.google.com/a/chromium.org/g/blink-dev/c/9e9q5WAepGk/m/uw_XP5zuFAAJ> already has 3 LGTMs, there are some updates. Hence requesting another review) Contact emailsxiaoche...@chromium.org
Explainerhttps://drafts.csswg.org/css-counter-styles/#example-cce4b0db Specification https://www.w3.org/TR/css-counter-styles-3/#counter-style-speak-as Design docs https://bit.ly/3kEHluz Summary A custom counter style can be constructed with a meaning that is obvious visually, but impossible to meaningfully represent via a speech synthesizer or other non-visual means, or possible but nonsensical when naively read out loud. The 'speak-as' descriptor describes how to synthesize the spoken form of a counter formatted with the given counter style. *Update since I2P:* The 'spell-out' value is not implemented because it is currently unimplementable (crbug.com/1247764). As the spec requires alphabetic counter styles with 'speak-as: auto' to use the 'spell-out' value, we use 'words' instead. This aligns with what Firefox currently does. Blink componentBlink>CSS <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> Search tagscss <https://chromestatus.com/features#tags:css>, counter <https://chromestatus.com/features#tags:counter>, counter-style <https://chromestatus.com/features#tags:counter-style>, speak <https://chromestatus.com/features#tags:speak>, speak-as <https://chromestatus.com/features#tags:speak-as> TAG reviewN/A; Firefox already shipped it years ago. TAG review statusNot applicable Risks Interoperability and Compatibility Interoperability risks are very low, as we are implementing a CR feature that Firefox already shipped years ago, and Safari is positive on. *Update since I2P:* There is a low compatibility risk. Accessible names of a lot of predefined counter styles are changed from the counter text to the counter number. For example, if we have a list marker "IV. " using 'upper-roman' counter style, its accessible name is changed from "IV. " to "4. ". This change matches the spec and aligns with Firefox, but may shave backward compatibility risks. Gecko: Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=966166) Firefox didn't implement the 'spell-out' value, and uses the 'words' value instead. WebKit: Positive ( https://lists.webkit.org/pipermail/webkit-dev/2021-February/031719.html) Safari is positive on the @counter-style rule as a whole, including this descriptor. Web developers: Strongly positive ( https://bugs.chromium.org/p/chromium/issues/detail?id=687225) Developers are positive on the @counter-style rule as a whole, including this descriptor. Debuggability N/A; it's an extension to an already shipped feature, @counter-style. Note that we don't have DevTools support for @counter-style yet, as the requirement was imposed after @counter-style was shipped. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> ?Yes Flag name--enable-blink-features=CSSAtRuleCounterStyleSpeakAsDescriptor Requires code in //chrome?False Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1166766 Estimated milestones 96 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5687059677184000 Links to previous Intent discussionsIntent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/9e9q5WAepGk/m/uw_XP5zuFAAJ This intent message was generated by Chrome Platform Status <https://www.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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFqEGhaNDEdFEVu-Bop%2B0W5eaMZNM%2BT8dqADwUEQ_2iD_R0gTQ%40mail.gmail.com.
