- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jul 2017 20:48:19 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-contain] `contain` should not affect `display` == Paint Containment is messing with box relationships in ways that don't make 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. Basically this whole section is messed up. It either needs a proper definition that makes sense 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. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1581 using your GitHub account
Received on Wednesday, 5 July 2017 20:48:25 UTC