Re: [webrtc-pc] Permission API for receive-only media and data use cases (#2175)

The BT prompt seems especially hard to reason about.
And the more a user faces such prompts, the more the user might disregard all prompts.

> This might even help Firefox explore persisting this "direct connection" permission after initial gUM, for parity with Chrome (which is why I drew it as "Allowed" instead of "Allowed Temporarily".

That would further entice developers in calling getUserMedia when they do not have host candidates (for good or bad reasons) since this will be a one-time call.

Ideally, we would be able to identify legit uses of RTCPeerConnection.
Or we would identify cases where leaking the host candidate is not a privacy issue.

GitHub Notification of comment by youennf
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 9 July 2019 21:08:52 UTC