Bug 15709 – Image appears as broken image icon when printing

• Status: NEW
• Component: Printing

[Ortwin Zillgen]

this is a GoogleMap-page. Printing doesn't print all symbols and does dithers shadows instead of rendering.
the missing symbols get importet on line 24 of the html-document.
1 missing symbols
2 dithered shadow
3 wrong shadow
4 object isn't transparent (white area)
display on screen is perfect

yes I did search

[Ortwin Zillgen]

Created attachment 16878 [details]
it's a printing issue, see the PDF, it's obvious

it's a printing issue, see the PDF, it's obvious

[Mark Rowe (bdash)]

The URL you provided gives me an alert about the Google API key being invalid.  Could you please provide a working page where we can test this?

[Mark Rowe (bdash)]

The URL is now working.   What I see is that the airport symbol renders as the missing image icon.  The issues with transparency is to be expected as I believe that the Tiger PDF subsystem does not support transparency.  I don't see the white areas on Leopard.  That leaves two issues:

1. Missing image.
2. The poor dithering on the shadows.

I suspect 2 may be an issue outside of WebKit, perhaps in CoreGraphics.

[Mark Rowe (bdash)]

Created attachment 16879 [details]
PDF generated by Leopard Safari

[Mark Rowe (bdash)]

<rdar://problem/5561689>

[Ortwin Zillgen]

are you sure about CoreGraphics?
We found out about the printing, saving the page to 4D 2004 which goes:
WebKit -> PDF -> QuickTime -> jpg, png, tiff
same results with 4D V11 which uses this chain:
WebKit -> PDF -> Quartz -> jpg, png, tiff

this true for X.4.10, Safari 2 and X.5 9A559, Safari 3 = 5523.6

anyway: are you going to file this to the CoreGraphics or the QuickTime team? Thanks!

(In reply to comment #4)
> Created an attachment (id=16879) [edit]
> PDF generated by Leopard Safari
> 

[Mark Rowe (bdash)]

What is a "4D 2004" or "4D V11?  It's not clear what your last comment is saying.  CoreGraphics is involved in the rendering from WebKit to PDF.  The libraries that are used afterwards on the PDF are not really relevant to this from a WebKit point of view that I can see.

[Ortwin Zillgen]

(In reply to comment #7)
> What is a "4D 2004" or "4D V11?  It's not clear what your last comment is
> saying.  CoreGraphics is involved in the rendering from WebKit to PDF.  The
> libraries that are used afterwards on the PDF are not really relevant to this
> from a WebKit point of view that I can see.
> 

correct, it's reproducible by printing from Safari, so our circumstances aren't really relevant.