[Webkit-unassigned] [Bug 145717] It's impossible to detect that XMLHttpRequest is blocked by mixed content blocking

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=145717

Michael Catanzaro <mcatanzaro at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mcatanzaro at igalia.com

--- Comment #4 from Michael Catanzaro <mcatanzaro at igalia.com> ---
I wonder if this was fixed by bug #146706. TODO: test it out!

(In reply to comment #3)
> 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."

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151111/5655b072/attachment.html>