Bug 101419

Summary: Filters applied to a <g> via the SVG filter attribute cause their children to repaint (or not) incorrectly
Product: WebKit Reporter: Tim Horton <thorton>
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: dino, jan.boesenberg, karlcow, krit, pdr, simon.fraser, webkit-bug-importer, zimmermann
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 68469    
Attachments:
Description Flags
testcase
none
screenshot
none
rendering in safari, firefox, chrome none

Tim Horton
Reported 2012-11-06 18:46:32 PST
See attached test case. Notice how it's white (in Safari, with tiled mode -- in non-tiled-mode, the first paint is OK, but subsequent paints won't be). Grab with your mouse around 150,150 and drag around. See the screenshot for an example: the path is painted ... sometimes. Sometimes just the shadow is painted. Sometimes neither. Lots of flashes and horribly incorrect invalidation. Applying the filter via CSS seems to work fine.
Attachments
testcase (2.68 KB, text/html)
2012-11-06 18:46 PST, Tim Horton 		no flags
Details
screenshot (52.11 KB, image/png)
2012-11-06 18:47 PST, Tim Horton 		no flags
Details
rendering in safari, firefox, chrome (119.86 KB, image/png)
2026-05-10 20:17 PDT, Karl Dubost 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Tim Horton
Comment 1 2012-11-06 18:46:53 PST
Created attachment 172695 [details] testcase
Tim Horton
Comment 2 2012-11-06 18:47:34 PST
Created attachment 172696 [details] screenshot
Radar WebKit Bug Importer
Comment 3 2012-11-06 18:49:01 PST
<rdar://problem/12650693>
Philip Rogers
Comment 4 2012-11-07 10:56:53 PST
Oh my goodness this is messed up.
Jan Bösenberg
Comment 5 2018-05-17 03:20:13 PDT
Does this bug still persist? It looks solved on Safari 11, maybe it can be closed.
Karl Dubost
Comment 6 2026-05-10 20:17:34 PDT
Created attachment 479585 [details] rendering in safari, firefox, chrome This is working everywhere the same.
Note You need to log in before you can comment on or make changes to this bug.