- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Sat, 03 Apr 2021 12:03:02 +0000
- To: public-css-archive@w3.org
I vote for an implicit fallback root option. My reasoning: with MQ it is a common practice (questionable, but exists) to define all the styles only for the appropriate scopes. If someone would apply this for the CQ, then if they would have an explicitly defined container, the styles would work perfectly. However, in case the container would lose its containing property or the component would be inserted somewhere without it, the styles would stop from working completely (or would lose some important parts if some of the common styles were moved outside of the CQ, but the important parts were divided by width scopes only). On the other hand, I can't think of a use case where authors would want to avoid the implicit fallback. > If we do not provide an implicit fallback, authors can always add root containment to create their own I find this a false assumption, if we're looking at a single component separated from any context, it can't set the containment around itself on its own. Making it so the authors are **required** to set the containment in every case makes the components much less reusable. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6178#issuecomment-812855974 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 3 April 2021 12:03:49 UTC