Integrate Fetch and "AppCache" or remove "AppCache"

[annevk]

The fix for #95 leaves "AppCache" slightly broken based on the expectation that it will be removed. If removing "AppCache" is no longer likely a year and a bit from now we should reevaluate and consider defining "AppCache" properly in terms of Fetch. (And move parts of the processing model into Fetch, most likely.)

[wanderview]

Should we mark it deprecated? I believe both Firefox and Chrome have intentions to remove it in the future.

In the meantime, it would be nice to at least spec that appcache is disabled when the page is being controlled by a service worker handling FetchEvent.

[annevk]

It's already marked deprecated. The other issue is https://www.w3.org/Bugs/Public/show_bug.cgi?id=27482 which @jungkees will provide a PR for at some point.

[wanderview]

Ok, sorry for my confusion.

[jakearchibald]

F2F: Chrome really needs to drop appcache for HTTP (as do other browsers, as it's a security risk). Then we can start phasing it out further when other browsers ship service worker.

We really hope we can drop this before we have (well, @annevk has) to do a ton of spec work about it.

[jakearchibald]

Thought from @wanderview: Browsers could display "This site may be compromised" on appcache over HTTP.

[jakearchibald]

…although the above may result in the user just using another browser which doesn't show such scary warnings.

[brucelawson]

Can we drop Appcache, though? Are many sites using it? And are there usecases for it that SW doesn't easily meet? Eg, making mostly-textual sites work offline?

…

-- Bruce Lawson www.brucelawson.co.uk www.twitter.com/brucel