Any reason not to request a Gecko position on this? Per https://mozilla.github.io/standards-positions/#webxr they’re Positive on WebXR in general but I don’t think that necessarily implies support for the modules like this one, so it might be good to ask about this specifically.
Thanks, Dan From: Alex Cooper <alcoo...@chromium.org> Date: Thursday, September 12, 2024 at 3:26 PM To: Rik Cabanier <caban...@gmail.com> Cc: blink-dev <blink-dev@chromium.org> Subject: Re: [blink-dev] Intent to Ship: WebXr hand input module - Level 1 You don't often get email from alcoo...@chromium.org. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Thanks Rik, Good catch! The actual impl here is fairly old and I assumed this was something the underlying API already handled. My recent work on the feature has largely been integrating with our permissions framework and the launch process. This CL<https://chromium-review.googlesource.com/c/chromium/src/+/5857347> addresses the issue. I think it should land in time for M130, but if not, I won't enable the feature until it does land. On Wed, Sep 11, 2024 at 1:40 PM Rik Cabanier <caban...@gmail.com<mailto:caban...@gmail.com>> wrote: Awesome to hear to see this shipping on Chrome! Quest browser has supported this API for close to 4 years and it's used by many developers and supported by all WebXR frameworks. Does your implementation ensure that the hand joints are not matched to the user? On Wed, Sep 11, 2024 at 11:35 AM 'Alex Cooper' via blink-dev <blink-dev@chromium.org<mailto:blink-dev@chromium.org>> wrote: Contact emails alcoo...@chromium.org<mailto:alcoo...@chromium.org> Explainer https://github.com/immersive-web/webxr-hand-input/blob/main/explainer.md Specification https://immersive-web.github.io/webxr-hand-input Summary Exposes hand joint data on XrInputSources for use during a WebXr session. This allows developers to have more fine grained interactions during WebXr sessions. Blink component Blink>WebXR<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EWebXR> TAG review https://github.com/w3ctag/design-reviews/issues/568 TAG review status Issues addressed Risks Interoperability and Compatibility None Gecko: No signal WebKit: Shipped/Shipping (https://webkit.org/blog/15443/news-from-wwdc24-webkit-in-safari-18-beta) Web developers: Strongly positive Other signals: Shipped on Meta Quest, Initially added to Chrome for HoloLens support 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? None Debuggability None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? No WebXR is only supported on Windows and Android (not WebView) Is this feature fully tested by web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>? No API shape is relatively simple consisting largely of the enum and a simple idl to get a "joint space", which is used in other tested APIs; however, generating realistic synthetic joint data (~50 poses) is quite difficult and error prone. Further, no test API currently exists to supply this data. https://github.com/immersive-web/webxr-test-api/issues/86 tracks investigating adding such an API. IDL validation: https://wpt.fyi/results/webxr/hand-input?label=experimental&label=master&aligned Flag name on chrome://flags webxr-hand-input Finch feature name WebXRHandInput Requires code in //chrome? False Tracking bug https://crbug.com/359418633 Launch bug https://launch.corp.google.com/launch/4338213 Sample links https://immersive-web.github.io/webxr-samples/immersive-hands.html Estimated milestones Shipping on desktop 130 Shipping on Android 130 Anticipated spec changes None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/6290425179275264?gate=6298185765748736 Links to previous Intent discussions Intent to Prototype: https://groups.google.com/a/chromium.org/forum 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 blink-dev+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz0GZkKBz1Zma9aEdkJj8GMXcLx0nnXbOyKbKG%2BXn37tcw%40mail.gmail.com<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz0GZkKBz1Zma9aEdkJj8GMXcLx0nnXbOyKbKG%2BXn37tcw%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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 blink-dev+unsubscr...@chromium.org<mailto:blink-dev+unsubscr...@chromium.org>. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz0_yujuwxwQTYeqHdA4h8ngVmvygceqoZAnEnKazXkmYw%40mail.gmail.com<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGOLbz0_yujuwxwQTYeqHdA4h8ngVmvygceqoZAnEnKazXkmYw%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- 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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MW4PR00MB14556549CE7B7DF85793CAB2C5642%40MW4PR00MB1455.namprd00.prod.outlook.com.
