- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Mar 2021 16:01:52 +0000
- To: public-css-archive@w3.org
> walk up ancestors until it finds a value Sounds like it's already settled, but I'll emphasize anyway that this is something we should definitely not do. > sub in the serialization of the computed value We recently (-ish) invented the [equivalent token sequence](https://drafts.css-houdini.org/css-properties-values-api-1/#equivalent-token-sequence), so we can just re-use that for this. --- I've been trying to think about whether or not the new "cross property inheritance" proposed here creates any significant new problems (performance, complexity, etc) for style recalcs. I _think_ it should be fine. It's similar to situations that must anyway be dealt with via `var()` and explicit inheritance of non-inherited properties. This looks like a relatively "easy win", so I'm supportive, FWIW. :+1: -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2864#issuecomment-807004172 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 March 2021 16:01:54 UTC