- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Apr 2022 00:24:01 +0000
- To: public-css-archive@w3.org
So I think the only question here is whether we want to update the resolution above (`spec content:none as having no effect on elements`) to additionally spec that `content:none` resolves to `normal` as part of having-no-effect. CC @graouts who implemented the recent WebKit commit that keeps it distinct (according to @Loirooriol above), in case they have opinions here, since they are alone on that for the moment (but that is nice & straightforward if it's web-compatible). -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6503#issuecomment-1089568308 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 April 2022 00:24:02 UTC