Merge pull request #2245 from w3c/aboba-patch-3

Mark VAD and dtx as "features at risk"
w3c · Aug 15, 2019 · 5b2cc41 · 5b2cc41
2 parents 1a2a324 + eeefe98
commit 5b2cc41
Showing 1 changed file with 12 additions and 0 deletions.
diff --git a/webrtc.html b/webrtc.html
@@ -655,6 +655,12 @@ <h2>Dictionary <dfn>RTCOfferAnswerOptions</dfn>
                 This option allows the application to provide information about
                 whether it wishes this type of processing enabled or
                 disabled.</p>
+                <div class="issue atrisk">
+                <p>Support for the <code>voiceActivityDetection</code> attribute of
+                <code><a>RTCOfferAnswerOptions</a></code> is marked
+                as a feature at risk, since there is no clear
+                commitment from implementers.</p>
+              </div>
               </dd>
             </dl>
           </section>
@@ -6966,6 +6972,12 @@ <h2>Dictionary <code><a>RTCRtpEncodingParameters</a></code>
               then discontinuous operation will be turned off regardless of the
               value of <code>dtx</code>, and media will be sent even when silence
               is detected.</p>
+              <div class="issue atrisk">
+                <p>Support for the <code>dtx</code> attribute of
+                <code><a>RTCRtpEncodingParameters</a></code> is marked
+                as a feature at risk, since there is no clear
+                commitment from implementers.</p>
+              </div>
             </dd>
             <dt data-tests="RTCPeerConnection-transceivers.https.html,RTCRtpParameters-encodings.html"><dfn data-idl><code>active</code></dfn> of type <span class=
             "idlMemberType">boolean</span>, defaulting to