NEW 275843
[LBSE] Invalid filter effects should not render 
https://bugs.webkit.org/show_bug.cgi?id=275843
Summary [LBSE] Invalid filter effects should not render
Rob Buis
Reported 2024-06-25 01:48:06 PDT
Invalid filter effects should not render.
Attachments
tesy-invalid-filters (730 bytes, text/html)
2024-07-02 10:12 PDT, Said Abou-Hallawa 		no flags
Details
safari display (567.59 KB, image/png)
2024-07-02 10:17 PDT, Said Abou-Hallawa 		no flags
Details
chrome display (564.41 KB, image/png)
2024-07-02 10:17 PDT, Said Abou-Hallawa 		no flags
Details
firefox display (550.22 KB, image/png)
2024-07-02 10:17 PDT, Said Abou-Hallawa 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Rob Buis
Comment 1 2024-06-25 01:48:35 PDT
An example of this is svg/filters/feConvolveMatrix-invalid-targetX.svg.
Radar WebKit Bug Importer
Comment 2 2024-07-02 01:49:13 PDT
<rdar://problem/130951885>
Said Abou-Hallawa
Comment 3 2024-07-02 10:12:18 PDT
Created attachment 471789 [details] tesy-invalid-filters HTML elements with invalid CSS filters or referenced SVG filters are displayed without the filter. But SVG elements with invalid SVG filters are not displayed at all. See the attached test case. Where did we get this weird behavior? Is this speced somewhere?
Said Abou-Hallawa
Comment 4 2024-07-02 10:14:58 PDT
I personally prefer to see the element displayed without the filter more than displaying nothing.
Said Abou-Hallawa
Comment 5 2024-07-02 10:17:20 PDT
Created attachment 471790 [details] safari display
Said Abou-Hallawa
Comment 6 2024-07-02 10:17:33 PDT
Created attachment 471791 [details] chrome display
Said Abou-Hallawa
Comment 7 2024-07-02 10:17:48 PDT
Created attachment 471792 [details] firefox display
Said Abou-Hallawa
Comment 8 2024-07-02 10:18:29 PDT
Safari, Chrome and Firefox disagree in displaying the attached test case.
Said Abou-Hallawa
Comment 9 2024-07-02 10:29:21 PDT
Submitted https://github.com/whatwg/html/issues/10455
Said Abou-Hallawa
Comment 10 2024-07-03 10:21:12 PDT
I filed https://github.com/w3c/fxtf-drafts/issues/564.
Note You need to log in before you can comment on or make changes to this bug.