W3C home > Mailing lists > Public > www-style@w3.org > July 2007

Re: CSS Futures

From: David Woolley <forums@david-woolley.me.uk>
Date: Tue, 03 Jul 2007 08:19:36 +0100
Message-ID: <4689F888.3080900@david-woolley.me.uk>
To: www-style@w3.org

James Elmore wrote:
> 
>     Block sizing control is extremely limited. Only tables allow users 
> to take both block content sizes and screen width into account when 

Note that tables here mean CSS display: table*, and need not bear any 
relation to HTML tables.

> 
>     Some documents, like coupons, should not be displayed before / after 
> certain times. Some document information might be more or less important 

Time restrictions on documents should be considered part of the primary 
document meta data, and, in fact, for the end time, for HTML versions < 
"5", this is handled by HTTP and http-equiv (WHATWG's HTML 5, 
redefines/removes http-equiv, so that it no longer has the same meaning 
as an HTTP header of the same name).  In an online medium, like the web, 
start time restrictions are less of a problem; simply don't serve the 
content before the start time.

Also, before carrying this too far, consider that the whole concept of a 
coupon is that it is printed, and unless one can have printers that 
print with ink that fades out sharply after a fixed time (and 
independent of temperature, humidity, etc.) blanking on the soft copy 
won't prevent people having expired ones, so, if a user chooses to 
override caching policies on a soft copy, or simply leaves a page open, 
they are probably in no worse a position than having printed the coupon.


-- 
David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.
Received on Tuesday, 3 July 2007 07:19:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:51 GMT