- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Mar 2022 17:11:30 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `CSS MultiCol`, and agreed to the following: * `RESOLVED: Accept proposal that elements which establish fixedpos containing block also block descendant spanners` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: CSS MultiCol<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/6805<br> <fantasai> alisonmaher: Criteria of becomming a spanner, specifically in case of a transform<br> <fantasai> alisonmaher: According to spec, can become a spanner if in the same formatting context<br> <fantasai> alisonmaher: even if inside a transformed ancestor<br> <fantasai> alisonmaher: because transform doesn't establish a new formatting context<br> <fantasai> alisonmaher:even though transforms trap fixed pos descendants<br> <fantasai> alisonmaher: Proposal is that anything that establishes a fixedpos containing block also prevents descendants from becoming a spanner<br> <rachelandrew> q+<br> <TabAtkins> +1<br> <astearns> ack rachelandrew<br> <fantasai> dbaron: Sgtm<br> <fantasai> rachelandrew: It seems like a sensible proposal, happy to make the edits<br> <fantasai> astearns: Anyone with concerns?<br> <fantasai> [silence]<br> <fantasai> astearns: Any objections?<br> <fantasai> RESOLVED: Accept proposal that elements which establish fixedpos containing block also block descendant spanners<br> <chris> https://github.com/w3c/csswg-drafts/issues/6773#issuecomment-1062008116<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6805#issuecomment-1063159219 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 March 2022 17:11:32 UTC