Window open + print + close, has some issues in non-Firefox browsers

Yes. We're using 7x.2x because we need to have the links displayed in a block, which is not a 7.x-1.0 option.

We'd love to see that @todo become a @todone, but we're too weak on PHP @todoit ourselves.

BTW, what you've done with the new branch is great.

Thanks so much for your quick response and explanation.

I switched from 7.x-1.0 to 7.x-1.x-dev and tried it out with Firefox and my preferred settings, and it worked perfectly. Then I tried another browser, and another, and realized that I'd have to test much more extensively.

I primarily tested the settings that govern how the tab or window is opened and closed, using the Windows versions of the following browsers (ordered by their rankings in our site's analytics). I tested with the output going to either a printer or to CutePDF, which made no difference to the way the browsers performed.
Internet Explorer 8 (58% of users)
Safari 5.1.5 (17%)
Firefox 3.6 (11%)
Chrome 14 (9%)
Opera 11.51 (0.1%)

For each combination of settings all caches were flushed and the test page was refreshed in each browser. The choice of New window method made no difference to the results.

Annoyingly, as usual, all of the browsers wanted to do things in their own special ways. Firefox was the best behaved. Chrome is usually well behaved, but failed badly under one combination of settings (the ones I prefer, of course :/ ). IE was unpredictable; Safari had some failures; and Opera was a total disaster (no surprise there).

Since the results were so inconsistent, I would not be at all surprised if you were to get completely different results. In one way or another, all browsers suck.

1. Without Open the printer-friendly version in a new window and
   Without Close window after sending to printer
   OR
2. Without Open the printer-friendly version in a new window and
   With Close window after sending to printer
   • IE, Firefox, and Chrome:
     • The printer-friendly page opens in the current tab.
     • The print dialog tab (Chrome) or dialog box (Firefox, IE) opens. Upon printing or cancelling, the print dialog closes, but the printer-friendly page remains in the current tab and the back button must be clicked to return to the original page.
   • Safari:
     • The print dialog box opens.
     • Upon printing or cancelling(!), the print dialog closes and the printer-friendly page opens in the current window, then the back button must be clicked to return to the original page.
   • Opera:
     • The printer-friendly page opens in the current tab.
     • No print dialog opens, so one must select print from the browser menu, then the back button must be clicked to return to the original page.
3. With Open the printer-friendly version in a new window and
   Without Close window after sending to printer
   • IE, Firefox, and Chrome:
     • The printer-friendly page opens in a new tab (Chrome, Firefox) or window (IE).
     • The print dialog tab (Chrome) or dialog box (Firefox, IE) opens. Upon printing or cancelling, the print dialog closes, but the printer-friendly tab or window remains open and must be closed manually.
   • Safari:
     • A blank window opens.
     • The print dialog box opens.
     • Upon printing or cancelling, the print dialog closes and the printer-friendly page opens in the blank window, which must be closed manually.
   • Opera:
     • The printer-friendly page opens in a new tab.
     • No print dialog opens, so one must select print from the browser menu, then close the tab displaying the printer-friendly page.
4. With Open the printer-friendly version in a new window and
   With Close window after sending to printer
   • IE:
     • Either:
       • The printer-friendly page opens in a new window.
       • The print dialog box opens.
       • Upon printing or cancelling, the print dialog and the new window with the printer-friendly page close.
         OR
       • The printer-friendly page opens in a new window, then closes immediately.
       • The print dialog box does not open.
       • No print output is produced.
   • Safari:
     • A blank window opens.
     • The print dialog box opens.
     • Upon printing or cancelling, both the print dialog and the blank new window close.
     • No print output is produced.
   • Firefox:
     • The printer-friendly page opens in a new tab.
     • The print dialog box opens.
     • Upon printing or cancelling, the print dialog and the new tab with the printer-friendly page closes.
   • Chrome:
     • The printer-friendly page opens briefly in a new tab, but closes before or shortly after the Chrome print dialog opens.
     • The Chrome print dialog page opens, but with the error message "Print is unavailable because the page you were trying to print has been closed."
     • If the printer-friendly tab closed before the print dialog tab opened, then the "Reopen the page" button does not appear beneath the error message, so the print dialog tab must be closed manually and one must try again by clicking the printer icon on the original page.
     • If the printer-friendly tab closed after the print dialog tab opened, then the "Reopen the page" button does appear beneath the error message. When that button is clicked, the printer-friendly page opens in the current (print dialog) tab and remains and a new print dialog tab opens successfully. Upon printing or cancelling, the print dialog tab closes, but the printer-friendly tab remains open and must be closed manually.
   • Opera:
     • A blank tab opens, then closes immediately.
     • No print dialog opens.
     • No print output is produced.

Finally, this is totally unrelated to the block-only option.. Can you please open a new issue?

Yes, but it is totally related to the original support request issue that I opened. You asked what I thought, so I invested the time in testing it. Shouldn't have bothered, I guess; won't bother again. :(

My last message was a little testy, I know. Up too late; up too early; no coffee. I do beg your pardon.

I'll be happy to test Safari, I'll get to it tomorrow or Saturday.

Cheers :)

So I tried it out over the weekend at home, with completely different results: Chrome worked like a charm, but IE failed completely. I didn't have Safari or Firefox installed -- it's a new PC -- and I didn't really have time to install them because I'm in a big rush to get our site live on time. In a couple of weeks I'll have more time; right now, doing anything that isn't work is an inexcusable luxury. (._.)

Thank you very much. I'm looking forward to trying out the new dev version as soon as time allows. :)