- From: Hakon Lie <howcome@w3.org>
- Date: Wed, 3 Jul 1996 16:57:13 +0200
- To: Thomas Reardon <thomasre@microsoft.com>
- Cc: "'www-style@w3.org'" <www-style@w3.org>, "'Pam Kagan'" <pam@safari.net>
Thomas Reardon writes: > >From: Pam Kagan[SMTP:pam@safari.net] > >Are there any provisions in existing CSS to specify the order in which > >blocks of text and/or images will load...thereby allowing HTML authors > >greater creative control? > I don't think anyone responded to this yet: we have proposed a > "PRIORITY" attribute for CSS in the part (not for CSS Level 1 mind you), > not sure where it sits now. (I responded -- did it get lost? Reply enclosed) ------- start of forwarded message (RFC 934 encapsulation) ------- In-Reply-To: <1.5.4.32.19960701142640.0071eff8@safari.net> References: <1.5.4.32.19960701142640.0071eff8@safari.net> From: Hakon Lie <howcome@w3.org> To: Pam Kagan <pam@safari.net> Cc: www-style@w3.org Subject: Beyond Netscape ML Date: Mon, 1 Jul 96 16:07:41 MET DST Pam Kagan writes: > Are there any provisions in existing CSS to specify the order in which > blocks of text and/or images will load...thereby allowing HTML authors > greater creative control? This has come up in several discussions, but it's not in any of the CSS specifications. The issue is related to the presentation of a document, but it touches on so many other issues (net load, colormap, persistent connections, interleaving of data) that I've resisted addressing it up to now. Also, while we can set properties on HTML elements like IMG, we cannot set properties on images that are referred to from CSS properties: BODY { background: url(really-dull.gif) white } Regards, - -h&kon Hakon W Lie, W3C/INRIA, Sophia-Antipolis, France http://www.w3.org/people/howcome howcome@w3.org ------- end -------
Received on Wednesday, 3 July 1996 10:57:27 UTC