[whatwg] Browsers delay window.print() action until page load finishes
ian at hixie.ch
Wed May 4 15:38:41 PDT 2011
On Thu, 20 Jan 2011, Alexey Proskuryakov wrote:
> There seems to be no provision in the spec for a behavior Firefox and IE
> (and now WebKit-based browsers, too) have. If window.print() is called
> during page load, then its action is delayed until loading is finished.
I haven't been able to reproduce this. I can reproduce cases where the
browser entirely ignores a window.print() call (as allowed by the spec),
but none where the call is delayed until later.
Do you have a test case demonstrating this?
I'd be happy to spec this, I'm just trying to work out what it means with
respect to event firing, etc (the rest of the algorithm). Presumably, in
many cases we want it to be synchronous as now, since pages presumably
depend on being able to edit the DOM before and after.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg