- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2022 22:48:34 +0000
- To: public-css-archive@w3.org
> Agenda+ to decide if we want to make `none` compute to `normal` on regular elements, or keep them as distinct values with identical behavior. [tl;dr: we may already be interoperable on them being distinct values, so maybe we should stick with that?] Looking at the two most recent contentful comments here, it seems like Gecko and Chromium **both** have these keywords implemented as distinct computed values right now. This just wasn't easily-observable in Chromium, because as @Loirooriol said, `content:inherit` was nerfed Chromium (which was a bug/TODO to be eventually fixed). (I also tested WebKit using Mats' [testcase from his comment above](https://github.com/w3c/csswg-drafts/issues/6503#issuecomment-897234696) but it just renders with a single bullet, so I'm not sure they have this implemented at all right now.) So I think maybe the existing implementations are interoperable on these keywords being distinct computed values, aside from that Chromium bug about `content` not inheriting. Do I have that correct? (@Loirooriol , please correct me if I'm misunderstanding your comment.) -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6503#issuecomment-1082444062 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 March 2022 22:48:39 UTC