- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 May 2022 19:12:37 +0000
- To: public-css-archive@w3.org
> Oh, interesting. Is there an explainer for this that demonstrates the visual effect of applying different `container-type` properties? @matthew-dean I think this behavior is described in several places, but I don't know if any of those descriptions really 'demonstrate the visual effect' in a simple & clear author-centered way. That would be a good example to have somewhere. We could consider adding a note/example to the spec, but it will be even more helpful to call out in articles about the feature. > Less has a syntax for "adding values" to existing list values, as well as a keyword like all which applies all items from a possible list. There are several other open issues about that exact idea, and I think we do need something like that. But I don't see any reason to define it in a way that is specific to container queries. It's something we would want to define generically for all list values, and should be handled elsewhere. --- @astearns I think it would make sense to bring this issue back to the group? With several implementors arguing against the current behavior, and several browsers preparing to ship the feature, it seems important to discuss the tradeoff they bring up. I think this issue needs to be resolved before any version of the feature can be shipped, since it impacts the default value of the property? - on the one hand, in order for style queries to be useful on inherited properties, authors will want style containment set globally. If that is an author setting, they will also need to be careful not to override it when adding `size` containers. Since size CQs are likely to launch before style CQs, this will create some unexpected difficulties for authors once both are supported. It's not as simple as adding the global `style` value, it will also have to be added to every instance of `container-type` that might accidentally override that global setting. If we go that rout, we need to clarify that the default style-container behavior is not overridden by author values ([as described by fantasai](https://github.com/w3c/csswg-drafts/issues/7066#issuecomment-1042410631)). - on the other hand, it sounds like this desired behavior may cause performance issues for browser engines. I think we've made the right choice about how the syntax should ideally work for authors. But, of course, performance is also important to authors. It's not clear to me how those concerns should be balanced, or how bad the performance impacts would be, but I'd like to resolve that question one way or the other so that we don't accidentally paint ourselves into a corner. In either case, this issue needs clarification in the spec. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7066#issuecomment-1135043695 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 May 2022 19:12:38 UTC