Re: [webrtc-extensions] Add normative steps to getCapabilities() or deprecate it in favor of an async API (#57) from Bernard Aboba via GitHub on 2022-01-06 (public-webrtc-logs@w3.org from January 2022)

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Thu, 06 Jan 2022 02:44:48 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1006240246-1641437087-sysbot+gh@w3.org>

At this point, I don't seem much implementer interest in replacing `getCapabilities()` with an async API.  To some extent the existing specification does document implementation-dependent behavior (e.g. that `getCapabilities()` can return different information when called before versus after `createOffer()` or `createAnswer()`.  So can we close this issue? 

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


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

Received on Thursday, 6 January 2022 02:44:50 UTC