User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20151029151421 Steps to reproduce: On Windows 8.1 with FF 42. I have experienced this bug on older versions of FF as well, and on Windows XP SP 2 too (til now was too lazy to file a bug, but this really annoyed me today and only today did I figure out what was wrong; may as well be a windows printer driver-related bug). Print page on a printer which redirects to file (tried 3 different PostScript drivers, XPS Writer). After hitting Print, the OS dialog appeared. named the file: C:\albert\BANKA PS\2015-11-21 TD 2186,78.ps Actual results: Firefox flicked the printing page dialog (suspiciously quickly) and continued as usual. *THE ACTUAL OUTPUT WAS IN DEED THE FILE C:\albert\BANKA PS\2015-11-21 TD 2186,78.ps, BUT IT WAS 0 BYTES LONG. SAME HAPPENED WHEN PRINTING ON XPS WRITER, SAVED TO C:\albert\BANKA PS\2015-11-21 TD 2186,78.oxps, OUTPUT WAS EMPTY FILE.* Expected results: The C:\albert\BANKA PS\2015-11-21 TD 2186,78.ps should have been 69kB large and the printing process should have taken a second, however it took 0 seconds. I could achieve this by (strangely) renaming the output file in the Windows print dialog to "C:\albert\BANKA PS\2015-11-21 TD 218678.ps" (without a comma in the file name). This stupid bug has been annoying me for ages and only today did I figure this out. I often print invoices with sums in cents included in the file name in the form USDS,CENTS. The comma in the file name causes FF to silently fail.
Severity: normal → blocker
OS: Unspecified → Windows 8.1
Hardware: Unspecified → x86_64
That's a bug in Windows' XPS drivers, see http://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/bug-in-print-to-pdf-and-print-to-xps-in-windows-10/13e0976f-7bbe-4aec-bffe-c3cded548a49
Severity: blocker → normal
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Component: Untriaged → General
Product: Firefox → Invalid Bugs
Resolution: --- → INVALID
Version: 42 Branch → unspecified
You need to log in before you can comment on or make changes to this bug.