I have two printers available to my machine. Webkit uses the opposite one to the default. The behaviour is correct in Safari.
It's probably duplicate of bug 17364.
Are both these printers physical ones? Bug 17364 mentions a virtual printer from Adobe, so I'm curious if that's important.
(In reply to comment #2)
> Are both these printers physical ones? Bug 17364 mentions a virtual printer
> from Adobe, so I'm curious if that's important.
As far as I know, virtual printers act as physical printers. It shouldn't be matter is this a really printer or no.
That's generally true - but there may be hacks hiding somewhere (perhaps in some closed source code) that could affect the behavior, so it helps to have as much detail about the configuration as possible.
They are both physical printers, however a little more experimentation yielded the following:
The default printer is a laser connected to an airport express base station.
The second printer is an inkjet connected directly to the machine.
Webkit ignores the setting of "default printer" in preferences and favours the directly connected printer.
ie. it always prints to the inkjet whether it is the default or not.
File/print (command-P) always defaults to first printer in aphabetical list of printers. It does not use system default printer or the "last printer used" in webkit.
The default printer is used in this situation in Safari, if this is the intended functionality in Webkit - why?
(In reply to comment #0)
> I have two printers available to my machine. Webkit uses the opposite one to
> the default. The behaviour is correct in Safari.
I have same problem. I have a Brother laser, a Brother laser fax and a Canon ink jet. The Brother laser is the default. WebKit defaults to the Canon ink jet.
Per comment #6 and comment #8 marked as confirmed bug. Bug 17364 has the same root problem so I mark that bug as duplicate of this bug, because the bug covers all of cases (not only virtual printers).
*** Bug 17364 has been marked as a duplicate of this bug. ***
*** Bug 18439 has been marked as a duplicate of this bug. ***