W3C home > Mailing lists > Public > www-style@w3.org > October 2001

RE: The "display" property

From: Manos Batsis <m.batsis@bsnet.gr>
Date: Mon, 1 Oct 2001 11:19:54 +0300
Message-ID: <A35E2040C17F0C48B941B8F4D0DF12291DFD0D@ermhs.Athens.BrokerSystems.gr>
To: "Rowland Shaw" <Rowland.Shaw@crystaldecisions.com>, "Daniel BODEA" <dali@dali-designs.com>
Cc: <www-style@w3.org>

> -----Original Message-----
> From: Rowland Shaw [mailto:Rowland.Shaw@crystaldecisions.com] 

> From reading the relevant section of the CSS2 spec [
> http://www.w3.org/TR/REC-CSS2/visuren.html#propdef-display ] it merely
> states the element will create no boxes in the formatting 
> structure. I'd
> expect the guys at Netscape will argue their case of saving 
> downloads of
> content "not required".
> My personal thought on this is if we're not going to display 
> this visual
> element, we don't need to download it (just yet). However, I 
> would expect
> the user agent to hold on to the image data if it's display 
> property changes
> to a visual state (in this case, inline), even if it goes non 
> visual again.

The spec is wise for not stating if the image should be downloaded. It
would make no sense to download images that may never really display. On
the other hand, if the image's display attribute is going to change
dynamically, it should be the developers job to preload it or write code
that will dynamically preload it based to some user interaction (still,
before the image's display changes).
But that's just my opinion.

Kindest regards,

Received on Monday, 1 October 2001 04:18:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:26:59 UTC