W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2016

[csswg-drafts] [css-display] Add a third display-box property, similar to discard in box-suppress

From: nilssolanki via GitHub <sysbot+gh@w3.org>
Date: Thu, 08 Sep 2016 16:06:18 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-175794794-1473350777-sysbot+gh@w3.org>
nilssolanki has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-display] Add a third display-box property, similar to discard 
in box-suppress ==
>From what I understand, the current behavior of `display: contents` is
 similar to `box-suppress: hide` (except that it only applies to the 
current element, not its children):

> Properties that rely on boxes but do not rely on layout, such as 
animations, counter-increment, etc., must work as normal on this 
element and its descendants.

[Issue 1 of `display: 
contents`](https://drafts.csswg.org/css-display-3/#box-generation) 
discusses the question of whether it should take other properties into
 account as well.

I suggest adding a `display: discard` property, which behaves would be
 (more or less) analogous to `box-suppress: discard`.

Meaning the element would not generate a box, all other CSS properties
 on the element and pertaining to the element would be ignored and 
sibling/descendant selectors wouldn't register it as an element 
either.

**Use-Case**

Third-party markup which contains unwanted elements and could destroy 
the layout. This happens in CMS for frontend-editing purposes for 
example.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/456 using your GitHub 
account
Received on Thursday, 8 September 2016 16:06:25 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:34 UTC