Re: CfC: Mixed Content to PR; deadline July 6th.

Anne van Kesteren <annevk@annevk.nl> wrote:

> On Tue, Jul 7, 2015 at 4:16 PM, Brian Smith <brian@briansmith.org> wrote:
> > [...] any use of fetch() by a service worker to fetch a
> > non-secure resource will fail due the pre-connect blocking in section
> 5.2.
>
> "no-cors" is not blocked.
>

Are you basing that this?:
on https://w3c.github.io/webappsec/specs/mixedcontent/#should-block-fetch

My reading of that section makes me thing that every fetch() is blocked by
step 7.2, because "fetch" is not optionally-blockable mixed content. Only
"video", "audio", and "img" are optionally-blockable mixed content.

Cheers,
Brian