- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Jun 2021 11:55:14 +0000
- To: public-css-archive@w3.org
Investigating a bit more, looks like Chromium already behaves according to the new spec text. The reason Chromium appears to evaluate `not fn()` to false in the [demo](url) is because `not fn()` is actually invalid grammar. (`<any-value>`, requires **one or more** tokens). -- GitHub Notification of comment by andruud Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/6312#issuecomment-856699290 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 June 2021 11:56:22 UTC