- From: WebMechanic via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jan 2024 18:58:04 +0000
- To: public-css-archive@w3.org
@dbaron Thanks for your reply! I believe this makes sense :-) My thinking was: the CSS engine should-would eventually know anyway if any property is "valid" within a specific context as it has to render it at some point and decide if it knows what it's about. And we can already have a gazillion warnings abourt invalid / unsupported properties in the console -- like vendor prefixed stuff. But maybe this "path" is too expensive to follow in the initial parser level. Have a nice time. -- GitHub Notification of comment by WebMechanic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3559#issuecomment-1917694606 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 January 2024 18:58:07 UTC