Looks like the TAG reviewed this back in 
2021: https://github.com/w3ctag/design-reviews/issues/620
Can you update the Chromestatus entry to include the review?
Has anything significant changed with the feature since then?

-- Dan

On Tuesday, February 10, 2026 at 1:44:59 PM UTC-8 Chromestatus wrote:

> *Contact emails*
> [email protected]
>
> *Specification*
> https://immersive-web.github.io/plane-detection 
>
> *Summary*
> The WebXR Plane Detection API allows sites to retrieve the set of planes 
> detected in the user's environment. This is both less work for developers 
> and more powerful than using the depth-sensing WebXR feature as planes such 
> as walls that are occluded by objects can still be fully represented if the 
> system is aware of the boundaries of the wall. (Whereas a depth map would 
> show the wall, but it would be broken up by any objects in front of the 
> wall, potentially obscuring the full scope of the wall). Further, semantic 
> labeling information is exposed where the device is aware of such labels 
> and they fit into predefined categories, allowing better knowledge about 
> the world. 
>
> *Blink component*
> Blink>WebXR 
> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EWebXR%22>
>
> *Web Feature ID*
> Missing feature 
>
> *Motivation*
> *No information provided* 
>
> *Initial public proposal*
> *No information provided*
>
> *TAG review*
> *No information provided* 
>
> *TAG review status*
> Issues addressed 
>
> *Risks*
>
>
> *Interoperability and Compatibility*
> *No information provided* 
>
> *Gecko*: Defer (https://github.com/mozilla/standards-positions/issues/1346) 
> Presumptive 
> Defer due to that being the state of all other WebXR positions due to 
> current lack of support/development.
>
> *WebKit*: No signal (
> https://github.com/WebKit/standards-positions/issues/608)
>
> *Web developers*: Positive
>
> *Other signals*:
>
> *WebView application risks*
>
> Does this intent deprecate or change behavior of existing APIs, such that 
> it has potentially high risk for Android WebView-based applications? 
> *No information provided* 
>
>
> *Debuggability*
> *No information provided* 
>
> *Will this feature be supported on all six Blink platforms (Windows, Mac, 
> Linux, ChromeOS, Android, and Android WebView)?*
> No 
> WebXR itself is only support on Android and Windows, and not on Android 
> WebView. This will be supported on all platforms, but primary usage is 
> expected to be on Android. 
>
> *Is this feature fully tested by web-platform-tests 
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?*
> Yes 
>
> https://wpt.fyi/results/webxr/plane-detection?label=experimental&label=master&aligned
>  
> Infrastructure issues exist on wpt.fyi, but tests do pass within Chromium CQ
>
> *Flag name on about://flags*
> webxr-plane-detection 
>
> *Finch feature name*
> WebXRPlaneDetection 
>
> *Rollout plan*
> Will ship enabled for all users
>
> *Requires code in //chrome?*
> False
>
> *Tracking bug*
> https://crbug.com/394636076
>
> *Estimated milestones*
> Shipping on desktop 147 
> Shipping on Android 147 
>
> *Anticipated spec changes*
>
> 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). 
> *No information provided*
>
> *Link to entry on the Chrome Platform Status*
> https://chromestatus.com/feature/5177993049800704?gate=6532572282748928
>
> This intent message was generated by Chrome Platform Status 
> <https://chromestatus.com>. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/65f682a1-5e3c-413d-a79e-6db0be0ae7f6n%40chromium.org.

Reply via email to