Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note on applicability of constraints to tracks in other specs #578

Closed
henbos opened this issue Apr 25, 2019 · 1 comment · Fixed by #594
Closed

Add note on applicability of constraints to tracks in other specs #578

henbos opened this issue Apr 25, 2019 · 1 comment · Fixed by #594
Assignees

Comments

@henbos
Copy link
Contributor

henbos commented Apr 25, 2019

Attempting to interpret how constraints defined in this spec, which was written with MediaStreamTracks generated by getUserMedia() in mind, apply to MediaStreamTracks generated in the contexts of other specs (such as webrtc-pc or mediacapture-screen-share), leads to confusion.

The solution to this under-specificity was to explicitly define what constraints do in the respective specs.

To make this even more clear, let's add a note to mediacapture-main spec clarifying that the constraints defined in this spec are only applicable to MediaStreamTracks generated by getUserMedia(), unless otherwise specified in other specs.

@youennf
Copy link
Contributor

youennf commented May 6, 2019

I agree this should be clarified to know which constraints are to be supported and which are not.
If we think some properties should be/can easily be supported for all sources of a given track type (say video), requirements should be put here and not repeated in each sub spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants