- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Sep 2016 09:26:04 +0000
- To: public-media-capture-logs@w3.org
Yes, this is information that the consumer of the track needs to have available, it's linked to the track, and it's not known to the track's producer. (The use case that drove this particular discussion is a case where we have a cable coming in to a device running a browser, and the app knows what's at the other end of the cable, but the browser doesn't). The alternatives I see are to add more API on the track to set it (a track property, which is empty unless the user has set it), or to stretch the constraint mechanism to cover this case. Is there a standards-process difference in how we'd handle those two cases? -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/391#issuecomment-245542586 using your GitHub account
Received on Thursday, 8 September 2016 09:26:15 UTC