W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2005

[whatwg] [html5] onbeforeprint/onafterprint (was window.print() undefined)

From: Dean Edwards <dean@edwards.name>
Date: Wed, 20 Jul 2005 16:18:15 +0100
Message-ID: <42DE6B37.2020005@edwards.name>
Matthew Raymond wrote:
> Dean Edwards wrote:
> 
>>Matthew Raymond wrote:
>>
>>>For instance, such events could be combined with AJAX to force people
>>>into a pay-to-print scenario.
>>
>>What's wrong with paying to print a high quality version of an image? If
>>you ask me this is a great example of why we should allow these events.
> 
> 
>    It alters the expected behavior of browser chrome while not actually
> securing the content. All one would have to do to circumvent the events
> is to create a fork of Firefox or an extension that turns off the
> print-related events. Why provide events that tamper with the normal
> behavior of a browser function without actually providing added security
> for the web developer? The onbeforeprint/onafterprint events only serve
> to harass the users, and it doesn't actually enable you to do something
> you couldn't do with a reasonable workaround (see my earlier Mapquest
> example).
> 

See several people's posts stating that because something may be abused 
it is not a good enough reason to disallow it.

-dean
Received on Wednesday, 20 July 2005 08:18:15 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:42 UTC