- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Mon, 17 Jun 2013 12:25:11 +0200
- To: public-media-capture@w3.org
(keeping the generic discussion on the list rather than in buganizer - the thread can get long) I think we should not have an option if we don't have a really compellling reason to have one - behaviour that changes according to decisions taken elsewhere tends to complicate the API. On 06/14/2013 02:45 PM, bugzilla@jessica.w3.org wrote: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=22365 > > Bug ID: 22365 > Summary: The spec should explicitly say something about > getUserMedia() in an iframe. > Classification: Unclassified > Product: WebRTC Working Group > Version: unspecified > Hardware: All > OS: All > Status: NEW > Severity: normal > Priority: P2 > Component: Media Capture and Streams > Assignee: public-media-capture@w3.org > Reporter: adam.bergkvist@ericsson.com > CC: public-media-capture@w3.org > > I think we should allow this. There was a suggestion to not allow > getUserMedia() in an iframe [1], but the people who expressed their opinions > seemd to have a different view. > > A possible way to keep some of the increased security, gained by not allowing, > is to disallow it by default, but let the main page to opt in to allow an > iframe to use getUserMedia(). > > [1] http://lists.w3.org/Archives/Public/public-media-capture/2012Mar/0085.html > was this the wrong link? This link points to Dom's request to abandon the two-callbacks pattern.
Received on Monday, 17 June 2013 10:25:44 UTC