Open Bug 606852 Opened 15 years ago Updated 3 years ago

Improper Printing from Pop Up Window

Categories

(Core :: Printing: Output, defect)

2.0 Branch
x86
Windows 7
defect

Tracking

()

UNCONFIRMED

People

(Reporter: Jack.Smith, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6) Gecko/20100101 Firefox/4.0b6 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6) Gecko/20100101 Firefox/4.0b6 Web site produces a pop up window with mailing address information. Printing the window from FF yields small boxes with hex values. Internet Explorer 8 works correctly. Reproducible: Always Steps to Reproduce: 1.Go to http://www.qrz.com/ to look up information on amateur radio station 2. Enter a callsign in the search box. For example N4ZR and execute search 3. Information returns on the licensee. 4. If you have logged into the site (free site but have to register) and if you click on the callsign in large blue letters, a second window will open with the licensees name and address, formatted to be printed as a mailing label for an envelope. 5. The mailing label appears correct. 6. Select PRINT and instead of the text displayed, the printer outputs square boxes with hex code inside each box. 7. There is no problem printing with Internet Explorer 8. 8. I assume this is some sort of Unicode incompatibility. Actual Results: For example |00| |50| instead of P for a letter. Expected Results: Print label correctly
This happened to me today. I had to resort to using evil, evil IE to print a shipping label for USPS via PayPal.
Do you still see this using Firefox 4 final?
Version: unspecified → 4.0 Branch
Reporter, are you still seeing this issue with Firefox 4.0.1 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Component: General → Printing: Output
Product: Firefox → Core
QA Contact: general → printing
Version: 4.0 Branch → 2.0 Branch
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.