W3C home > Mailing lists > Public > public-media-capture@w3.org > January 2016

Re: [mediacapture-fromelement] HTML Media Element captureStream() should avoid protected/encrypted content

From: Miguel Casas <mcasas@google.com>
Date: Mon, 11 Jan 2016 07:40:41 -0800
Message-ID: <CAPUS086aV232Ei_9O+e=k+FFGr2au7RM3BopGexaRZ=x+cC3Fg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: jan-ivar via GitHub <sysbot+gh@w3.org>, public-media-capture@w3.org
Martin, can't we have protected content of a Single Source Origin?
And what should be done if such situation ever arises, start capturing
blanks, fire an Event, throw an Exception?

On 10 January 2016 at 19:10, Martin Thomson <martin.thomson@gmail.com>
wrote:

> That is the entire point of section 5:
> http://w3c.github.io/mediacapture-fromelement/#security-considerations
>
> "Protected" content is always cross-origin, that is how this works.
> On Jan 9, 2016 1:30 PM, "Miguel Casas-Sanchez via GitHub" <
> sysbot+gh@w3.org> wrote:
>
>> miguelao has just created a new issue for
>> https://github.com/w3c/mediacapture-fromelement:
>>
>> == HTML Media Element captureStream() should avoid protected/encrypted
>>  content ==
>> [HTMLMediaElement.captureStream() &
>> co](http://w3c.github.io/mediacapture-fromelement/#methods) should
>> probably avoid capturing if the HTML element is protected/encrypted,
>> and very likely throw an Exception, the same as Canvas.captureStream()
>>  throws a SecurityError exception.
>>
>> Please view or discuss this issue at
>> https://github.com/w3c/mediacapture-fromelement/issues/20 using your
>> GitHub account
>>
>>


-- 

Miguel Casas-Sanchez | Gatopardo del Software | ydog <ydog@google.com> /
mcasas@google.com | +1 (650) 603 1380
Received on Monday, 11 January 2016 15:41:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:35 UTC