Hello, Uploads have been supported for a few years now. You can try it out on backgroundfetch.com (by ticking the *Fetch request with body* option).
If you are getting fetch errors, it could be because this is a cross-origin request? Make sure you have the appropriate CORS headers in place to allow for that. Thanks, ~Rayan On Tue, Oct 11, 2022 at 8:13 AM maasa yoshida <[email protected]> wrote: > Hello, > > I am eagerly awaiting support for the upload functionality of this API. > It would be a great experience if users of my application could close a > tab while uploading a huge file and the upload would continue. > > Am I correct in understanding that uploading is not yet implemented right > now? > (I tried it at hand and got a "fetch-error". I thought it must be because > preflight requests are not yet supported.) > > I would like to know if there are any plans regarding the implementation > of uploading. > Or is there any reason why it cannot happen? > > Thanks, > yoshiko > 2020年4月14日火曜日 20:06:08 UTC+9 [email protected]: > >> Hi, >> >> Here's a relevant excerpt from the spec: >> >>> The user agent may also consider setting bgFetch’s paused flag if the >>> user is on a metered connection, or the background fetch was started in the >>> background. >> >> >> Different browsers can implement this part differently. If you have spec >> issues you can file them here: >> https://github.com/WICG/background-fetch/issues/. >> >> Thanks, >> ~Rayan >> >> On Tue, Apr 14, 2020 at 11:49 AM [email protected] < >> [email protected]> wrote: >> >>> Thanks Rayan. >>> >>> > Yes this is intentional. Background Fetches initiated anywhere other >>> than the top level window start in a suspended state. >>> then I wanna discuss about this spec, not a crbug. >>> >>> if that is intentional, is that behavior based on (bgfetch, pbs, sw) >>> spec ? >>> or based on chrome own security/privacy considerations ? >>> if other browser implements bgfech & pbs, they should behave same ? or >>> depends on their intervention ? >>> >>> now I'm trying build Podcast app over PWA. >>> Podcast usually sync xml feed in background (pbs) >>> and if feed includes mp3, fetch in background (bgfetch) >>> >>> I wanna discuss this use-cased should covered by bgfetch + pbs or should >>> not. >>> >>> thanks >>> Jxck >>> >>> >>> >>> 2020年4月14日(火) 19:00 Rayan Kanso <[email protected]>: >>> >>>> Hi, >>>> >>>> Yes this is intentional. Background Fetches initiated anywhere other >>>> than the top level window start in a suspended state. >>>> >>>> If you have other issues or feedback, please file a bug using crbug.com >>>> with the Blink>BackgroundFetch component. >>>> >>>> Thanks, >>>> ~Rayan >>>> >>>> On Mon, Apr 13, 2020 at 8:04 PM Jxck Jxck <[email protected]> >>>> wrote: >>>> >>>>> Hi >>>>> >>>>> I tried this API, and register bgfetch task from window works fine. >>>>> but register task from sw doesn't works. >>>>> >>>>> 1. register bgfetch task from service worker (via 'sync', >>>>> 'periodic-sync' etc) >>>>> 2. task registered successful but suspended. >>>>> 3. if resume from system UI, fetch starts. >>>>> >>>>> I wanna register bgfetch in background, and also download in >>>>> background. >>>>> >>>>> I tried this in >>>>> - chrome 81 >>>>> - on android R emulator >>>>> - on MBP catalina >>>>> >>>>> is there any restriction for bgfetch registered from service worker >>>>> (not from window) ? >>>>> >>>>> thanks >>>>> Jxck >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 2019年3月4日月曜日 23時22分23秒 UTC+9 Mugdha Lakhani: >>>>>> >>>>>> Contact emails >>>>>> >>>>>> [email protected], [email protected], [email protected], >>>>>> [email protected] >>>>>> >>>>>> >>>>>> Explainer >>>>>> >>>>>> https://developers.google.com/web/updates/2018/12/background-fetch >>>>>> >>>>>> Spec >>>>>> >>>>>> https://wicg.github.io/background-fetch/ >>>>>> >>>>>> Tag Review >>>>>> >>>>>> https://github.com/w3ctag/design-reviews/issues/279 >>>>>> >>>>>> Test Website >>>>>> >>>>>> https://backgroundfetch.com/ (code here >>>>>> <https://github.com/rayankans/backgroundfetch>) >>>>>> >>>>>> Summary >>>>>> >>>>>> Background Fetch API provides a service worker based download and >>>>>> upload mechanism which is persistent across service worker and browser >>>>>> restarts. >>>>>> >>>>>> The system provides a developer-controllable interface to schedule, >>>>>> query, pause, and cancel background downloads and uploads. After a >>>>>> scheduled fetch completes, the system will notify the developer of the >>>>>> outcome of the operation by sending an event to the service worker. >>>>>> >>>>>> In progress downloads and uploads are handled by the download manager >>>>>> and will be visible to users in a notification. The user will be able to >>>>>> pause and cancel actions from that interface. >>>>>> >>>>>> Downloads and uploads should continue even if the developer's website >>>>>> is not loaded in a tab, and if Chrome is closed, the download should >>>>>> resume >>>>>> when Chrome opens again. >>>>>> >>>>>> Limitations >>>>>> >>>>>> We don’t support background fetch requests requiring CORS preflight >>>>>> at this time. Work on this is in progress. >>>>>> >>>>>> Link to “Intent to Implement” blink-dev discussion >>>>>> >>>>>> >>>>>> https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/Ia9_-CVrl1U/jEBQGVv_BQAJ >>>>>> >>>>>> Origin Trial feedback summary >>>>>> >>>>>> The API has been available through origin trials since Chrome 71. No >>>>>> negative feedback has been received. >>>>>> >>>>>> Will this feature be supported on all five Blink platforms supported >>>>>> by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)? >>>>>> >>>>>> Yes, except WebView. >>>>>> >>>>>> Demo link >>>>>> >>>>>> Demo page <https://bgfetch-http203.glitch.me/>. Video >>>>>> <https://www.youtube.com/watch?v=eLfgf2ZvFpo>. >>>>>> >>>>>> Note: Need to enable >>>>>> chrome://flags/#enable-experimental-web-platform-features >>>>>> >>>>>> Debuggability >>>>>> >>>>>> Background Fetch initiated downloads are clearly identified at >>>>>> chrome://download-internals. >>>>>> >>>>>> rayankans@ is working with the DevTools team to expose background >>>>>> behavior in Chrome, which will be used for Background Fetch as well. >>>>>> >>>>>> Risks >>>>>> >>>>>> Interoperability and Compatibility >>>>>> >>>>>> As this is a new feature which Chrome is leading with, we have >>>>>> solicited community feedback and submitted a complete WPT test suite. >>>>>> >>>>>> >>>>>> Interest from other stakeholders is as follows: >>>>>> >>>>>> Edge: Positive >>>>>> >>>>>> Firefox: Positive >>>>>> <https://github.com/mozilla/standards-positions/issues/30#issuecomment-433044406> >>>>>> >>>>>> Safari: No signal >>>>>> >>>>>> Web developers: Positive (Facebook and LinkedIn are super interested >>>>>> in the uploads support.) >>>>>> >>>>>> Compatibility isn’t an issue. We don’t foresee this breaking any >>>>>> existing websites as it’s a new feature. >>>>>> >>>>>> Ergonomics >>>>>> >>>>>> No adverse effects on Chrome performance are expected. >>>>>> >>>>>> We recommend developers to use the Permissions API to check for >>>>>> background-fetch permission before starting a background fetch, and >>>>>> expect >>>>>> these two APIs to often be used together. >>>>>> >>>>>> Activation >>>>>> >>>>>> The API can be used immediately and easily when shipped. The >>>>>> explainer >>>>>> <https://developers.google.com/web/updates/2018/12/background-fetch> >>>>>> has examples. >>>>>> >>>>>> Is this feature fully tested by web-platform-tests >>>>>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>? >>>>>> Link to test suite results from wpt.fyi. >>>>>> >>>>>> Yes. Test suite here >>>>>> <https://wpt.fyi/results/background-fetch?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned> >>>>>> . >>>>>> >>>>>> Entry on the feature dashboard <http://www.chromestatus.com/> >>>>>> >>>>>> https://www.chromestatus.com/feature/5712608971718656 >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "blink-dev" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fe0dd4f1-7c7a-4ad1-a519-189fe8267560%40chromium.org >>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fe0dd4f1-7c7a-4ad1-a519-189fe8267560%40chromium.org?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL6mntjtVn-DZi3iSL8Hk0z9-9LrBwpF3iuGyk2oLU9WowB88w%40mail.gmail.com.
