- From: Matthew Sundberg via GitHub <sysbot+gh@w3.org>
- Date: Sun, 09 Mar 2025 07:36:43 +0000
- To: public-css-archive@w3.org
That *is* unfortunate. I'm sure maintaining a standard as complex and widely used as CSS means your hands are tied in a whole bunch of situations like these, but it sure would be handy if that didn't apply right now! Is there any slim hope for changing that syntax's interpretation since the proposed new behavior is so similar to the old one (resolve to the inherited value due to IACVT *vs.* resolve to the inherited value \*plus\* re-resolve var()s used with their fresh values)? Either which way, thank you for looking for solutions to the lazy/late resolving var problem, and also being so careful while you're at it. I've always considered CSS slightly magical, and maintaining backwards compatibility to the degree it does is a large part of that. :) -- GitHub Notification of comment by mwsundberg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11543#issuecomment-2708716388 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 9 March 2025 07:36:44 UTC