W3C home > Mailing lists > Public > public-html@w3.org > April 2007

Re: beforeprint event

From: Dao Gottwald <dao@design-noir.de>
Date: Mon, 09 Apr 2007 11:39:41 +0200
Message-ID: <461A09DD.1010905@design-noir.de>
To: Anne van Kesteren <annevk@opera.com>
CC: Matthew Raymond <mattraymond@earthlink.net>, Chris Wilson <Chris.Wilson@microsoft.com>, "public-html@w3.org" <public-html@w3.org>

Anne van Kesteren wrote:
>
> On Mon, 09 Apr 2007 10:23:07 +0200, Dao Gottwald <dao@design-noir.de> 
> wrote:
>> That said, I still agree with HÃ¥kon. CSS can handle most real-world 
>> cases today, and it will get even better with future versions. So the 
>> beforeprint event sounds like it will become obsolete (if that's not 
>> already the case), thus it shouldn't be standardized.
>
> Implementing events like that should be pretty trivial and allows 
> authors to innovate themselves without having to wait for browser 
> vendors to implement everything they might ever want in CSS.

Yeah, but it are only edge cases where you would need more complex CSS 
than we have today. And those cases will fade away; it's not like 
"everything they might ever want in CSS" is an infinite list.

Besides, are beforeprint and afterprint even supported by browsers 
besides IE?

> The use cases might be catered for by something like XBL

And XSLT.

> , but I don't seen anything inherently harmful in supporting events 
> that indicate the transition between presentation media.

Maybe a "mediachange" event, but "beforeprint" and "afterprint" sound 
like a hack. It's not even clear to me how they work. Is there a copy of 
the document or would scripted transformations affect the real page as 
well as the print preview? The former seems unlikely (otherwise, why do 
we need "afterprint"?) and latter would be a design flaw.

--Dao
Received on Monday, 9 April 2007 09:39:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:42 UTC