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.

Sign up for GitHub

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

Jump to bottom

Clarify why no background access #8

Open
tomayac opened this issue Jun 10, 2020 · 2 comments
Open

Clarify why no background access #8

tomayac opened this issue Jun 10, 2020 · 2 comments

Comments

@tomayac
Copy link
Contributor

tomayac commented Jun 10, 2020

The current explanation isn't clear to me.

One could imagine a use case where "trending" data is provided regularly to a social networking site via a periodic background sync task. The shortcut to search for the top "trending" term could then be updated dynamically from the service worker in the background.
@aarongustafson
Copy link
Collaborator

Yeah, it may make sense to have this API be available from within a Worker and within the main thread (like Badging).

@rayankans
Copy link
Owner

This ties into #6. Under the assumption that shortcuts are tied to a manifest, I'm not sure how it would be possible to make it work from the background. A service worker can control multiple apps in theory, if a developer sets dynamic shortcuts from there, which app would it be routed to?

Other than that, I see no issue in exposing the API in the background as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aarongustafson @tomayac @rayankans