On 7/20/05, Matthew Raymond <[EMAIL PROTECTED]> wrote:
> Jim Ley wrote:
> > This is another of the use cases I've used "enhanced" printing for - I
> > actually generally used ScriptX http://www.meadroid.com/scriptx/
> > rather than simply the IE methods, but the events are all that's
> > needed. N
Dean Edwards wrote:
> Matthew Raymond wrote:
>>Dean Edwards wrote:
>>>Matthew Raymond wrote:
>>>
| if (documentchanged) {
| printClone = document.clone();
| prepareForPrinting(printClone);
| }
|
| printClone.print();
>>>
>>>This seems less practical than print events.
>>
Matthew Raymond wrote:
Dean Edwards wrote:
Matthew Raymond wrote:
| if (documentchanged) {
| printClone = document.clone();
| prepareForPrinting(printClone);
| }
|
| printClone.print();
This seems less practical than print events.
I don't see how:
| OnBeforePrintEventFunction() {
Dean Edwards wrote:
> Matthew Raymond wrote:
>>| if (documentchanged) {
>>| printClone = document.clone();
>>| prepareForPrinting(printClone);
>>| }
>>|
>>| printClone.print();
>
> This seems less practical than print events.
I don't see how:
| OnBeforePrintEventFunction() {
| prepareFo
James Graham wrote:
> Just to muddy the waters a bit - it is quite likely that Gecko 1.9 will
> allow pages to be 'exported' to a variety of formats (in a manner
> analogous to http://gecko.dynalivery.com/ ). Clearly I have no idea what
> the UI for this functionality will be but lets pretend th
Matthew Raymond wrote:
| if (documentchanged) {
| printClone = document.clone();
| prepareForPrinting(printClone);
| }
|
| printClone.print();
This seems less practical than print events. It is also very difficult
to detect changes to the document. What do you mean by changes? Style
cha
Matthew Raymond wrote:
3) It can be easily disabled with a modified open source browser or
browser extension.
So?
So it's useless for keeping people from printing stuff without paying
if the people in question really want to print something. Also, you
could probably also use cop
Anne van Kesteren wrote:
> Quoting Matthew Raymond <[EMAIL PROTECTED]>:
>
>>6) An alternative has been proposed that has less potential for abuse,
>>is more powerful, and doesn't change basic browser functionality.
>
> Which alternative was proposed that did not rely on CSS and is acceptable?
> (
Dean Edwards wrote:
> Matthew Raymond wrote:
>>1) The feature can be abused.
>
> All features can be abused.
Yes, but some more than others.
>>2) It alters the standard behavior of the browser.
>
> No it doesn't.
Uh, yes it does. Perhaps the problem is that CSS clouds the issue.
Since CS
The big problem for me on this whole onbeforeprint/onafterprint argument
is that I only have partial control of the DOM using JavaScript.
What do I mean by this?
I can create content using the window's load event:
onload = function() {
// create content for screen
}
This content, which is
Matthew Raymond wrote:
Dean Edwards wrote:
See several people's posts stating that because something may be abused
it is not a good enough reason to disallow it.
I think there's good enough reason to disallow a feature when you
have the following:
1) The feature can be abused.
All fea
Quoting Matthew Raymond <[EMAIL PROTECTED]>:
6) An alternative has been proposed that has less potential for abuse,
is more powerful, and doesn't change basic browser functionality.
Which alternative was proposed that did not rely on CSS and is acceptable?
(Also, the alternative probably won't
Dean Edwards wrote:
> See several people's posts stating that because something may be abused
> it is not a good enough reason to disallow it.
I think there's good enough reason to disallow a feature when you
have the following:
1) The feature can be abused.
2) It alters the standard behavio
Jim Ley wrote:
> On 7/19/05, Dean Edwards <[EMAIL PROTECTED]> 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
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
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
On 7/19/05, J. Graham <[EMAIL PROTECTED]> wrote:
> On Tue, 19 Jul 2005, Jim Ley wrote:
>
> > Someone will probably suggest CSS background-images as a suitable for
> > this aswell, yet again ignoring the fact that CSS is _optional_, and
> > content-images must not be in background images as they si
On Tue, 19 Jul 2005, Jim Ley wrote:
Someone will probably suggest CSS background-images as a suitable for
this aswell, yet again ignoring the fact that CSS is _optional_, and
content-images must not be in background images as they simply won't
be seen without CSS or if background images are disa
On 7/19/05, Dean Edwards <[EMAIL PROTECTED]> 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
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.
-dean
20 matches
Mail list logo
