- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Fri, 18 Oct 2019 07:32:18 +0000
- To: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
I think the proposal (moving degradationPreference to the content-hint spec) is the right thing to do given that no one has implemented it yet and getting WebRTC 1.0 stable has high priority IMO.
Br,
Stefan
On 2019-10-18, 09:07, "Harald Alvestrand" <harald@alvestrand.no> wrote:
It seems that we missed one feature in our list of unimplemented
features: DegradationPreference -
https://protect2.fireeye.com/v1/url?k=0d569b57-51dc4e52-0d56dbcc-861010bc36ff-745e305a885a5bb1&q=1&e=f6d0c509-33a3-461d-b27f-1240a84d394c&u=https%3A%2F%2Fw3c.github.io%2Fwebrtc-pc%2F%23dom-rtcrtpsendparameters-degradationpreference
No browser has currently implemented support for this beyond setting and
getting its value, according to the reports we have.
The chairs have discussed this issue, and the fact that the
functionality of degradationPreference is significantly overlapping with
what Content-Hint (https://protect2.fireeye.com/v1/url?k=619b7061-3d11a564-619b30fa-861010bc36ff-982fc77a1dc21938&q=1&e=f6d0c509-33a3-461d-b27f-1240a84d394c&u=https%3A%2F%2Fw3c.github.io%2Fmst-content-hint%2F) is intended
to achieve.
We thus suggest that we move the degradationPreference property to the
content-hint spec, so that both of these features can be considered on
their own, without becoming undocumented, and without blocking the
progress of WebRTC 1.0 to Proposed Recommendation.
Comments welcome.
Harald, for the chairs
Received on Friday, 18 October 2019 07:32:22 UTC