Browser interop issues - Githubissues

aboba commented 1 year ago

Moved from: https://github.com/w3c/webrtc-svc/issues/49#issuecomment-1465980206

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 (https://github.com/mdn/content/issues/25223)
Safari's special behaviour to show supported: true and add a supportedConfiguration object to the result (https://github.com/webrtc/samples/issues/1596)
Chrome >= 101 already reports supported: true for type webrtc and scalabilityMode parameter (https://github.com/webrtc/samples/issues/1597)

chrisn commented 11 months ago

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 #111 and #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 commented 10 months ago

We should also show configuration in the Examples.

w3c / media-capabilities

Browser interop issues #203