NEW 151815
Asynchronously call onerror when a content blocker blocks a link element's load 
https://bugs.webkit.org/show_bug.cgi?id=151815
Summary Asynchronously call onerror when a content blocker blocks a link element's load
Andrey Meshkov
Reported 2015-12-03 12:02:05 PST
The same as for https://bugs.webkit.org/show_bug.cgi?id=151649 but about "link" element. The difference is that in case of "link" element "onerror" is not called at all. Example: http://jsfiddle.net/82ez45js/11/ To see what's going on block webkit.org with a content blocker.
Attachments
Add attachment proposed patch, testcase, etc.
Andrey Meshkov
Comment 1 2020-01-29 02:07:39 PST
This issue is still present in the latest Safari version. This is strange that Safari behavior is inconsistent, "link" is processed differently from "script" which was fixed: https://bugs.webkit.org/show_bug.cgi?id=151649
Maciej Stachowiak
Comment 2 2020-02-19 02:38:36 PST
Does this cause website compatibility issues when content blockers block "link" loads?
Radar WebKit Bug Importer
Comment 3 2020-02-19 02:38:43 PST
<rdar://problem/59584713>
Andrey Meshkov
Comment 4 2020-02-19 03:37:35 PST
> Does this cause website compatibility issues when content blockers block "link" loads? It may cause compatibility issues as triggering "onerror" is a common way to let web pages know that a resource is not available. The previous issue (151649, about "script" tag) was causing a few. This one is not as important, though.
Maciej Stachowiak
Comment 5 2020-02-19 21:31:00 PST
It would raise the priority if this caused real compatibility issues when using content blockers, rather than just being a question of technical correctness.
Note You need to log in before you can comment on or make changes to this bug.