Bug 48462

Summary: SVG content gets opaque white background
Product: WebKit Reporter: Michael O'Rourke <mkorourk>
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: helder.magalhaes, jeffschiller, krit, mdelaney7, zimmermann
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows 7   
Bug Depends on: 10687    
Bug Blocks:    
Attachments:
Description Flags
Content referenced by example HTML files
none
HTML which brings in SVG content via <embed>
none
HTML which brings in SVG content via <img> none

Michael O'Rourke
Reported 2010-10-27 13:44:01 PDT
Created attachment 72079 [details] Content referenced by example HTML files When SVG content is brought into HTML via the <object> or <embed> tags the unpainted background of the SVG content is rendered as opaque white. When SVG content in brought into HTML via the <img> tag the unpainted background of the SVG content is rendered as transparent. It seems that the <img> tag behaviour is far more useful for compositing content and the correct model for SVG content. Using the <img> tag is undesirable as it seems to treat the SVG content as an image and then text selection and links in text do not work. These do work when the content is brought in with <object> or <embed> but then the opaque white background limits the usefulness of SVG content.
Attachments
Content referenced by example HTML files (591 bytes, image/svg+xml)
2010-10-27 13:44 PDT, Michael O'Rourke
no flags
HTML which brings in SVG content via <embed> (322 bytes, application/xhtml+xml)
2010-10-27 13:44 PDT, Michael O'Rourke
no flags
HTML which brings in SVG content via <img> (324 bytes, application/xhtml+xml)
2010-10-27 13:45 PDT, Michael O'Rourke
no flags
Michael O'Rourke
Comment 1 2010-10-27 13:44:42 PDT
Created attachment 72080 [details] HTML which brings in SVG content via <embed>
Michael O'Rourke
Comment 2 2010-10-27 13:45:00 PDT
Created attachment 72081 [details] HTML which brings in SVG content via <img>
Dirk Schulze
Comment 3 2010-10-27 22:47:26 PDT
The reason seems to be http://trac.webkit.org/browser/trunk/WebCore/rendering/RenderBoxModelObject.cpp#L646 Not sure what the SVG spec is saying.
Jeff Schiller
Comment 4 2010-10-27 23:25:59 PDT
WORKSFORME Please check with a nightly webkit. This was fixed for Bug 10687 and the embed displays with a transparent background on my nightly build.
Dirk Schulze
Comment 5 2010-10-28 01:12:46 PDT
(In reply to comment #4) > WORKSFORME > > Please check with a nightly webkit. This was fixed for Bug 10687 and the embed displays with a transparent background on my nightly build. I couldn't check the examples of above, since the circle.svg is not included, nor accessible. But I guess he's not talking about the transparence level, but the color. Can it be that the background of the embedded SVG's are transparent white and on image transparent black? If so, we should make it consistent. This can make a difference on some compositing modes.
Dirk Schulze
Comment 6 2010-10-28 01:13:37 PDT
Hm, maybe I misinterpreted the original comment, sorry.
Michael O'Rourke
Comment 7 2010-10-28 12:05:07 PDT
Bug 10687 does sound like it is the same issue and should resolve my problem. Sorry about that. I'll try out the nightly build. Is there a way to tell what version of webkit is in Chrome? So that I can see when the fixed webkit build gets into my Chrome?
Helder Magalhães
Comment 8 2011-01-27 01:59:08 PST
(In reply to comment #4) > WORKSFORME > > Please check with a nightly webkit. This was fixed for Bug 10687 and the embed displays with a transparent background on my nightly build. I confirm this fixed as well (on Windows Vista SP2 with Chrome 10.0.648.6 dev) - I'd vote this closed as well: WFM (as Jeff suggested) or even as a dup. of bug 10687, as that underlying issue is more generic and also older than this one (although a dependency was already set). :-) BTW: Great work in #10687, Jeff! ;-)
Alexey Proskuryakov
Comment 9 2011-01-27 11:31:04 PST
Please feel free to re-open if this is still an issue. *** This bug has been marked as a duplicate of bug 10687 ***
Note You need to log in before you can comment on or make changes to this bug.