Re: [csswg-drafts] [css-contain] How does @container resolve when no ancestor containers have been defined? (#6178)

The CSS Working Group just discussed `[css-contain] How does @container resolve when no ancestor containers have been defined?`, and agreed to the following:

* `RESOLVED: have container MQ not resolve when there is no ancestor container`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic:  [css-contain] How does @container resolve when no ancestor containers have been defined?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/6178<br>
&lt;dael> miriam: Initial proposal was if not container as explictly defined we'd fall back. Root element or viewport. Some sort of fallback for container queries so they always resolve against something<br>
&lt;iank_> a fallback to something random seems pretty bad to me.(?)<br>
&lt;dael> miriam: Not convinced. When writing a container query assuming it's close to actual size. Fallback to full viewport will be dramatically wrong in a lot of cases. IF authors are using current best MQ best practice for smaller layouts inside they get smaller fallback<br>
&lt;dael> miriam: If can have containment on root you can make the choice yourself. Popular to do, but risky fallback<br>
&lt;dael> miriam: We should not try and salvage container queries when there is no container<br>
&lt;dael> iank_: Agree. Sounds pretty hostile to fallback to something unexpected<br>
&lt;dael> astearns: I voted for root in twitter but you have convinced me I was wrong<br>
&lt;dael> astearns: Prop is have MQ not do anything if no container to measure against<br>
&lt;dael> miriam: Correct<br>
&lt;dael> florian: Reasonable<br>
&lt;dael> astearns: Obj to have conainer MQ not resolve when there is no ancestor container<br>
&lt;dael> RESOLVED: have container MQ not resolve when there is no ancestor container<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6178#issuecomment-833114628 using your GitHub account


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

Received on Wednesday, 5 May 2021 23:34:24 UTC