> Its been suggested before that we could leave the applicationCache global in place, but just make it do nothing in insecure contexts.
I did see this idea of keeping the applicationCache global in one of the bugs, I think if we have breakage we could try this as a follow up piece of work along with other approaches like expiring the cache more often. On Fri, Jan 19, 2018 at 5:47 PM, Ben Kelly <bke...@mozilla.com> wrote: > On Fri, Jan 19, 2018 at 12:26 PM, Mike Taylor <mi...@mozilla.com> wrote: > >> > When the pref is set to false the API will be removed: >> > >> > - >> > >> > window.applicationCache will be removed >> > - >> > >> > The cache service Firefox implements for AppCache will be disabled >> over >> > Insecure Contexts >> > >> > >> > When the pref is set to true the code will produce an additional >> developer >> > console warning about the removal timeline. >> > >> > In Nightly and Early beta for 60; the pref will be set to false removing >> > the API. >> >> It will be interesting to see if we get reports of pages (that don’t >> feature test) throwing with the missing applicationCache global. A few >> years (and laptops) ago I had done some site corpus grepping — I’ll see if >> I can find any of that data. >> > > Its been suggested before that we could leave the applicationCache global > in place, but just make it do nothing in insecure contexts. > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
