Re: [slightlyoff/ServiceWorker] Inconsistencies due to when clients are created (#870)

I think this is a Firefox bug and chrome is more correct.

The current spec says to control windows.  And it says to associate the service worker with the window (i.e. control it)  before firing the FetchEvent.  So there should be an existing controlled client when a navigation FetchEvent is fired.

The problem in Firefox is that we control documents, not windows.  The document does not exist before the navigation, so we don't have a controlling client yet.  There is a bug open for this, but there was some discussion at the last f2f that we might want to change to controlling documents in the spec.  So we have not moved on this.

  https://bugzilla.mozilla.org/show_bug.cgi?id=1237498

In regards to this spec language:

> If client is not a secure context, return null.

I think the spec is trying to check for a non-secure parent window.  It probably needs to be re-worded since it should use the navigation URL security and parent window security to make this determination.

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