Re: [whatwg/xhr] Allow developers to opt-out of sync XHR with feature policy (#178)

@eligrey genuinely curious, is there another (anti-)pattern that ties UI responsiveness to network conditions?  The browser is inherently event-driven, and the most common events it deals with are user input and network call resolution.  I'm not aware of any way to tell the UI thread to block completely until a user-input event occurs, and sync XHR is the only way I can think of to block until network resolution.  I saw this argument made in the other issue I just replied to, but nobody seemed to have any examples.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/178#issuecomment-364198241