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

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

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Mon, 07 Oct 2019 11:35:58 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-503395520-1570448157-sysbot+gh@w3.org>
youennf has just created a new issue for https://github.com/w3c/mediacapture-main:

== applying constraints on an ended track ==
I did https://jsfiddle.net/2kpdbnyz/ to test applyConstraints and getSettings on an ended track.
Testing Firefox, Chrome and Safari, all browsers behave differently:

- Firefox is resolving applyConstraint promise for ended track, getSettings returns an empty dictionary for ended tracks
- Safari tis resolving applyConstraint promise for ended track, getSettings returns some parameters that applyConstraints can change
- Chrome is rejecting applyConstraint promise for ended tracks (at least if some constraints are set), getSettings returns a reduced set of the settings after the track is ended (deviceId, groupId)

Looking at the spec, all implementations could potentially qualify as being compliant.
It would be better though to get some alignment there.
We could special case applyConstraints/getSettings for ended tracks, something like:
- Resolve applyConstraints promise early if track is ended
- Return deviceId/groupId settings if track is ended

Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/628 using your GitHub account
Received on Monday, 7 October 2019 11:35:59 UTC

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