Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Background Fetch #149

Open
marcoscaceres opened this issue Mar 15, 2023 · 3 comments
Open

Background Fetch #149

marcoscaceres opened this issue Mar 15, 2023 · 3 comments
Assignees
Labels
concerns: maintenance It's not clear the proposal is getting maintained. concerns: privacy This proposal may cause privacy risk if implemented from: Google Proposed, edited, or co-edited by Google. venue: WICG Proposal is incubated in the Web Incubator Community Group

Comments

@marcoscaceres
Copy link
Contributor

marcoscaceres commented Mar 15, 2023

Request for position on an emerging web specification

Information about the specification

See also https://developer.chrome.com/blog/background-fetch/.

Design reviews and vendor positions

Bugs tracking this feature

Anything else we need to know

An API to handle large uploads/downloads in the background with user visibility.

@marcoscaceres marcoscaceres added from: Google Proposed, edited, or co-edited by Google. venue: WICG Proposal is incubated in the Web Incubator Community Group labels Mar 15, 2023
@dmurph
Copy link

dmurph commented Mar 16, 2023

@mkruisselbrink did a recent poke at WPT tests (and hopefully they can add more knowledge) and I think the summary was there are testing gaps around the various cross origin and CORS scenarios, so that would be a good area to focus some attention on.

@annevk annevk added concerns: privacy This proposal may cause privacy risk if implemented concerns: maintenance It's not clear the proposal is getting maintained. labels Mar 16, 2023
@annevk
Copy link
Contributor

annevk commented Mar 16, 2023

I filed a number of issues on this in the past, which makes me concerned about maintenance:

(Some are addressed, but definitely not all.)

Apart from that I think the main concern here is the browser performing activity for the website while the end user is no longer visiting it. Even if you limit that up to the point where the end user switches networks, that would still reveal something about their activity. Potentially you could make this more visible through "download UI", but it's not immediately clear to me how that would work. Maybe a combination of a randomized time limit or the user switching networks, both enforced after closing the relevant tabs, could suffice?

I think there was tentative agreement that any script could run upon the next visit, but it would be good to confirm that is still the case.

@youennf
Copy link

youennf commented Mar 16, 2023

I think there is a path forward with background fetch, in terms of browser UI, mitigations mentioned by Anne and the ability to postpone firing non user initiated events.

It would help if the spec would migrate to service worker WG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
concerns: maintenance It's not clear the proposal is getting maintained. concerns: privacy This proposal may cause privacy risk if implemented from: Google Proposed, edited, or co-edited by Google. venue: WICG Proposal is incubated in the Web Incubator Community Group
Projects
Development

No branches or pull requests

5 participants