[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
Tue May 10 16:14:25 PDT 2016


--- Comment #6 from Michael Catanzaro <mcatanzaro at igalia.com> ---
(In reply to comment #5)
> Created attachment 278532 [details]
> 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. 

This seems like desirable behavior, and it's still implied by the candidate recommendation (see comment #2) that's being developed by Chrome folks. Alex, I think this is a duplicate of bug #146706, which is now fixed; do you agree?

> 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.

I guess this was our behavior prior to bug #146706. 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.

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/20160510/3ae485ca/attachment.html>

More information about the webkit-unassigned mailing list