Re: [w3c/ServiceWorker] register service worker on another domain (Issue #1631)

I haven't currently dig into web share so much as atm, web share is still not so wildly adopted (chrome only did something for windows and android - can't test it in Mac), so i'm currently looking into a solution that can instead POST a `<form target="https://b.com">` from `a.com` if that can be possible. But it first has to have registered a service worker and be able to handle (intercept fetch events)

I'm also thinking of other postMessage solutions too atm. but i would like to avoid iframes if at all possible.
hidden iframes could be a nice solution to install service worker, save something in indexeddb and then navigate to the external service.

or something even more crazier like > navigate to `b.com` > install a service worker on `b.com` > redirect back to `a.com` where you came from > then make a form submit to `b.com` from `a.com`
But this might be a bit bizarre if i'm only doing this to get around a problem with 3th party cookies being disabled...

I have found one other possible solution to install a service worker on another domain with the Web Payment api a long time ago when i played with it, but i'm not so sure about that, think it requires a payment dialog popup to even install the service worker on an external domain...

maybe i can use portals and postMessage also to do some magic, going to look into that as well...

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1631#issuecomment-1066771783
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1631/1066771783@github.com>