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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 3 01:54:19 PDT 2016


youenn fablet <youennf at gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |youennf at gmail.com

--- Comment #7 from youenn fablet <youennf at gmail.com> ---
(In reply to comment #4)
> 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."

This is described in https://fetch.spec.whatwg.org/#main-fetch, xhr being based on fetch in xhr.spec.whatwg.org

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/20160803/753690a7/attachment.html>

More information about the webkit-unassigned mailing list