- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Nov 2022 20:04:05 +0000
- To: public-css-archive@w3.org
Thanks for the link. It makes sense that the target property should include the legacy value in its syntax for back compat. So the first case in my examples should not exist. What would you expect in the following situation? ```js style['--custom] = 'b' style.shorthand = var(--custom) style['--custom] = 'c' style.longhand; // ?? ``` I am not very comfortable with *of their own* because it prevents serializing a shorthand when all its longhand have been independently declared with the same custom variable (and the same fallbacks, if any). But comparing custom variables for checking equality seems non-trivial. But I am not sure this is the reason of this restriction. Anyway, I do not have a strong opinion on serializing the target longhand when the legacy shorthand is declared with `var()`, and you and other members of the CSSWG are way more experienced than me. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3109#issuecomment-1307763701 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 November 2022 20:04:07 UTC