151815 2015-12-03 12:02:05 -0800 Asynchronously call onerror when a content blocker blocks a link element's load 2020-02-19 21:31:00 -0800 1 1 1 Unclassified WebKit WebKit Misc. WebKit Nightly Build All All NEW InRadar P2 Normal --- 1 am webkit-unassigned achristensen krzysztof.modras mjs webkit-bug-importer oldest_to_newest 1145999 0 am 2015-12-03 12:02:05 -0800 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. 1612365 1 am 2020-01-29 02:07:39 -0800 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 1620595 2 mjs 2020-02-19 02:38:36 -0800 Does this cause website compatibility issues when content blockers block "link" loads? 1620596 3 webkit-bug-importer 2020-02-19 02:38:43 -0800 <rdar://problem/59584713> 1620620 4 am 2020-02-19 03:37:35 -0800 > 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. 1621073 5 mjs 2020-02-19 21:31:00 -0800 It would raise the priority if this caused real compatibility issues when using content blockers, rather than just being a question of technical correctness.