- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Oct 2021 12:19:38 +0000
- To: public-css-archive@w3.org
If toggle() can be replaced with something else then it's fine, but this issue doesn't mean that it's unsalvageable. I guess toggle() in a shorthand should set the longhands to a pending-toggle-resolution internal value, that would serialize as empty string and cascade as normally. At computed value time we would resolve that by taking the shorthand, and evaluating it to each of the values in toggle(). If all longhands would have the same computed value as the parent element, then it's a match. Then we pick the corresponding longhand component of the next toggle value. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6764#issuecomment-951882186 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 October 2021 12:19:40 UTC