W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2019

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

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Mon, 08 Jul 2019 21:34:55 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-509401046-1562621694-sysbot+gh@w3.org>
I doubt Firefox would ever explore a modal prompt for this. I suspect a "block first" approach is better.

But that doesn't mean we cannot expose the permission. For instance, we could expose what is implicit today, which is that granting camera or microphone access has this IP leaking side effect (mockup):

<img src="https://user-images.githubusercontent.com/3136226/60744114-f4d9bd80-9f63-11e9-8f85-7b4dccfbc863.png" width="500">

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".

We've always been adamant that camera and microphone permission should not be persisted by default, to prevent uninitiated snooping, but I don't think those same concerns extend to IP mode. That part sort of just happened.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2175#issuecomment-509401046 using your GitHub account
Received on Monday, 8 July 2019 21:34:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:25 UTC