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

[mediacapture-record] Can .start() throw a SecurityError?

From: jan-ivar via GitHub <sysbot+gh@w3.org>
Date: Sat, 16 Apr 2016 12:00:08 +0000
To: public-media-capture@w3.org
Message-ID: <issues.opened-148845579-1460808008-sysbot+gh@w3.org>
jan-ivar has just created a new issue for 

== Can .start() throw a SecurityError? ==
The following text is quite troubling it if doesn't (emphasis mine):
> "If at any point the stream's isolation properties change so that 
MediaRecorder is no longer allowed access to it, the UA must stop 
recording, discard any data that it has gathered and throw a 
SecurityError DOMException followed by the stop event. If the UA is 
unable to start recording or at any point is unable to continue 
recording ***(i.e., for reasons other than a security violation)***, 
it must throw an UnknownError DOMException, followed by a 
dataavailable event containing the Blob it has gathered, follwed by 
the stop event."

(Nevermind that it's impossible to "throw a SecurityError" for runtime
 errors, I think it means fire the `error` event.)

If `.start()` doesn't throw `SecurityError` then this is a hole big 
enough to drive an already isolated stream through (since a stream 
doesn't really "change" if it starts out, and stays, isolated).

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-record/issues/55 using your GitHub
Received on Saturday, 16 April 2016 12:00:10 UTC

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