Re: [csswg-drafts] [css-conditional] [css-contain] Fleshing out @container queries with single-axis containment (#5796)

@mirisuzanne Thanks for the clarification. I think.... I may be misunderstanding what @cssinate means by scope, or a fundamental piece of this proposal.

I guess maybe what you're saying is that you can limit the scope of a query by placing the scope within the realm of the `@container` query.

So, I think what you're saying is that you don't _need_ a selector because you can already say, via the child selector within `@container`, to only apply the query based on, say, the fact that `.elementSelected` is a descendent of `.theScopeIWant`? 🤔  i.e. given this CSS:
```css
@container (width > 45em) {
  .theScopeIWant .elementSelected {
    ...
  }
}
```
One of the things I tried to illustrate with my proposal is that everyone thinks about this problem very differently! If I misunderstood some of the fundamentals of your proposal, I apologize! I honestly feel this is a far cleaner syntax than what I proposed, but it seems my fear that someone wouldn't get the mental model right should have been self-applied lol.

So to clarify, this:
```css
@container (width > 45em) {
  .card { ... }
  h2 { ... }
}
```
is essentially similar to:
```css
.card:container(width > 45em) { ... }
h2:container(width > 45em) { ... }
```
In that, it applies to`.card` and `h2` given that they would be rendering in a space (or container?) that is > 45em?

I think this is such a departure from previous proposals that maybe I didn't quite get it. That being the case, I'm not sure another issue needs to be raised because I'm not sure there is one? If I misunderstood (and am understanding it better now?) then I'm happy to remove my previous post so that I don't confuse anyone else.

Thanks for taking the time to respond!

-- 
GitHub Notification of comment by matthew-dean
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5796#issuecomment-778452687 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 12 February 2021 21:01:14 UTC