resolution: improve compat with non-persistent permissions#1728
Open
resolution: improve compat with non-persistent permissions#1728
Conversation
by not calling it with a empty deviceId and by repopulating the devices select after getUserMedia
Collaborator
Author
|
@nils-ohlmeier says this is a problem in Chrome with non-persistent permissions too |
fippo
changed the title
Collaborator
Author
|
it also seems that OverConstrainedError has an empty error message in that case? cc @guidou |
Collaborator
Author
Contributor
|
Confirmed locally. With this PR applied I'm getting a gUM prompt again and afterwards the demo works as expected. |
nils-ohlmeier
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
by not calling it with a empty deviceId and by
repopulating the devices select after getUserMedia