W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2021

Re: [csswg-drafts] [css-contain] :root/body viewport propagation and containment (#5913)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 May 2021 16:57:10 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-844290779-1621443428-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-contain] :root/body viewport propagation and containment`, and agreed to the following:

* `RESOLVED: specify this in CSS Contain`
* `RESOLVED: If the used value of contain is other than the default we break propagation`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-contain] :root/body viewport propagation and containment<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5913#issuecomment-836692271<br>
&lt;dael> futhark: I was not in APAc so clarification. Resolution says stops prop if there is containment. Applied or contain property?<br>
&lt;dael> futhark: Does paint containment stop it? Any containment?<br>
&lt;dael> futhark: And then there is which spec does this go into? Varios specs that talk about prop or the CSS Contain spec?<br>
&lt;dael> futhark: I don't know if anybody had opinions<br>
&lt;dael> astearns: So where does this get specified?<br>
&lt;dael> florian: Suggest contain spec, possibley with notes<br>
&lt;dael> astearns: Objections to spec this in CSS Contain<br>
&lt;dael> RESOLVED: specify this in CSS Contain<br>
&lt;dael> astearns: What types of containment change prop?<br>
&lt;dael> astearns: Any non-default or all of the values that create a container?<br>
&lt;dael> futhark: Problem with those that establish a container is we may need to change behavior as we add values<br>
&lt;dael> futhark: Can spec as the containment nec to establish a container but that breaks content if you use containment for all things<br>
&lt;dael> astearns: Downside to saying we break prop for non-default value?<br>
&lt;dael> futhark: Don't think so. Not strictly necessary<br>
&lt;dael> florian: Feels overkill, but is it really bad?<br>
&lt;dael> fantasai: My thoughts exactly<br>
&lt;dael> florian: We're not effecting any amount of prop from root, it's from body to root?<br>
&lt;dael> futhark: Body to viewport and potentially root<br>
&lt;dael> futhark: Also for applied containment. Used or applied<br>
&lt;dael> astearns: Sounds like your preference is that if the used value of containment is other than default it breaks prop<br>
&lt;dael> futhark: Yep<br>
&lt;dael> astearns: Slgihtly worried that things which use contain:paint might depend on prop but can't think of a reason<br>
&lt;iank_> I think its a non-issue here<br>
&lt;dael> florian: Absense of container quereis doing containment on body might not be common<br>
&lt;dael> astearns: Prop: If the used value of contain is other than the default we break propagation<br>
&lt;dael> astearns: Obj?<br>
&lt;dael> RESOLVED: If the used value of contain is other than the default we break propagation<br>
&lt;chrishtr> \o/<br>
&lt;dael> astearns: other questions on your list?<br>
&lt;dael> futhark: no<br>
&lt;florian> s/Absense of container quereis doing containment on body might not be common/In the absense of container quereis, doing containment on body might not be common, so we're probably fine/<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 May 2021 16:57:12 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:33 UTC