1667557 - 82.0B1 Print Preview is blank. (Print is OK)

Status: RESOLVED FIXED

(Thunderbird :: General, defect)

Description

[Brant Mercer]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0

Steps to reproduce:

Updated to 82.0B1.

Actual results:

Print Preview is blank. It actually shows multiple pages in page number field, but all screens are blank. I printed anyway and it seems to print ok. Appears to be solely a print preview display issue? Noted that it does allow changes such as scaling, but still shows no content of item being previewed.

Expected results:

Print Preview should have shown contents of e-mail being printed and allow editing, such as scaling.

Comment 1

[WaltS48 [:walts48]]

I'll have to test again, but printing on Windows 10 came out blank for me when testing the release candidate.

Calendar printing also didn't work IIRC.

Comment 2

[Brant Mercer]

Agree, calendar does show preview in print settings pop-up (like the grid version myself), but does not print (Win 10). Does not cause crash as with 81.0B4, just simply does not print. Different than e-mail issue that does not show preview, but dose print. ??

Comment 3

[WaltS48 [:walts48]]

Just tested this in TB 82.0b1 on Windows 10

Email printing works.
Email print preview doesn't open a preview window.
Calendar opens the preview window but doesn't print.

Does this have anything to do with the new redesign of printing for Firefox? bug 133187

Thunderbird doesn't appear to have adopted it.

Comment 4

[Brant Mercer]

Clarification Note: Print works direct from Print selection in menu, but prints blank page if Print is selected from Preview screen (in other words both preview and print-out are blank). As stated earlier, calendar simply does not print at all.

Comment 6

[Brant Mercer]

10/2/20: Updated to 82.0b2 - same issues as noted above.

Comment 8

[Brant Mercer]

10/17/20: Updated to 82.0b3 - same issues above continue.

Comment 9

[Sergey]

Now, update to 82b3 32 bit. Preview window is blank or not opened
Error console:
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebBrowserPrint.printPreviewNumPages] PrintingChild.jsm:411
updatePageCount resource://gre/actors/PrintingChild.jsm:411
handleEvent resource://gre/actors/PrintingChild.jsm:75
handleActorEvent resource://gre/modules/ActorManagerChild.jsm:153
handleActorEvent self-hosted:1208
(Асинхронный: EventListener.handleEvent)
addEventListener resource://gre/modules/ActorManagerChild.jsm:102
init resource://gre/modules/ActorManagerChild.jsm:73
attach resource://gre/modules/ActorManagerChild.jsm:335
<анонимный> chrome://global/content/browser-content.js:16
getPrintPreviewBrowser chrome://messenger/content/msgPrintEngine.js:52
_enterPrintPreview chrome://global/content/printUtils.js:679
observe chrome://global/content/printUtils.js:637
(Асинхронный: setTimeout handler)
observe chrome://global/content/printUtils.js:636
doneIniting chrome://global/content/printPreviewProgress.js:151
(Асинхронный: setTimeout handler)
onLoad chrome://global/content/printPreviewProgress.js:123
onload chrome://global/content/printPreviewProgress.xhtml:1
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDocShell.exitPrintPreview]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/actors/PrintingChild.jsm :: exitPrintPreview :: line 404" data: no] PrintingChild.jsm:404:19
exitPrintPreview resource://gre/actors/PrintingChild.jsm:404
receiveMessage resource://gre/actors/PrintingChild.jsm:99
receiveMessage resource://gre/modules/ActorManagerChild.jsm:179
(Асинхронный: MessageListener.receiveMessage)
init resource://gre/modules/ActorManagerChild.jsm:67
attach resource://gre/modules/ActorManagerChild.jsm:335
<анонимный> chrome://global/content/browser-content.js:16
getPrintPreviewBrowser chrome://messenger/content/msgPrintEngine.js:52
_enterPrintPreview chrome://global/content/printUtils.js:679
observe chrome://global/content/printUtils.js:637
(Асинхронный: setTimeout handler)
observe chrome://global/content/printUtils.js:636
doneIniting chrome://global/content/printPreviewProgress.js:151
(Асинхронный: setTimeout handler)
onLoad chrome://global/content/printPreviewProgress.js:123
onload chrome://global/content/printPreviewProgress.xhtml:1

Comment 10

[Brant Mercer]

10/22/20 - Upgraded to 83.0b1. Same issues.

Comment 11

[Ping Chen (:rnons)]

Here is what I found, after clicking File -> Print Preview, the print preview progress dialog shows up with Progress: Preparing..., then nothing happens. It's because windowGlobal is null at https://searchfox.org/mozilla-central/source/toolkit/content/widgets/browser-custom-element.js#1785. PrintingChild never receives Printing:Preview:Enter message.

I tried to write ppBrowser https://searchfox.org/comm-central/source/mailnews/base/content/msgPrintEngine.js#45-53 directly in msgPrintEngine.xhtml, then TB crashes at https://searchfox.org/mozilla-central/source/dom/base/nsGlobalWindowOuter.cpp#5349. If I comment out the MOZ_DIAGNOSTIC_ASSERT line, then print preview works as before.

:emilio can you give me some help? I can't find out why browsingContext.currentWindowGlobal is null in the first case. And in the second case, does it make sense if that assert is disabled for TB? Thanks.

Comment 12

[Emilio Cobos Álvarez (:emilio)]

(In reply to Ping Chen (:rnons) from comment #11)

Here is what I found, after clicking File -> Print Preview, the print preview progress dialog shows up with Progress: Preparing..., then nothing happens. It's because windowGlobal is null at https://searchfox.org/mozilla-central/source/toolkit/content/widgets/browser-custom-element.js#1785. PrintingChild never receives Printing:Preview:Enter message.

That generally means that the browsing context is somehow detached or well, doesn't have a window to send the message to. What is the entry point for File -> Print Preview in Thunderbird? The printing setup looked really different from Firefox, for some reason I won't claim to understand.

I tried to write ppBrowser https://searchfox.org/comm-central/source/mailnews/base/content/msgPrintEngine.js#45-53 directly in msgPrintEngine.xhtml, then TB crashes at https://searchfox.org/mozilla-central/source/dom/base/nsGlobalWindowOuter.cpp#5349. If I comment out the MOZ_DIAGNOSTIC_ASSERT line, then print preview works as before.

What do you mean with "I tried to write ppBrowser in msgPrintEngine.xhtml?

:emilio can you give me some help? I can't find out why browsingContext.currentWindowGlobal is null in the first case. And in the second case, does it make sense if that assert is disabled for TB? Thanks.

No, that assertion needs to stay, if it breaks is that the original and preview browser could end up in different processes or doing other crazy stuff.

Comment 13

[Ping Chen (:rnons)]

Thanks.

What is the entry point for File -> Print Preview in Thunderbird?

The entry point is https://searchfox.org/comm-central/source/mailnews/base/content/msgPrintEngine.xhtml. Which is brought up by https://searchfox.org/comm-central/source/mail/base/content/mailWindowOverlay.js#2710-2711,2726-2727.

I tried to write ppBrowser https://searchfox.org/comm-central/source/mailnews/base/content/msgPrintEngine.js#45-53 directly in msgPrintEngine.xhtml, then TB crashes at https://searchfox.org/mozilla-central/source/dom/base/nsGlobalWindowOuter.cpp#5349. If I comment out the MOZ_DIAGNOSTIC_ASSERT line, then print preview works as before.

What do you mean with "I tried to write ppBrowser in msgPrintEngine.xhtml?

Currently the ppBrowser is created in msgPrintEngine.js with createXULElement. I tried to write it in msgPrintEngine.xhtml

  <browser id="ppBrowser"
           type="content"
           primary="true"
           name="content"
           src="about:blank"
           flex="1"
           disablehistory="true"
           disablesecurity="true"/>

With this change, browsingContext.currentWindowGlobal seems fine, but failed at the assert line. Is there any way I can ensure the two <browser> have the same group?

Comment 14

[Emilio Cobos Álvarez (:emilio)]

Well, so you have a window global if you do that because you load about:blank.

But really you should create a browser that does something like this: https://searchfox.org/mozilla-central/rev/c938c7416c633639a5c8ce4412be586eefb48005/toolkit/components/printing/content/printUtils.js#147-152

So tldr the creation of the preview browser has to depend on the source browser (and you should set the initialBrowsingContextGroupId attribute correctly). That should help, let me know if it doesn't.

I'm still wondering why the print setup in TB is so bespoke. Maybe eventually TB can move to the nicer modal preview that Firefox has and remove a lot of that ugly code?

Comment 15

[Ping Chen (:rnons)]

Attachment: Bug 1667557 - Fix print preview by init ppBrowser first. r=mkmelin

After setting initialBrowsingContextGroupId, browsingContext.currentWindowGlobal is still null. I wonder what's the difference between document.documentElement.appendChild and put directly in the .xhtml.

Comment 16

[Ping Chen (:rnons)]

(In reply to Emilio Cobos Álvarez (:emilio) from comment #14)

Well, so you have a window global if you do that because you load about:blank.

I tried browser.setAttribute("src", "about:blank"); in msgPrintEngine.js, but browsingContext.currentWindowGlobal is still null.

But really you should create a browser that does something like this: https://searchfox.org/mozilla-central/rev/c938c7416c633639a5c8ce4412be586eefb48005/toolkit/components/printing/content/printUtils.js#147-152

So tldr the creation of the preview browser has to depend on the source browser (and you should set the initialBrowsingContextGroupId attribute correctly). That should help, let me know if it doesn't.

I'm still wondering why the print setup in TB is so bespoke. Maybe eventually TB can move to the nicer modal preview that Firefox has and remove a lot of that ugly code?

Somehow, the gBrowser and tabbrowser.js are not available in TB.

I sent a patch so you can clearly see what I tried. Thanks.

Comment 17

[Emilio Cobos Álvarez (:emilio)]

What's the stack for the windowGlobal being null?

Comment 18

[Ping Chen (:rnons)]

You mean the <stack> element? No stack element, I tried to do something similar to https://searchfox.org/mozilla-central/rev/c938c7416c633639a5c8ce4412be586eefb48005/toolkit/components/printing/content/printUtils.js#173-178, still the same.

There is no error stack, I added a console.log after https://searchfox.org/mozilla-central/source/toolkit/content/widgets/browser-custom-element.js#1785

Comment 19

[Ping Chen (:rnons)]

Turns out to be a timing issue. browsingContext.currentWindowGlobal is created a few ms after appendChild, by init ppBrowser first, it works now. Thanks Emilio.

Comment 20

[Emilio Cobos Álvarez (:emilio)]

(In reply to Ping Chen (:rnons) from comment #18)

You mean the <stack> element? No stack element, I tried to do something similar to https://searchfox.org/mozilla-central/rev/c938c7416c633639a5c8ce4412be586eefb48005/toolkit/components/printing/content/printUtils.js#173-178, still the same.

I meant the actual error stack yeah. Fwiw you can get them quite easily with new Error().stack or such.

Comment 21

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/f9161d72406a
Fix print preview by init ppBrowser first. r=mkmelin

Comment 22

[Ping Chen (:rnons)]

Comment on attachment 9185875 [details]
Bug 1667557 - Fix print preview by init ppBrowser first. r=mkmelin

[Approval Request Comment]
Regression caused by (bug #): Several m-c changes
User impact if declined: Print preview doesn't work
Testing completed (on c-c, etc.): Manually tested
Risk to taking this patch (and alternatives if risky): Low, print preview is already broken in beta

Comment 23

[Wayne Mery (:wsmwk)]

Comment on attachment 9185875 [details]
Bug 1667557 - Fix print preview by init ppBrowser first. r=mkmelin

[Triage Comment]
We aren't building another build for 83 beta, so this will appear in 84 beta

Comment 24

[WaltS48 [:walts48]]

Print preview and email printing works in my test of 84.0b1 on Ubuntu 18.04.