Once we have an asynchronous alternative we can simply remove getCapabilities() as far as the spec is concerned unless we want to document its behavior in legacy interface extensions section. For backwards compatibility, until it is safe to remove it from implementations without breaking the web platform, its probably best to let implementations support getCapabilities() the way it is implemented today. I.e. add a deprecation warning but continue to return whatever the implementation is able to know synchronously. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2539#issuecomment-645297815 using your GitHub accountReceived on Wednesday, 17 June 2020 10:42:28 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:51 UTC