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.

Sign up for GitHub

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

Jump to bottom

AudioContextOptions sinkId should only be allowed in a secure context #2598

Open
mjwilson-google opened this issue Aug 21, 2024 · 0 comments
Open

AudioContextOptions sinkId should only be allowed in a secure context #2598

mjwilson-google opened this issue Aug 21, 2024 · 0 comments
Labels
category: enhancement Substantive changes that do not add new features. https://www.w3.org/policies/process/#class-3 Needs Discussion The issue needs more discussion before it can be fixed. Priority: Eventually "nice to have". https://speced.github.io/spec-maintenance/about/ size: S Small amount of work expected to resolve.

Comments

@mjwilson-google
Copy link
Contributor

AudioContext.setSinkId is only allowed in secure contexts.

However, a sink ID may also be passed into the AudioContext contructor, and the constructor may be called from an insecure context.

We don't specify what happens if this occurs in an insecure context. I think it should probably throw a NotAllowedError.

We can specify this right below the "If sinkId is specified, [...]" section of the AudioContext constructor steps.
@mjwilson-google mjwilson-google added category: security/privacy Needs Reporter Feedback The issue needs feedback from the reporter. https://speced.github.io/spec-maintenance/about/ labels Aug 21, 2024
@mjwilson-google mjwilson-google added category: enhancement Substantive changes that do not add new features. https://www.w3.org/policies/process/#class-3 Needs Discussion The issue needs more discussion before it can be fixed. Priority: Eventually "nice to have". https://speced.github.io/spec-maintenance/about/ size: S Small amount of work expected to resolve. and removed category: security/privacy Needs Reporter Feedback The issue needs feedback from the reporter. https://speced.github.io/spec-maintenance/about/ labels Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
category: enhancement Substantive changes that do not add new features. https://www.w3.org/policies/process/#class-3 Needs Discussion The issue needs more discussion before it can be fixed. Priority: Eventually "nice to have". https://speced.github.io/spec-maintenance/about/ size: S Small amount of work expected to resolve.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mjwilson-google