w3c / w3c/ServiceWorker

register service worker on another domain

Open
#1,631 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
3.6k
Forks
324
Avg merge
14d 22h
Merged PRs (30d)
1

Description

With Web Share 2.0 it will be possible to share files to other domains.

If i am on page a.com and i wish to share something, and i happen to know another grate service that can handle those file on b.com, then that service also needs to install their service worker and set up share_target in the manifest.

but the visitor have never visited b.com and registered it before...

So the question really is: how can i make it so a.com can trigger b.com to register their service worker even before he/she have visited that page.
One solution i can think of is to create a hidden iframe that installs the service worker. But the the problem with 3th party cookies kicks in and you won't be able to install the service worker.

is there some solution to register a foreign service worker?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Web Share 2.0, service-worker registration, manifest share_target, hidden iframe, and third-party-cookie behavior described in the issue. Research the cross-origin constraints and define what a supported mechanism would need to accomplish for a.com and b.com; done means the question has a documented, technically grounded resolution.

Written by the indexing model from the issue text.

Assessment

Domain
security, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.