- From: Vitor Roriz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2023 15:10:17 +0000
- To: public-css-archive@w3.org
vitorroriz has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-counter-styles-3] Should fallback use prefix/suffix of original style or fallback style? == Hi everybody, Counter styles specification says at https://www.w3.org/TR/css-counter-styles-3/#counter-styles: Note: [prefix](https://www.w3.org/TR/css-counter-styles-3/#descdef-counter-style-prefix) and [suffix](https://www.w3.org/TR/css-counter-styles-3/#descdef-counter-style-suffix) don’t play a part in this algorithm. This is intentional; the prefix and suffix aren’t part of the string returned by the counter() or counters() functions. Instead, the prefix and suffix are added by the algorithm that constructs the value of the [content](https://www.w3.org/TR/css-content-3/#propdef-content) property for the [::marker](https://www.w3.org/TR/css-pseudo-4/#selectordef-marker) pseudo-element. This also implies that the prefix and suffix always come from the specified counter-style, even if the actual representation is constructed by a fallback style. However, some related WPT tests (below) expects that the suffix and prefix come from the fallback style: imported/w3c/web-platform-tests/css/css-counter-styles/counter-style-at-rule/suffix-fallback.html imported/w3c/web-platform-tests/css/css-counter-styles/counter-style-at-rule/system-additive.html imported/w3c/web-platform-tests/css/css-counter-styles/counter-style-at-rule/system-alphabetic.html imported/w3c/web-platform-tests/css/css-counter-styles/counter-style-at-rule/system-extends.html imported/w3c/web-platform-tests/css/css-counter-styles/counter-style-at-rule/system-symbolic.html imported/w3c/web-platform-tests/css/css-counter-styles/counter-style-at-rule/fallback-cycle.html imported/w3c/web-platform-tests/css/css-counter-styles/counter-style-at-rule/descriptor-prefix.html I've created a related issue at the WPT repo (https://github.com/web-platform-tests/wpt/issues/38772) since there were related changes to the expected values here https://github.com/web-platform-tests/wpt/commit/90a953f4c4f0235160e96c8dd27d4a5e7638511d I'd like to clarify what the proper behavior should be. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8619 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 March 2023 15:10:19 UTC