Make InputDeviceInfo.getCapabilities() return empty for cameras that are unavailable to the UA because they are opened in exclusive mode by other applications. The only platform affected in practice is Windows, which is the only platform that exhibits the issue.
The proposed behavior change on Windows has low risk in that this change addresses a situation that is rare in practice and applications written to spec are not expected to break from this change.
Applications that don't handle the case that a given property in the result of getCapabilities() may not be present might experience some minor breakage, but this is expected to be very low both in frequency and severity. In terms of interoperability with other browsers, Blink is the only engine that currently implements InputDeviceInfo.getCapabilities() on Windows, so the existing interoperability risk is largely unchanged.
This feature is part of the larger MediaStreams API and is used together with other functions in that API such as enumerateDevices and getUserMedia.
No.
No.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
The feature is implemented on all platforms. However, the behavior change covered by this PSA only applies in practice to Windows because it addresses a situation that only occurs on that platform (cameras opened in exclusive mode).
Shipping on desktop | 122 |
DevTrial on desktop | 121 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
None