- From: Sam Atkins via GitHub <noreply@w3.org>
- Date: Wed, 15 Oct 2025 18:50:32 +0000
- To: public-houdini-archive@w3.org
> [@janvarga](https://github.com/janvarga) actually [started implementing it](https://bugzilla.mozilla.org/buglist.cgi?bug_id=1981363%2C1980620%2C1981352%2C1981111%2C1981487%2C1991628%2C1991631%2C1976441%2C1976443%2C1992964%2C1857849%2C1988479%2C1990426%2C1978444%2C1976439%2C1981764%2C1990418%2C1988473%2C1990419%2C1979610%2C1965749%2C1990201&list_id=17726966) recently. 🎉 Excellent! > This approach already follows the “type-based reification” model you describe? The mapping is determined by value type rather than property name, so new properties generally require no additional reification code (only if there's no suitable value type). Yes, that sounds exactly like what I'm doing for Ladybird, just ours is C++ not Rust: Each of our internal `StyleValue` classes has a `reify()` method that returns a corresponding `CSSStyleValue` subclass (falling back to a direct `CSSStyleValue` if nothing else is defined). I haven't yet hit any cases that do require property-specific rules, though I'm still fleshing things out. -- GitHub Notification of comment by AtkinsSJ Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1159#issuecomment-3407816725 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 October 2025 18:50:33 UTC