W3C home > Mailing lists > Public > public-webappsec@w3.org > November 2019

Re: CfC to transition MIX to PR.

From: Mike West <mkwst@google.com>
Date: Wed, 27 Nov 2019 15:05:16 +0100
Message-ID: <CAKXHy=fHoSjV8eg+feaM+39VyTnKWdRbAR7ge9SkgN+M7rg4LA@mail.gmail.com>
To: Emily Stark <estark@google.com>, Wendy Seltzer <wseltzer@w3.org>
Cc: Dan Veditz <dveditz@mozilla.com>, Samuel Weiler <weiler@w3.org>, Web Application Security Working Group <public-webappsec@w3.org>
+Emily

I think Google is mostly focused on the next, stricter version of MIX at
the moment. Emily’s team put out a blog post recently, and there might be
some aspects of that that we could put together about locking in the
requirements of MIX and tightening them in a MIX2 that we could publish at
the same time?

Emily, Carlos, perhaps one of you could send a CFC to publish a first
public working draft of MIX2? Or I could do it for you?

-mike

On Tue 26. Nov 2019 at 17:59, Wendy Seltzer <wseltzer@w3.org> wrote:

> Thanks Mike!
>
> Great to get this moving toward Rec. Do you or anyone else in the group
> want to write a blog post to tell the world about mixed content?
>
> We also have the opportunity to do some more publicity when the spec
> goes to Recommendation. Would any orgs be interested in giving
> testimonials (quotes for a press release) on the subject?
>
> I expect we'd be looking at publishing MIX as Recommendation in January
> 2020 (after AC review).
>
> --Wendy
>
> On 11/25/19 07:21, Mike West wrote:
> > Following up on this, just a _wee_ bit later than expected:
> > https://github.com/w3c/transitions/issues/193.
> >
> > -mike
> >
> >
> > On Fri, Aug 31, 2018 at 9:20 AM Mike West <mkwst@google.com> wrote:
> >
> >> Hey folks!
> >>
> >> MIX has been sitting around as CR for over two years now. I believe we
> >> agreed in last year's TPAC to advance it once we aligned on behavior for
> >> prefetch (tests
> >> <
> https://wpt.fyi/results/mixed-content/link-prefetch-tag?label=experimental
> >),
> >> and to close the `<track>` issue at
> >> https://github.com/w3c/webappsec-mixed-content/issues/13 as WontFix,
> >> aiming for tightening the behavior for `<audio>` and `<video>` in MIX2
> >> rather than loosening anything in MIX1. I didn't actually follow up on
> any
> >> of that (except insofar as we did change Chrome's behavior to match
> >> Firefox's (and the spec) for prefetch!).
> >>
> >> At this point, I think it's past time that we called MIX done. I've
> >> created https://github.com/w3c/webappsec-mixed-content/issues/15 to
> >> discuss transitioning to PR.
> >>
> >> Please comment there within the next two weeks (e.g. by Friday,
> September
> >> 14th) if you have opinions on the matter. :) If the CfC passes, Dan and
> I
> >> will put together a transition request for the AC to chew on to finalize
> >> the transition.
> >>
> >> -mike
> >>
> >
>
>
> --
> Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
> Strategy Lead, World Wide Web Consortium (W3C)
> https://wendy.seltzer.org/        +1.617.863.0613 (mobile)
>
> --
-mike
Received on Wednesday, 27 November 2019 14:05:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:55:09 UTC