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: Mon, 25 Nov 2019 13:21:10 +0100
Message-ID: <CAKXHy=d8sjftYSRUF3KbrUTP5kWdic64PkwEDvF6X0OOW9cBwg@mail.gmail.com>
To: Web Application Security Working Group <public-webappsec@w3.org>
Cc: Samuel Weiler <weiler@w3.org>, Wendy Seltzer <wseltzer@w3.org>, Dan Veditz <dveditz@mozilla.com>
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
>
Received on Monday, 25 November 2019 12:21:26 UTC

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