- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Sun, 12 Aug 2018 09:25:52 +0000
- To: public-media-capture-logs@w3.org
making sure I understand what you're proposing: > > 1. MediaStreamTrack objects are only readable by the origin that requested them, unless other constraints cause them to gain a different origin (the peerIdentity constraint for WebRTC does this). when you say "readable", is this shorthand for "copy media content into another object"? > > 2. MediaStreamTrack objects can be rendered if they belong to another origin, but only their size is known. "rendered" = "used for display in a <video> element"? (as opposed to being painted on a canvas?) "known" = "readable by JS from the current origin"? Size is if course not known for audio tracks. Is the frame rate (for video) or sample rate (for video) knowable properties? Clarifying this seems to make a lot of sense, yes. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/529#issuecomment-412330093 using your GitHub account
Received on Sunday, 12 August 2018 09:25:54 UTC