- From: Duan Yao <notifications@github.com>
- Date: Fri, 15 May 2015 09:30:53 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Friday, 15 May 2015 16:31:23 UTC
>Most of the problems you list are problems with giving devs the XHR API; not with a busy indicator. It is not meaningful to blame XHR or developers here, because even the brand new Fetch API won't make busy indicator easier to handle. The problem __is__ the explicit state management. UAs already do good jobs at managing the state of busy indicator, why not reuse them? So I suggested `FetchObserver` and `.affectBusyIndicator`, and I believe this solution is hard to get wrong even if you copy-paste other's code blindly. `FetchObserver` also opens a door to many possibilities. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/19#issuecomment-102453662
Received on Friday, 15 May 2015 16:31:23 UTC