- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Jun 2021 16:27:18 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Contain`, and agreed to the following: * `RESOLVED: add style containment back to 'strict' and 'content' values of 'contain'` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Contain<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6287<br> <fantasai> TabAtkins: Some time ago we removed 'style' from set of containments applied by 'strict'<br> <fantasai> TabAtkins: since at-risk, unsure if FF would implement<br> <fantasai> TabAtkins: no longer at-risk<br> <fantasai> TabAtkins: Question is should we have a keyword that applies 'strict'?<br> <fantasai> TabAtkins: if so, should we add a new keyword or build it back into 'strict'?<br> <fantasai> TabAtkins: chrishtr commented that he thinks it'd be fine to add into existing 'strict', and willing to do experimentation in Chrome<br> <fantasai> fremy: I agree, makes sense to me<br> <dholbert> Sounds fine by me<br> <fantasai> oriol: Wouldn't just be strict, but also ...<br> <fantasai> oriol: content<br> <fantasai> TabAtkins: content used to be 'strict' without 'size', so add to that as well<br> <fantasai> fantasai: sgtm<br> <fantasai> astearns: so proposed resolution is to add back in style containment to 'strict' and 'content' values of 'contain'<br> <fantasai> astearns: Any objections?<br> <chrishtr> I will get this change made in Chromium asap so we can get canary channel feedback. Will report back if there are any found.<br> <fantasai> RESOLVED: add style containment back to 'strict' and 'content' values of 'contain'<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6287#issuecomment-862525199 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 June 2021 16:27:47 UTC