Bug 110800

Summary: SVG with animated filters doesn't render properly in WebKit nightly
Product: WebKit Reporter: lars.sonchocky-helldorf
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: bfulgham, fmalita, pdr, schenney, simon.fraser, thorton, zimmermann
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
test-svg-animation.svg none

lars.sonchocky-helldorf
Reported 2013-02-25 14:20:27 PST
Created attachment 190125 [details] test-svg-animation.svg The attached SVG doesn't render properly in WebKit nightly but in Chrome 24 and higher (did not try earlier version): The filters aren't applied. To see how it should look like open the file in Google Chrome.
Attachments
test-svg-animation.svg (3.28 KB, image/svg+xml)
2013-02-25 14:20 PST, lars.sonchocky-helldorf 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Philip Rogers
Comment 1 2013-02-26 12:37:41 PST
This is working for me on Chrome at tip of trunk. Could this be a Chrome vs Safari difference? You can confirm with Chrome Canary (roughly equivalent to WebKit nightly but with Chromium's feature flags turned on).
lars.sonchocky-helldorf
Comment 2 2013-02-26 13:01:11 PST
(In reply to comment #1) > This is working for me on Chrome at tip of trunk. Could this be a Chrome vs Safari difference? > > You can confirm with Chrome Canary (roughly equivalent to WebKit nightly but with Chromium's feature flags turned on). It says so in the bug's title. Maybe I should have written: Chrome 24 and later. It's not a Chrome but a (Safari)-WebKit nightly issue.
Philip Rogers
Comment 3 2013-02-26 13:03:05 PST
(In reply to comment #2) > (In reply to comment #1) > > This is working for me on Chrome at tip of trunk. Could this be a Chrome vs Safari difference? > > > > You can confirm with Chrome Canary (roughly equivalent to WebKit nightly but with Chromium's feature flags turned on). > > It says so in the bug's title. Maybe I should have written: Chrome 24 and later. It's not a Chrome but a (Safari)-WebKit nightly issue. I'm sorry, I misunderstood. CC'ing some Safari experts.
Brent Fulgham
Comment 4 2022-07-15 16:07:05 PDT
Safari, Chrome, and Firefox all agree on rendering for this test case. I don't believe there is any remaining compatibility issue.
Note You need to log in before you can comment on or make changes to this bug.