<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:youennf@gmail.com" title="youenn fablet <youennf@gmail.com>"> <span class="fn">youenn fablet</span></a>
</span> changed
<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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>youennf@gmail.com
</td>
</tr></table>
<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#c7">Comment # 7</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:youennf@gmail.com" title="youenn fablet <youennf@gmail.com>"> <span class="fn">youenn fablet</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=145717#c4">comment #4</a>)
<span class="quote">> I wonder if this was fixed by <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>. TODO: test it out!
>
> (In reply to <a href="show_bug.cgi?id=145717#c3">comment #3</a>)
> > IIRC, Firefox raised an exception from send() in my testing.
>
> To be clear: the candidate recommendation strongly implies we should fire
> onerror and not throw an exception:
>
> "These changes together mean that we’ll no longer throw a SecurityError
> exception directly upon constructing a WebSocket object, but will instead
> rely upon blocking the connection and triggering the fail the WebSocket
> connection algorithm, which developers can catch by hooking a WebSocket
> object’s onerror handler. This is consistent with the behavior of
> XMLHttpRequest, EventSource, and Fetch."</span >
This is described in <a href="https://fetch.spec.whatwg.org/#main-fetch">https://fetch.spec.whatwg.org/#main-fetch</a>, xhr being based on fetch in xhr.spec.whatwg.org</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>