- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Feb 2018 17:41:23 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `[css-contain] Clarify style containment effect 1`, and agreed to the following resolutions: * `RESOLVED: have the break properties not effected by style containment` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-contain] Clarify style containment effect 1<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1872<br> <dael> florian: There's a thing called style containment with 2 groups of effect. #2 isn't under discussion, that's fine. What's under discussion is how style containment shouldshouldn't effect break-before and break-after.<br> <dael> florian: A number of people said effecting made no sence. TabAtkins wasn't sure. TabAtkins are you now sure?<br> <dael> TabAtkins: I think we can remove it.<br> <dael> astearns: Proposal is to have the break properties not effected by style containment?<br> <dael> florian: Or drop the part that claims they are.<br> <dael> astearns: Obj?<br> <dael> RESOLVED: have the break properties not effected by style containment<br> <liam> regrets+ Liam<br> <dael> florian: Part 2 talks about flow-from and flow-into. I think that should be moved to regions spec given relative maturity.<br> <dael> astearns: I think that's fine. Can you open an issue on regions to add that?<br> <dael> florian: I can open a PR that changes both specs?<br> <dael> astearns: Even better.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1872#issuecomment-365686723 using your GitHub account
Received on Wednesday, 14 February 2018 17:41:25 UTC