W3C home > Mailing lists > Public > www-style@w3.org > June 2013

Re: [css-display]? Compositing, expensive things, and laziness

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sun, 23 Jun 2013 00:43:58 +1200
Message-ID: <CAOp6jLYu9d17Cb5+tVNZXU8RwGazDGOmFFDWwEzWex2ZZOu64Q@mail.gmail.com>
To: Nicholas Cameron <nick@ncameron.org>
Cc: www-style list <www-style@w3.org>
On Fri, Jun 21, 2013 at 10:08 AM, Nicholas Cameron <nick@ncameron.org>wrote:

> What happens with re-sizing? Assuming the display-optionality:optional
> element does not have fixed width/height and is in flow, then when the
> element does get rendered it might cause the rest of the document to need
> reflowing. That seems undesirable - users don't expect the webpage to
> randomly change some time after 'loading' is finished.
>

The idea is that this property has no effect on how layout works.
"Rendering" here just means painting.

Also, an idea: the default value is 'required' for visible elements, could
> we specify the default as 'optional' for invisible elements (display:none,
> visibility:hidden, etc)?
>

No. The default value of a CSS property can't depend on the values of other
properties. You could define an "auto" value that means "required" for
visible elements and "optional" for invisible ones. I'm not sure whether
that's a good idea...

Rob
-- 
Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le
atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa
stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm
aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt
wyeonut thoo mken.o w
Received on Saturday, 22 June 2013 12:44:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:12 UTC