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

> If you give developer a tool looks very simple, but actually difficult to use correctly, the result is not ideal.

But the tool isn't the problem (the problem being "custom progress indicators get messed up if not done right") here, it's what the devs want to do -- and that's not changing.

> Overlapping XHRs are hard to handle. 

Again, already a problem, if the user does something to trigger multiple XHRs at once, a site not designed to handle it will stumble.

Most of the problems you list are problems with giving devs the XHR API; not with a busy indicator.

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