- From: Fred Boyle via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 18:44:56 +0000
- To: public-css-archive@w3.org
@fergald I think both would be useful in a variety of scenarios. Components intended to be themed would benefit from the 'deny all except' approach while components that are meant to be more flexible would be best served by a 'allow all except' approach. The default, should nothing be defined, would be an 'allow all' mechanism from our perspective. Hope this helps you better understand our point of view. Do you believe this makes sense for the spec and potentially implementation? @emilio The thinking behind this is to allow greater ease of customization and "theming" of components while having guardrails in place to prevent breaking a component. -- GitHub Notification of comment by fredboyle Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3506#issuecomment-463317788 using your GitHub account
Received on Wednesday, 13 February 2019 18:44:57 UTC