RESOLVED CONFIGURATION CHANGED 155887
Drop Shadow Filter prevents inline SVGs from displaying in Safari 9.1
https://bugs.webkit.org/show_bug.cgi?id=155887
Summary Drop Shadow Filter prevents inline SVGs from displaying in Safari 9.1
Joel G Goodman
Reported 2016-03-25 09:37:02 PDT
Applies to Safari 9.1 and mobile Safari released with iOS 9.3. If a drop-shadow filter is applied via CSS to an inline SVG, the SVG will not be visible. Interestingly enough, the box model is adhered to, and you can still inspect the various SVG parts, they just are not visible. Removing the drop-shadow filter fixes this behavior. I have not tested with any other CSS filters at this point, but drop-shadow filters on SVGs worked prior to the release of Safari 9.1
Attachments
Safari 15.5 matches other browsers (1.72 MB, image/png)
2022-07-18 09:56 PDT, Ahmad Saleem
no flags
Mike Sherov
Comment 1 2016-04-07 13:17:50 PDT
This is affecting https://behance.net as well, we use inline SVG with drop shadow for our appreciation buttons. See here: https://www.behance.net/gallery/35746977/Dolomites-Heart-Of-The-Alps If the filter is removed from the `#appreciation svg` selector, the button rendered just fine.
Matthias Kretschmann
Comment 2 2016-04-29 02:44:37 PDT
In my test (Safari 9.1 / OS X 10.11.4) this is happening with ALL css filters, not just drop-shadow. Here's an isolated test case: https://jsfiddle.net/kremalicious/zf9cnjm0/
Radar WebKit Bug Importer
Comment 3 2016-06-15 09:47:53 PDT
Ahmad Saleem
Comment 4 2022-07-18 09:56:31 PDT
Created attachment 460978 [details] Safari 15.5 matches other browsers I am unable to reproduce this issue based on attached test case in Comment 02 using Safari 15.5 on macOS 12.4. It matches with all other browsers and show alien / vampiric something character and all elements are visible (all legs, hoverboard, teeth etc.). I think it was fixed along the way and can be marked as "RESOLVED CONFIGURATION CHANGED". If I tested incorrectly, please retest accordingly and happy to be educated. Thanks!
Note You need to log in before you can comment on or make changes to this bug.