You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea was for JS to query permissions of individual media devices, which is only useful on browsers that implement per-device permissions, currently Firefox. Mozilla, however, won't be implementing it over fingerprinting concerns that would extend beyond those of other browsers.
There are currently zero implementations, one (manual) WPT, and AFAIK no implementations planned.
I propose we remove this API (the deviceId part of permissions.query) from this spec and mediacapture-output.
The text was updated successfully, but these errors were encountered:
jan-ivar
changed the title
deviceId in permissions.query({name: "camera" | "microphone})
deviceId in permissions.query() is a huge fingerprinting surface.
Jul 17, 2023
jan-ivar
changed the title
deviceId in permissions.query() is a huge fingerprinting surface.
deviceId in permissions.query() remains unimplemented & is a fingerprinting surface
Jul 17, 2023
jan-ivar
changed the title
deviceId in permissions.query() remains unimplemented & is a fingerprinting surface
deviceId in permissions.query() is unimplemented fingerprinting surface
Jul 17, 2023
This spec's Permissions Integration section extends the permission spec's PermissionDescriptor with the deviceId member, for
"camera"
,"microphone"
, and"speaker-selection"
permissions.The idea was for JS to query permissions of individual media devices, which is only useful on browsers that implement per-device permissions, currently Firefox. Mozilla, however, won't be implementing it over fingerprinting concerns that would extend beyond those of other browsers.
There are currently zero implementations, one (manual) WPT, and AFAIK no implementations planned.
I propose we remove this API (the
deviceId
part ofpermissions.query
) from this spec and mediacapture-output.The text was updated successfully, but these errors were encountered: