- From: Jan Varga via GitHub <noreply@w3.org>
- Date: Sun, 10 May 2026 09:36:29 +0000
- To: public-css-archive@w3.org
janvarga has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-typed-om-1] Reification spec appears out of sync with UA/WPT behavior == While implementing CSS Typed OM support in Firefox, we noticed several cases where the CSS Typed OM reification spec does not appear to match existing WPT coverage and interoperable browser behavior. In particular, the property specific rules in the spec do not always match how properties are reified in Chrome/Safari and validated by WPT tests. In practice, WPT behavior often appears to follow existing implementation behavior rather than the current spec text. This makes implementation difficult because the spec cannot always be used as the sole source of truth for Typed OM reification behavior. Some examples encountered while implementing support: * [stroke-dasharray](https://w3c.github.io/svgwg/svg2-draft/painting.html#StrokeDasharrayProperty) * [stroke-width](https://w3c.github.io/svgwg/svg2-draft/painting.html#StrokeWidthProperty) It would be useful to audit and reconcile: * interoperable browser behavior * existing WPT expectations * and the corresponding spec text so the spec, tests, and implementations describe the same reification behavior. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13907 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 10 May 2026 09:36:34 UTC