RE: "Officially" deprecating main-thread synchronous XHR?

As I understand it, that is one of the scenarios covered by the recently proposed Beacon API:
http://www.w3.org/TR/beacon/


Sent from my Windows Phone
________________________________
From: Scott González
Sent: 2/7/2014 9:33 AM
To: Anne van Kesteren
Cc: Jonas Sicking; Domenic Denicola; olli@pettay.fi; public-webapps@w3.org
Subject: Re: "Officially" deprecating main-thread synchronous XHR?

What about developers who are sending requests as the page is unloading? My understanding is that sync requests are required. Is this not the case?

On Friday, February 7, 2014, Anne van Kesteren <annevk@annevk.nl<mailto:annevk@annevk.nl>> wrote:
On Fri, Feb 7, 2014 at 6:18 PM, Jonas Sicking <jonas@sicking.cc> wrote:
> Agreed. I think for this to be effective we need to get multiple browser
> vendors being willing to add such a warning. We would also need to add text
> to the various versions of the spec (whatwg and w3c).

For what it's worth, was done when Olli brought this up in #whatwg:
http://xhr.spec.whatwg.org/#sync-warning


--
http://annevankesteren.nl/