Re: [w3c/ServiceWorker] clarify secure context requirements in Handle Fetch (#890)

Changing plan:

- Remove the secure context check of the source client in Handle Fetch step 12.1
  . The original intention was to check it against the target client, but we don't have any control over the target client at this stage
- Add a step (to HTML navigation algorithm) that checks whether the source client that triggered this navigation is secure context
  . If it's not a secure context, disown the `window.opener` of the target client
- Add a step (to HTML navigation algorithm) that checks whether the newly created environment setttings object (target client) is secure context
  . If it's not a secure context, it won't get a controller

This change requires progress on https://github.com/w3c/ServiceWorker/issues/870.

-- 
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/890#issuecomment-241643492

Received on Tuesday, 23 August 2016 06:55:35 UTC