- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Apr 2019 14:19:30 +0000
- To: public-svg-issues@w3.org
Good to see some clarification here. As [I said in my initial review comments](https://lists.w3.org/Archives/Public/www-svg/2019Apr/0010.html), we need to be clear what exactly from CSS is supported, or not supported. In my initial comment, I said > probably means that it removes CSS selectors, CSS stylesheets, and > cascading. CSS properties and inheritance are still used. Having a defined whitelist of supported properties is an improvement. Allowing the style attribute might be valuable, although in the absence of internal or external style sheets it adds nothing compared to just presentational attributes, and adds complexity (comments, multiple declarations, specificity if the presentational attribute is also specified). I agree that internal and external stylesheets should be forbidden (and thus the `style` element), which also removes at-rules, selectors, and cascading. Restrictions on CSS Values and Units is probably a good idea, although I am unsure why `rgba()` should be disallowed (and note that CSS Color 4 now allows an optional alpha term even for `rgb()`.) -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/svgwg/issues/658#issuecomment-484530669 using your GitHub account
Received on Thursday, 18 April 2019 14:19:31 UTC