1640768 - Make AutoPrintEventDispatcher work in fission

Status: RESOLVED FIXED

(Core :: Printing: Setup, defect, P3)

Description

[Hiroyuki Ikezoe (:hiro)]

AutoPrintEventDispatcher uses EnumerateSubDocuments, it doesn't enumerate any OOP iframes.

The HTML Standard spec clearly says;

3. The user agent must fire an event named beforeprint at the relevant global object of the Document that is being printed, as well as any child browsing contexts in it.

I am less sure that any child browsing contexts contain cross origin iframe's contexts though. But I suppose it does.

Comment 1

[Emilio Cobos Álvarez (:emilio)]

Yes it does, though worth looking at other browser's behavior here.

Comment 2

[Hiroyuki Ikezoe (:hiro)]

Attachment: A sample to see whether beforeprint/afterprint is fired in an OOP iframe

Thank you Emilio. Chrome does fire beforeprint/afterprint events in OOP iframes (at least in print preview).

Comment 3

[Neha Kochar [:neha]]

This should probably also get fixed in Shirley.

Comment 4

[Jonathan Watt [:jwatt]]

I actually don't think we need this as a separate bug. This should automatically just work once we do static clones for oop-iframes.

Hiro, are you okay to close this?

(Also, FWIW AutoPrintEventDispatcher no longer exists - the events are dispatched from nsPrintJob::DoCommonPrint.)

Comment 5

[Hiroyuki Ikezoe (:hiro)]

Sure.