W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2019

Re: [mediacapture-main] applying constraints on an ended track (#628)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Tue, 08 Oct 2019 12:17:37 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-539485296-1570537056-sysbot+gh@w3.org>
After a track is ended, it shouldn't matter what the constraints are - it won't affect the output (there is none).

deviceId / groupId would seem to make sense to return, because it tells you what the track is attached to - this is info that could let you try to reopen the device, if so desired. I could argue that the other settings should be frozen in time as they were when the track ended, but if we currently don't return them, I don't see a strong reason to bother.

Thinking abstractly, I'd say that attempting to set constraints on a dead track is a silly thing and should be rejected with WrongStateError (or whatever similar error exists). But we're normally claiming that an applyConstraints() that doesn't cause any setting to change should always succeed. I could go either way on that one.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/628#issuecomment-539485296 using your GitHub account
Received on Tuesday, 8 October 2019 12:17:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:29 UTC