Re: [whatwg/xhr] Abandon hope of removing sync XHR from the web platform? (#20)

We are working on a product that has JS code dating back 15 years. Not being able to dynamically loading these snippets of code and inject it when needed, while holding back DOM processing, would pretty much cost us 300 hours of refactoring. While this is not impossible, I really don't see the value in removing support for sync execution. How is it different from <p>test</p><script src=".."></script><p>more content</p> behaviorally? I'm aware that the browser would be able to optimize by downloading the JS code asynchronously before executing it synchronously alongside the DOM, but the order of execution is the import part here which is what we use sync XMLHttpRequests for.
I'm fine with Developer Tools throwing **one** warning about the use of Synchronous XMLHttpRequests, but it should not be marked as Deprecated.
Seriously, we are developers, not kids in need of course correction. We can't just rewrite every poorly designed (but functional) snippet of JavaScript out there.

Also, at least give us a time frame - **when** will it be acceptable for browsers to remove the functionality?

-- 
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/20#issuecomment-339606066