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

[mediacapture-screen-share] Clarify what audio is captured and what "application" means in the context of restrictOwnAudio (#102)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Feb 2019 13:57:52 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-405712600-1549029470-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/mediacapture-screen-share:

== Clarify what audio is captured and what "application" means in the context of restrictOwnAudio ==
On https://github.com/w3c/mediacapture-screen-share/pull/94/files, @martinthomson wrote:

> "application" here is very vague.  Does it mean:
> 
> 1. the browser
> 2. the specific browser process
> 3. the document origin
> 4. the document
> 5. the window/tab
> 
> Relevant questions I'd like to be able to answer:
> 
> * if capture is initiated from an iframe, does the audio from the parent get captured?
> * similarly, for a parent, does the audio from an iframe get captured?
> * if the same origin is playing audio from multiple tabs, is it only the tab that calls this API that is suppressed, or are all of these expected to be suppressed?
> 
> I realize that there are very few cases where audio comes from multiple sources and the primary use of this will be for origins that want to ensure that their own output, coming from the same page, is not echoed back.  But this does need to be clear.

Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/102 using your GitHub account
Received on Friday, 1 February 2019 13:57:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 June 2019 15:32:54 UTC