Bugzilla

I just bought a copy of Windows 10 64bit and used it to create a VMware Fusion VM (running on macOS 10.15.7). I can't reproduce this bug there (using the current FF release).

The easy way to fix this bug is to do a Windows-specific backout of my patch for bug 1719215. But, as I mentioned above in comment #9, this might open security holes in FF on Windows. The alternative (changing FF's Windows-specific printing code) would be much harder, at least for me. I know nothing about that code, and haven't done any Windows development in decades. This is made even more complicated by the fact that you're only able to reproduce this bug using "Microsoft Print to PDF".

Before we do anything more here, I think we need to find out exactly where and under what circumstances this bug happens. Which versions of Windows? Which default language settings? And so forth.

I tested with the EN_us version of Firefox on the English US version of Windows 10.

I just bought a copy of Windows 10 64bit and used it to create a VMware Fusion VM (running on macOS 10.15.7). I can't reproduce this bug there (using the current FF release).

The easy way to fix this bug is to do a Windows-specific backout of my patch for bug 1719215. But, as I mentioned above in comment #9, this might open security holes in FF on Windows. The alternative (changing FF's Windows-specific printing code) would be much harder, at least for me. I know nothing about that code, and haven't done any Windows development in decades. This is made even more complicated by the fact that you're only able to reproduce this bug using "Microsoft Print to PDF".

Before we do anything more here, I think we need to find out exactly where and under what circumstances this bug happens. Which versions of Windows? Which default language settings? And so forth.

I tested with the en-US version of Firefox on the English US version of Windows 10.

I just bought a copy of Windows 10 64bit and used it to create a VMware Fusion 12.1.2 VM (running on macOS 10.15.7). I can't reproduce this bug there (using the current FF release).

The easy way to fix this bug is to do a Windows-specific backout of my patch for bug 1719215. But, as I mentioned above in comment #9, this might open security holes in FF on Windows. The alternative (changing FF's Windows-specific printing code) would be much harder, at least for me. I know nothing about that code, and haven't done any Windows development in decades. This is made even more complicated by the fact that you're only able to reproduce this bug using "Microsoft Print to PDF".

Before we do anything more here, I think we need to find out exactly where and under what circumstances this bug happens. Which versions of Windows? Which default language settings? And so forth.

I tested with the en-US version of Firefox on the English US version of Windows 10.

I just bought a copy of Windows 10 64bit and used it to create a VMware Fusion 12.1.2 VM (running on macOS 10.15.7). I can't reproduce this bug there (using the current FF release).

The easy way to fix this bug is to do a Windows-specific backout of my patch for bug 1719215. But, as I mentioned above in comment #9, this might open security holes in FF on Windows. The alternative (changing FF's Windows-specific printing code) would be much harder, at least for me. I know nothing about that code, and haven't done any Windows development in decades. This is made even more complicated by the fact that you're only able to reproduce this bug using "Microsoft Print to PDF".

Before we do anything more here, I think we need to find out exactly where and under what circumstances this bug happens. Which versions of Windows? Which default language settings? And so forth.

I tested with the en-US distro of Firefox on the English US version of Windows 10.