- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 06 Jul 2015 08:26:25 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
Received on Monday, 6 July 2015 15:27:08 UTC
It seems there is some interest from at least Mozilla in exposing this. I think the promise API proposed by @gaearon is the most promising. Maybe the constructor approach from @bloodyowl minus the progress bits (boolean seems fine given OS indicators to date). Though looking at https://w3c.github.io/wake-lock/ I wonder why @marcoscaceres ended up with just a property as API. whatwg/fetch is probably not the best place to hash this out. If some people here would like to turn this into something I can create whatwg/busy so there's a better place to evolve this. Any takers? (@duanyao you might be interested in #65. I don't think we want to tie a Busy Indicator API to fetching though. There's a number of other things such as WebSocket and WebRTC that are network-related and might cause a page to be busy. And I suppose we could even use it for non-network things.) --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/19#issuecomment-118890471
Received on Monday, 6 July 2015 15:27:08 UTC