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

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

From: François REMY <francois.remy.dev@outlook.com>
Date: Sat, 22 Jun 2013 14:47:43 +0200
Message-ID: <DUB120-DS7C1F35B0E552EF1D1B25FA5880@phx.gbl>
To: "Nicholas Cameron" <nick@ncameron.org>, "www-style list" <www-style@w3.org>
Cc: "Ali Juma" <ajuma@chromium.org>, "Tab Atkins" <jackalmage@gmail.com>
> [A newly show element] might cause the rest of the document to need 
> reflowing.

No, it would still be layouted, just on rendered; ‘invisible’ would not be 
quite the same as ‘display: none’; in fact, you may consider it like 
‘visibility: visible-if-possible’ which evaluates to ‘visibility: visible’ 
if the browser had enough time to paint the element, and to ‘visibility: 
hidden’ if it didn’t. That would not affect the layout. When there's a 
resize, the new layout would be computed, but the element may return to 
invisible (or reuse older frames) if the browser has not time to update its 
rendering.

That may indicate a good name for the property: ‘visibility-hint: auto | 
if-ready | pre-rendered’ where an ‘optional’ element may be invisible even 
if its visibility is visible, and where a ‘pre-rendered’ element may be 
prerendered even if it’s not visible. That yields ‘visbility: visible 
if-ready’ and ‘visibility: hidden pre-rendered’ as new visibility behaviors. 
Received on Saturday, 22 June 2013 12:48:12 UTC

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