Bug 193492 - Fuzzy SVG Scaling when styled with drop-shadow
Summary: Fuzzy SVG Scaling when styled with drop-shadow
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Images (show other bugs)
Version: Other
Hardware: Unspecified All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
: 205941 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-01-16 07:00 PST by uta.l
Modified: 2023-08-21 10:35 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description uta.l 2019-01-16 07:00:01 PST 
The problem:
On mouseover zoomed in SVG graphics appear very fuzzy. It should be sharp.

How to reproduce:
1. go to page http://jimmac.musichall.cz/stuff/icon-revolution/
2- mouseover on one of the icons

Version:
Epiphany 3.30.2
WebKitGTK+ 2.22.5
Comment 1 Alexey Proskuryakov 2019-01-17 14:30:46 PST 
Reproduces in Safari on Mac too.
Comment 2 Simon Fraser (smfr) 2019-01-17 14:32:40 PST 
Doesn't seem "very fuzzy" on macOS. Can you attach a GTK screenshot?
Comment 3 Said Abou-Hallawa 2019-01-17 16:46:44 PST 
This happens because the icons has a drop-shadow filter:

.icon.blurred img {
   -webkit-filter: drop-shadow(0 1px 1px rgba(0,0,0,0.4)) drop-shadow(0 1px 10px rgba(0,0,0,0.1));
          filter: drop-shadow(0 1px 1px rgba(0,0,0,0.4)) drop-shadow(0 1px 10px rgba(0,0,0,0.1));
}

If I remove this filter, the icons are scaled as expected on mouse over.
Comment 4 uta.l 2019-01-18 04:26:54 PST 
@Said Abou-Hallawa
Is this intended behaviour though? 

@Alexey Proskurayakov @Simon Fraser (smfr)
Also, could you please claify if it is reproducable on MacOS or not and in which version? It seems like there are two different experiences here. Is the proving screenshot still needed?
Comment 5 Simon Fraser (smfr) 2019-01-18 11:19:33 PST 
Yes.
Comment 6 Radar WebKit Bug Importer 2022-02-08 17:56:45 PST 
<rdar://problem/88663265>
Comment 7 Simon Fraser (smfr) 2023-08-21 10:35:22 PDT 
*** Bug 205941 has been marked as a duplicate of this bug. ***