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

Should we treat PTZ constraints given to getUserMedia as booleans #270

Closed
youennf opened this issue Oct 21, 2020 · 2 comments
Closed

Should we treat PTZ constraints given to getUserMedia as booleans #270

youennf opened this issue Oct 21, 2020 · 2 comments

Comments

@youennf
Copy link
Contributor

youennf commented Oct 21, 2020

Following on TPAC meeting, it seems there is a desire to have a model where pan, tilt and zoom constraints given to getUserMedia are for device selection. It would be thus recommended to pass booleans there.
For applyConstraints however, given the device is already selected, it makes sense to not pass boolean but pass numerical values. It would be thus recommended to pass numerical values there.

We should probably make it clear in specs and examples that this is the recommended way.
We could also decide to mandate that behavior in the spec and always treat pan tilt zoom constraints in getUserMedia as if they are true whenever present.

@murillo128
Copy link

I don't knot the background of the discussion so maybe I am missing something, but anyway.

Having params boolean values in gUM for PTZ seems correct, but I would recommend changing the name of the attributes to avoid confusion, something like zoomSupported,tiltSupported and panSupported. May require to refactor the dictionaries though.

@jan-ivar
Copy link
Member

This was addressed by #271 and w3c/mediacapture-main#766.

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

No branches or pull requests

3 participants