-
Notifications
You must be signed in to change notification settings - Fork 40
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
Define when gUM rejects with required PTZ constraints #228
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. Maybe add an example of passing {pan: 1}
to getUserMedia as well?
Done in 9ab6635 |
@reillyeon The issue I'm seeing is that we would currently simply reject the |
I guess this is an implementation issue actually. @riju If that looks good to you as well, please merge. |
Looks good, I guess we need to keep a track of this bug, which can help Chrome in not leaking information. |
Will track w3c/mediacapture-main#697 |
And I've created #229 |
As discussed with @guidou, we should make it clear how
getUserMedia()
can reject when PTZ constraints are required.This currently means
getUserMedia({video: {pan: 1}})
for instance rejects with anOverConstrainedError
. We should think about how to make sure we don't leak camera PTZ capabilities when user didn't grant access yet.@reillyeon @eehakkin @riju @andypaicu