Re: [fetch] XHR option to trigger busy indicators (#19)

@jussi-kalliokoski
I got your point, but explicitly setting busy indicator has a few problem in my opinion:

* browsers currently don't use busy indicator for busy computation, so if a web app does, it seems counter intuitive.

* managing the state of busy indicator explicitly can be error-prone. If someone forgets to turn it off in a single code path, a web app may look busy for a surprisingly long time in some situation.

* currently it is hard or impossible to monitor IO operations that are not initiated directly by script, so if we want to implement a faithful busy indicator, this problem should be resolved first.


---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/19#issuecomment-102396442

Received on Friday, 15 May 2015 13:22:59 UTC