Browser interop issues

[aboba]

Moved from: w3c/webrtc-svc#49 (comment)

Hello, thank you for all your effort on this!

Since Chrome 111 allows working with SVC, we had a first look at this feature and we've found some issues due to the usage of MediaCapabilities.encodingInfo():

• MediaCapabilities.encodingInfo() type webrtc vs transmission (configuration type "transmission" should be replaced with "webrtc" mdn/content#25223)
• Safari's special behaviour to show supported: true and add a supportedConfiguration object to the result (Scalable Video Codec prevent incorrect Safari usage webrtc/samples#1596)
• Chrome >= 101 already reports supported: true for type webrtc and scalabilityMode parameter (Scalable Video Codec include an SVC support check webrtc/samples#1597)

[chrisn]

Discussed in Media WG meeting 12 December 2023 (minutes).

• webrtc vs transmission looks to be a Firefox issue, perhaps @alastor0325 can confirm. Gecko has not implemented webrtc for decodingInfo().
• configuration was added to the spec in Changes to MediaConfigurations cannot be feature detected in older UAs. #111 and Expose "configuration" to the DOM. #115, but there's an inconsistency if the spec says configuration and Safari uses supportedConfiguration. Chrome and Firefox return neither. @jernoble
• In the meeting, you mentioned the Chrome issue has been fixed?

[chrisn]

We should also show configuration in the Examples.

[markafoltz]

It looks like Safari is still using MediaCapabilitiesDecodingInfo.supportedConfiguration while Chrome does not set this property.

https://jsfiddle.net/kpof8612/