W3C home > Mailing lists > Public > public-media-capture@w3.org > July 2013

[Bug 22594] New: noaccess / peerIdentity as constraints

From: <bugzilla@jessica.w3.org>
Date: Mon, 08 Jul 2013 15:43:46 +0000
To: public-media-capture@w3.org
Message-ID: <bug-22594-5753@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22594

            Bug ID: 22594
           Summary: noaccess / peerIdentity as constraints
    Classification: Unclassified
           Product: WebRTC Working Group
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Capture and Streams
          Assignee: public-media-capture@w3.org
          Reporter: dom@w3.org
                CC: public-media-capture@w3.org

[ Tracking for http://www.w3.org/mid/1373012764.3351.8.camel@cumulustier ]

The latest media capture and streams editors draft describes the
noaccess and peerIdentity constraints:
http://dev.w3.org/2011/webrtc/editor/getusermedia.html#isolated-media-streams

But the text is ambiguous as to whether these are constraints on the
MediaStream or per MediaStreamTrack.

Based on my understanding, we want them as constraints for the whole
MediaStream. There are at least two reasons for that:
* they don't fit well with the other track-constraints — e.g. they can't
be optional, and presumably they can't be applied later once the stream
has been obtained
* they influence addStream() which is at the stream level, not at the
track level

If so, they should be removed from the list of registered constraints in
13.1, and instead be added as MediaStreamConstraints in 11.2.1; the text
in "Isolated Media Streams" would also need to be clarified in that
regard.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Monday, 8 July 2013 15:43:47 UTC

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