- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Sat, 18 Jun 2022 11:19:56 +0000
- To: public-css-archive@w3.org
> I'm not sure why the spec required them to be all one way or the other, as that restriction doesn't do anything productive. Because that is what CSS1 did. So there is an assumed Web compat issue (what content does, what scripts expect, what browsers implement since forever), although given other changes like the 0..255 form now allowing `<number>`, removal of commas, and addition of `none` it isn't clear that this is a strong argument. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7338#issuecomment-1159447119 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 18 June 2022 11:19:57 UTC