L. David Baron

Sorry, we got preoccupied with the cooperation agreement with W3C, and didn't end up cycling back to this issue afterwards. We'll try to think about this set of issues more...

This policy comes from whatwg/meta#84 and #72 (which I somehow managed to entirely miss).

I think this comment is from a personal perspective, since I originally raised this issue back when I was the AC Rep for a company that I no longer work...

So I'd like to give some reactions to this proposal. 1. As background, I should point out that one of the costs of doing container queries or element queries is...

I probably should have been clear that I meant [the CSS Containment spec](https://drafts.csswg.org/css-contain/). It currently contains some of the primitives that I think are needed, but not all of them:...

So if I'm understanding things correctly, relative units are something that would take some result of layout of the parent element (or maybe some ancestor element) and apply it to...

I think limiting queries to elements that have '[`contain: strict`](https://drafts.csswg.org/css-containment/#contain-property)' avoids many of the theoretical problems (although it would still be a substantial amount of work to implement). If you...

So saying the browser can select which element the query gets matched against isn't really a useful answer. Which element will it actually select, and how will it handle that?...

One other piece is that this should at least be compatible with future mechanisms that allow specifying what the *intrinsic* size or aspect-ratio of an image is. (These mechanisms would...

So I have a few thoughts on this proposal; I think it's probably better to put them in one place rather than distributing them across a bunch of issues in...