Closed Bug 1462582 Opened 7 years ago Closed 6 years ago

firefox displays boarding pass barcodes at such low resolution that they may not be accepted at checkin

Categories

(Core :: Printing: Output, defect, P3)

Product:
Core
Component:
Printing: Output
Version:
59 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: bdj10, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20180323154952 Steps to reproduce: I checked in for a flight of my wife's on line using my MacBook Pro, and printed out a boarding pass. Actual results: The boarding pass was not accepted and she had to go to the check in desk to get a new one. More recently I printed out a boarding pass, then remembered what happened last time so opened up Safari and did the same there. Safari's printed boarding pass was visibly higher resolution than Firefox's. I can't supply an example as I have no upcoming flights at present (I do have some saved boarding passes but these were emailed to me by the airline and probably don't have this browser-specific problem). Expected results: The process for generating 2D barcodes needs to be fixed so that there is sufficient resolution for them to work properly with airport barcode readers.
Just a thought: my subsequent bug report relating to map display suggests that one might be able to deal with this issue by saving the web page concerned and printing the resulting file, rather than trying to print the boarding pass directly.
Component: Untriaged → Printing: Output
Product: Firefox → Core
Priority: -- → P3
Perhaps this bug should have higher priority, as it might lead to people missing flights?

@bdj10: Very sorry to hear about this. Unfortunately, without a specific example (including information on your printer settings) this is difficult for us to debug or test. We do have some other bugs filed related to bar codes or QR codes not quite printing correctly. We will continue to investigate those. I'm going to close this one since it's not really actionable at this time. Feel free to re-open if you run into it again or have a reproducible example.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.