Re: [w3c/ServiceWorker] should Client.navigate() reject on uncontrolled clients? (#1254)

> Hmm, I think we should lift the restriction and perhaps look at some way of opting back into it.

Right. Perhaps the client could call `preventDefault()` in the `beforeunload` event? Showing at least a dialog would be an improvement for my use case, although it's unfortunate that the web app would have no way of informing the user what's going on, especially if it detects that the new SW is unsigned (and therefore presumed malicious).

It doesn't work today in Chrome and Firefox because:

> Blocked attempt to show a 'beforeunload' confirmation panel for a frame that never had a user gesture since its load. https://www.chromestatus.com/feature/5082396709879808

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