[whatwg] print stylesheet

Would it be possible to add a print stylesheet to the specifications? Or perhaps a global one although that is not stricly necessary. (PDF would be even cooler, but I'm not sure if there are any good scripts for that you could add to the publishing mechanism.) -- Anne van Kesteren

Re: [whatwg] WA1: attribute requirements

On Wed, 20 Jul 2005, fantasai wrote: > > One way of drawing the line might be, does dropping this requirement > result in a semantically-meaningful representation? An empty list > represents an empty list. But a without a 'name', or a > without a 'href': these, per spec, represent nothing. Th

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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? > (

[whatwg] [wf2] default value size attribute from select element

Any chance Web Forms 2 is going to say something about: Default value for size DOM attribute from the SELECT element Test alert(document.getElementsByTagName('select')[0].size); Firefox 1.8b3: -1. Opera 8 and IE 6: 0. Haven't been able to test other browsers. -- Anne van Kesteren

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

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

Re: [whatwg] print stylesheet

Quoting Anne van Kesteren <[EMAIL PROTECTED]>: Would it be possible to add a print stylesheet to the specifications? Or perhaps a global one although that is not stricly necessary. (PDF would be even cooler, but I'm not sure if there are any good scripts for that you could add to the publishing

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

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

[whatwg] [wf2] seeding SELECT with ambiguous XML

Say I load this file through a DATA attribute of a SELECT element: http://www.w3.org/1999/xhtml";> FAIL PASS Should it say PASS? Is it undefined? Is there a specification which defines this? Kind regards, Anne -- Anne van Kesteren

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

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

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

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

Re: [whatwg] [Web Forms 2.0] type="url"

James Graham wrote: The problem is if I state one thing explicitly, then people will want something else stated ("does it allow IDNs?" "does it allow UTF-8 characters?" "does it allow fragment identifiers?"). Why should one aspect of something be redundantly stated? Because it's identified b

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

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() {

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

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. >>

Re: [whatwg] [wf2] seeding SELECT with ambiguous XML

Anne van Kesteren wrote: Say I load this file through a DATA attribute of a SELECT element: http://www.w3.org/1999/xhtml";> FAIL PASS Should it say PASS? Is it undefined? Is there a specification which defines this? "If a user agent encounters an element it does not recognize, it shou

Re: [whatwg] [wf2] seeding SELECT with ambiguous XML

On Wed, 20 Jul 2005, Anne van Kesteren wrote: > > Say I load this file through a DATA attribute of a SELECT element: > > http://www.w3.org/1999/xhtml";> > FAIL > > PASS > > > > Should it say PASS? Is it undefined? Is there a specification which > defines this? It should do exactly the s