Comment 22 for bug 526482

With CUPS and *some* drivers Firefox honours all the print queue parameters *except* resolution. It initially offers 300dpi irregardless of the queue settings and without lpoptions being invoked on the client machine. I am not concerned with the setting sticking if changed by a user as I believe the only sticky setting should be the one which Firefox has got from

   lpoptions <printer_queue> -l

It knows what it is but for some reason it insists that the queue resolution must be 300dpi in spite of being informed it is something else like 600dpi. It is not even consistent in its view because it only does this with some drivers.

Why? The ppd produced by the CUPS+Gutenprint v6.2.6 has the line

  *Resolution 300dpi/300x300 DPI: "<</HWResolution[300 300]/cupsCompression 3>>setpagedevice"

Change 300dpi to 301dpi or 300dp or 300x300dpi. Now the Firefox print dialogue displays the correct queue resolution.

Firefox has no problem with the Foomatic/pixmono (en) driver. If a queue is 150dpi in resolution Firefox displays that. No defaulting to 300dpi in this case. Its ppd has

  *PrinterResolution 300x300dpi/300 DPI: "%% FoomaticRIPOptionSetting: PrinterResolution=300x300dpi"

Note the difference in the format.

My theory is Firefox looks for 300dpi and defaults to that value if it is found. If not found it displays the queue value it already knows. It should stop doing this.