- From: Jan-Ivar Bruaroey <jib@mozilla.com>
- Date: Fri, 28 Feb 2020 11:12:07 -0500
- To: public-webrtc@w3.org
- Message-ID: <4bda4460-2bcc-2562-1569-7ea967dcd183@mozilla.com>
I support publishing the current content-hints draft as a Working Draft On 2/20/20 12:03 PM, Bernard Aboba wrote: > This is a Call for Consensus (CfC) to push the editor's draft of > Content-Hints, https://w3c.github.io/mst-content-hint/ out as a new > Working Draft. > The CfC will last for one week, and will end on Friday, February 28, > 2020 at 16:00 UTC > > In response, please state one of the following: > > * I support publishing the current content-hints draft as a Working > Draft > * I object to publishing the current content-hints draft as a > Working Draft, due to issues filed in open bug <#number>. > > Bernard, for the Chairs > > Explanation > > Since the last CfC for a Content-Hints WG Draft > <https://lists.w3.org/Archives/Public/public-webrtc/2019Jul/0066.html> > (which went out on July 24, 2019), the specification has been > revised. Changes include: > > * Clarification of the behavior in various specifications triggered > by content-hint values, to address the following issues: > o https://github.com/w3c/mst-content-hint/issues/28 > o https://github.com/w3c/mst-content-hint/issues/29 > o https://github.com/w3c/mst-content-hint/issues/30 > > * Moving degradationPreference from WebRTC-PC to content-hints. > This was the subject of a previous CfC: > https://lists.w3.org/Archives/Public/public-webrtc/2019Oct/0087.html >
Received on Friday, 28 February 2020 16:12:23 UTC