- From: Andy Hume <andyhume@thedredge.org>
- Date: Fri, 6 Apr 2007 11:22:50 +0100
- To: public-html@w3.org
On 5 Apr 2007, at 22:42, Chris Wilson wrote: > > [chair hat off...maybe I should leave it off for a bit] > That's partly true, but partly app authors may want to provide some > more programmatic change to the page - e.g., informing controls > (whether ActiveX, script-behind, whatever) that they're about to > print, in case the control needs to make changes. I'd agree with this. It's particularly desirable in a more web application type scenario rather than simply styling content for print, and would typically be used in conjunction with a print stylesheet. To what level are these browser-based events within the scope of the HTML WG? - Andy > For events like that, it would seem to be better than forcing > everyone to do everything using css media (which, btw, IE supports > as well; this isn't saying that support is not good). > > -Chris > > -----Original Message----- > From: Dao Gottwald [mailto:dao@design-noir.de] > Sent: Thursday, April 05, 2007 2:38 PM > To: Chris Wilson > Cc: Matthew Raymond; public-html@w3.org > Subject: Re: Microsoft has now joined the HTML Working Group > > Chris Wilson wrote: >>> 8) Do you feel that |onbeforeprint| and |onafterprint| should be >>> incorporated into the next HTML standard? >> >> If you mean the events we support in IE (or some cleanup of same/ >> same concept), sure. > > What are the use cases? I remember that when people asked for these > events, it seemed that they just didn't know CSS well enough to > define a > print stylesheet. >
Received on Friday, 6 April 2007 20:43:34 UTC