- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jul 2017 21:00:39 +0000
- To: public-css-archive@w3.org
Wow, I didn't even notice this section being added. The whole thing makes no sense. For example, it's saying that `display: ruby` element becomes a `display: flow-root` when `contain: paint` is set on it, and that this is a _used value_ time transformation of the `display` value... which makes no sense because box generation depends on computed values. Then it goes on to define a concept of “becoming a formatting context”, but doesn't explain how this is different from “establishing a formatting context” (which is an established term of art that has a specific meaning as defined in the Display glossary and CSS2.1), nor how that works. Imho, either this needs a proper definition that makes sense, is appropriate to the issues in paint containment, and doesn't conflict with the rest of CSS, or `contain` needs to limit itself to appropriate `display` values so that it's not creating nonsensical layout effects out of thin air. Origin of section: https://github.com/w3c/csswg-drafts/pull/831/files Move to Display: https://hg.csswg.org/drafts/rev/49ade53b18a2 Current location: https://drafts.csswg.org/css-display-3/#becoming-formatting-context -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-313225448 using your GitHub account
Received on Wednesday, 5 July 2017 21:00:45 UTC