- From: Glen Little <notifications@github.com>
- Date: Thu, 04 Jun 2015 16:26:41 -0700
- To: whatwg/xhr <xhr@noreply.github.com>
Received on Thursday, 4 June 2015 23:27:08 UTC
To me, this is very strange. When I click on a link to go to another page, the browser UI become unresponsive as it goes to get that page. I have a few cases in my code that I *need* the browser to wait while it talks to the server using XHR. The user has just clicked a button, and is expecting a short wait. If I can't do that call synchronously, I'll have to build an artificial approach to freeze the UI until the response is received! I can live with a "warning" in the developer terminal, but to remove this feature from the spec is going to hurt a lot! --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/xhr/issues/20#issuecomment-109091495
Received on Thursday, 4 June 2015 23:27:08 UTC