Exposes several new mechanisms to customize the behavior of the depth sensing feature within a WebXR session, with the goal of improving the performance of the generation or consumption of the depth buffer. The key mechanisms exposed are: the ability to request the raw or smooth depth buffer, the ability to request that the runtime stop or resume providing the depth buffer, and the ability to expose a depth buffer that does not align with the user's view exactly, so that the user agent does not need to perform unnecessary re-projections every frame.
Web Developers use the depth sensing feature for a number of reasons; however, the existing shape of the API needs some tweaking to accommodate for changes in hardware (non-eye-aligned depth buffers), and to improve performance of developer experiences who often don't need depth sensing during the full scope of their experience.
These features have been designed to work in a backwards compatible way. Sites have to explicitly opt-in to receive any of this new behavior.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
https://wpt.fyi/results/webxr/depth-sensing?label=experimental&label=master&aligned
No milestones specified