- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 May 2018 04:06:53 +0000
- To: public-css-archive@w3.org
upsuper has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-content] Does `content: none` on element suppress box generation of children? == The spec currently says the following for `content: none`: > On elements, this inhibits the children of the element from being rendered as children of this element, as if the element was empty. while for `<content-replacement>` and `<content-list>` it says: > (On elements, their) normal contents are suppressed and do not generate boxes, as if they were `display: none`. It is unclear to me whether `content: none` should suppress boxes as well. On the one hand, "as if the element was empty" seems to indicate that all the children should behave as if they were `display: none` so that the element behaves as if it's empty. On the other hand, "this inhibits the children of the element from being rendered" seems to indicate that it would just cause the children not to be rendered, like what `visibility: hidden` does but cannot be overridden by children. I suppose `content: none` should suppress children from generating boxes just like the other two values. The spec should make it clearer. If the spec intends to mean just skipping rendering (rather than suppressing generating boxes), it should probably make a note there explicitly mentioning the difference. Although I don't think this is a good idea. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2637 using your GitHub account
Received on Thursday, 3 May 2018 04:08:27 UTC