search

w3c / webappsec-mixed-content

WebAppSec Mixed Content
https://w3c.github.io/webappsec-mixed-content/
Other
12 stars 22 forks source link

Move MIX2 to FPWD #25

Closed carlosjoan91 closed 2 years ago

carlosjoan91 commented 4 years ago

We discussed Mixed Content Level 2 during TPAC, and there was some amount of consensus (and no objections) in moving mixed content in that direction. Chrome is currently planning to start autoupgrades for audio and video mixed content starting in version 80 (to be released in February 2020).

This is a CfC for moving the existing ED to FPWD. Please add any thoughts (preferably here in the issue).

carlosjoan91 commented 4 years ago

I created an FPWD version of the ED document in https://github.com/w3c/webappsec-mixed-content/pull/24

annevk commented 4 years ago

I find it very hard to review as it's not clear compared to Level 1 what is removed, replaced, or added.

Also, I'd expect a Level 2 document to be self-contained and not written as a set of updates to a prior document.

carlosjoan91 commented 4 years ago

Do you think copying the non-changed stuff from Level 1 would be better? That way the doc would be self contained (and can completely replace level 1 once published).

annevk commented 4 years ago

Yeah, that's definitely where we want to end up I think.

carlosjoan91 commented 4 years ago

I sent a PR (https://github.com/w3c/webappsec-mixed-content/pull/30) that merges the still relevant concepts from MIX onto MIX2, could you take a look and see if addresses your concerns @annevk ?

annevk commented 3 years ago

Shall we move forward with this? Or at least make the editor's draft of Mixed Content be the Level 2 version.

carlosjoan91 commented 3 years ago

Happy to move forward if there are no objections, I'll start by making MIX2 be the editor's draft like you suggest (to give folks a chance for more comments since this was dormant for a while) then push it to FPWD if nothing comes in.

wseltzer commented 3 years ago

It would be nice to have the "Latest published version:" link go someplace. Currently, there's nothing at https://www.w3.org/TR/mixed-content-2/

carlosjoan91 commented 3 years ago

Since MIX2 has been fairly stable and no comments have come in, my guess is we can go ahead and start the Transition Request process to FPWD. I'll add this to the next meeting agenda to do one last check before starting it.

In the meantime, I'm trying to figure out how to get bikeshed to build without a "Latest published version" link, since there is none other than the editor's draft.

sideshowbarker commented 2 years ago

Closing this as I believe that with the move of the Mixed Content spec to permanent CRD status — and when the changes in #57 are merged to help clarify that the spec is now being continuously maintained (rather than replaced by a new version) — it’s no longer necessary or useful to do a FPWD for a new rev of the spec (when the changes in #57 are merged there will in fact no longer be any mention at all of the current spec being Level 2; instead it’s unversioned).