<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - It's impossible to detect that XMLHttpRequest is blocked by mixed content blocking"
href="https://bugs.webkit.org/show_bug.cgi?id=145717#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - It's impossible to detect that XMLHttpRequest is blocked by mixed content blocking"
href="https://bugs.webkit.org/show_bug.cgi?id=145717">bug 145717</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=145717#c5">comment #5</a>)
<span class="quote">> Created <span class=""><a href="attachment.cgi?id=278532&action=diff" name="attach_278532" title="test">attachment 278532</a> <a href="attachment.cgi?id=278532&action=edit" title="test">[details]</a></span>
> test
>
> While playing with HSTS, I came across this. We call the onreadystatechange
> with readyState == 1 then readyState == 4 and status 0, then call the
> onerror. </span >
This seems like desirable behavior, and it's still implied by the candidate recommendation (see <a href="show_bug.cgi?id=145717#c2">comment #2</a>) that's being developed by Chrome folks. Alex, I think this is a duplicate of <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [Content Extensions] Make blocked async XHR call onerror"
href="show_bug.cgi?id=146706">bug #146706</a>, which is now fixed; do you agree?
<span class="quote">> Chrome and Firefox just call onreadystatechange with readyState
> == 1 then stop. I think our behavior is more correct, but I don't see it
> specified anywhere.</span >
I guess this was our behavior prior to <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [Content Extensions] Make blocked async XHR call onerror"
href="show_bug.cgi?id=146706">bug #146706</a>. The old behavior broke YouTube for us with adblocker enabled; YouTube would wait for a horrible timeout before starting to play videos, because it thought the ad was still loading.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>