- From: Maxim Salnikov <notifications@github.com>
- Date: Fri, 30 Nov 2018 05:20:06 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 30 November 2018 13:20:28 UTC
>From this post: "The `downloadTotal` property we pass during the background fetch registration is the total number of bytes of the whole set. It’s also optional. If passed, it works as a guard — we’ll get `backgroundfetcherror` event in the service worker if the total size of the resources is larger. Also, it’s a good helper for our UI to show the correct download percentage if needed. Unfortunately, there is another bug: at least on Mac OS this number can’t be larger than `2147483647` (2 GB) which is the maximum size of *one file* in the file system but it’s intended to be the maximum total size of the *whole set*. I’m going to submit a bug to the Chromium Bug Tracker about this. Meanwhile, if the total set size doesn’t bypass 2GB (like in our case) our calculations are correct." But I might be wrong in my assumptions :) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/279#issuecomment-443201222
Received on Friday, 30 November 2018 13:20:28 UTC