Bug 15709

Summary: Image appears as broken image icon when printing
Product: WebKit Reporter: Ortwin Zillgen <dddd>
Component: PrintingAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: emacemac7, mrowe
Priority: P2 Keywords: InRadar
Version: 523.x (Safari 3)   
Hardware: Mac (Intel)   
OS: OS X 10.4   
URL: http://dddd.mettre.de/d/display.html?webkit
Attachments:
Description Flags
it's a printing issue, see the PDF, it's obvious
none
PDF generated by Leopard Safari none

Ortwin Zillgen
Reported 2007-10-26 06:29:53 PDT
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
Attachments
it's a printing issue, see the PDF, it's obvious (409.35 KB, application/pdf)
2007-10-26 06:38 PDT, Ortwin Zillgen 		no flags
Details
PDF generated by Leopard Safari (460.69 KB, application/pdf)
2007-10-26 08:01 PDT, Mark Rowe (bdash) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ortwin Zillgen
Comment 1 2007-10-26 06:38:56 PDT
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)
Comment 2 2007-10-26 07:26:38 PDT
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)
Comment 3 2007-10-26 07:59:55 PDT
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)
Comment 4 2007-10-26 08:01:49 PDT
Created attachment 16879 [details] PDF generated by Leopard Safari
Mark Rowe (bdash)
Comment 5 2007-10-26 08:03:14 PDT
<rdar://problem/5561689>
Ortwin Zillgen
Comment 6 2007-10-26 09:25:02 PDT
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)
Comment 7 2007-10-26 09:30:12 PDT
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
Comment 8 2007-10-26 09:38:56 PDT
(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.
Note You need to log in before you can comment on or make changes to this bug.