This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Seems the WebAppSec WG attempted to make xhr.open() throw NetworkError for some errors that could be detected synchronously such as mixed content. What's the status of that?
Sorry. I meant SecurityError. It has been removed on this change. https://github.com/w3c/webappsec/commit/aac819b28287e8fd3a9ebad2666336e2bc77a24b So, the consensus is: - to handle it as network error - in async mode, not throwing but dispatching an error event async Right?
OK. Anne objected to the plan at https://lists.w3.org/Archives/Public/public-webappsec/2014Oct/thread.html#msg198
Maybe the same argument applies to the proposal of making send() throw. Just wanna confirm what Anne think of that.
Yes, send() should only throw for synchronous XMLHttpRequest. Not otherwise. Now that Mixed Content is defined in terms of fetching this should all fall out naturally, no? To recap, the status is that WebAppSec dropped their attempt and instead integrate with Fetch.
Takeshi, can this be closed?
OK. Please close. I'll reopen when necessary. Thanks!