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.
Same problem in 26.0 Workaround: - Go to drive - Right-click on the spreadsheet - Choose "Preview" - Print works as expected.
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.
This happens on OSX and Linux as well.
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.
Component: Untriaged → Printing
Product: Firefox → Toolkit
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?
2 years ago
platform-rel: --- → ?
2 years ago
Whiteboard: [platform-rel-Google][platform-rel-GoogleDocs][platform-rel-GoogleSheets] → [platform-rel-Google][platform-rel-GoogleSuite][platform-rel-GoogleSheets]
platform-rel: ? → ---
You need to log in before you can comment on or make changes to this bug.