- From: Philip Walton <philip@philipwalton.com>
- Date: Tue, 5 Mar 2013 13:57:37 -0800
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style list <www-style@w3.org>
- Message-ID: <CAGRhNhVGj=X3tYJ4Wjz6mgQHhbRFr26=5eyjL-jrgNKirVwWZg@mail.gmail.com>
How about `render`? It seems to work semantically for all the examples/cases you listed. render: normal; render: none; render: contents; render: hidden; On Tue, Mar 5, 2013 at 1:46 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Tue, Mar 5, 2013 at 1:05 PM, Tab Atkins Jr. <jackalmage@gmail.com> > wrote: > > Recent discussion between me, fantasai, and some internal people over > > the 'display-box' property > > <http://dev.w3.org/csswg/css-display-3/#the-display-box> have led us > > to conclude that it needs to be a completely separate property, not a > > longhand of 'display'. (Reasoning below.) However, now we need a > > name. We've come up with "box", "show", and "box-tree". Better > > suggestions? > > Alan points out that it's probably valuable to know the full range of > values we expect to have for this. > > There's the obvious starting values - "none" and something like > "normal" or "auto". > > Then, we'll add "contents", a la the current Display draft, which > suppresses the display of the box but still displays the contents, as > if they were "hoisted" up a level in the tree. > > We'll probably also want a value that suppresses the box but keeps > animations/counters/etc going. For this value, maybe "hide"? > > ~TJ > >
Received on Tuesday, 5 March 2013 21:58:04 UTC