Re: [webrtc-extensions] Add normative steps to getCapabilities() or deprecate it in favor of an async API (#57)

> Option 3 is really an implementation choice.

I know this one (blocking-invoke) is "taboo", but in terms owning our mistakes, this seems to be the only option that does not break the usual flow that you mentioned. So it's not "just an implementation choice" if we decide to take that path, but I understand if we don't want to go there.

> Validate/Make sure media capabilities as input to setCodecPreferences is a superior replacement

I like this option. But I agree that if we cannot do that then we do need an async replacement.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/57#issuecomment-747361979 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config