923464 - Attempting to print Google Spreadsheets results in a message stating "There was an unexpected problem while printing." Printing other Google Documents works as expected.

Status: RESOLVED INACTIVE

(Core :: Printing: Output, defect)

Description

[macgurlnet]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.76 Safari/537.36

Steps to reproduce:

Go to Google Drive & open any Google Spreadsheet
Use the Firefox menu to choose the Print option


Actual results:

Error message pops up. Message states "There was an unexpected problem while printing."


Expected results:

Printer properties dialog box should pop up, requesting a printer be chosen, etc.

Printing using the option provided by Google (a printer button located below the file name) works as expected. Only Google Spreadsheets are affected by this issue; other Google documents print as expected.

Printing issue occurs on 2 laptops running Windows 7 Professional 64-bit and a desktop running Windows XP.

Comment 1

[Mark]

Same problem in 26.0

Workaround:
- Go to drive
- Right-click on the spreadsheet
- Choose "Preview"
- Print works as expected.

Comment 2

[Mark]

I take that back. The same or another bug still prevents printing.

After the steps above, I cannot click the File menu anymore.
I can however click on other menus, and if I then move to the file menu and choose Print again, I get the following:

"Printer Error" -- "Some functionality is not currently available."

And after this, the File menu works again.

Comment 3

[Adam Moore]

This happens on OSX and Linux as well.

Comment 4

[Adam Moore]

This also happens when you attempt to print a document that hasn't finished loading.  Google may be doing something that is keeping the top-level document perpetually in a 'loading' state.

Comment 5

[Steve Jorgensen]

I'm having the same problem trying to print a page from the OnPoint credit union site. I have tried reloading the page. Perhaps OnPoint is also doing something to keep the page in a perpetually 'loading' state? Is there a way to check for that?