- From: Klaus Weidner <klausw@google.com>
- Date: Fri, 17 Jan 2020 14:15:53 -0800
- To: public-immersive-web@w3.org
- Message-ID: <CAFU2V81JH0jPZth-bXgEC4F9Vp7tfEGhJ=vsT1sTAga4r42YWQ@mail.gmail.com>
A quick status update on the DOM Overlay proposal's status. In case you haven't seen it yet, please see the draft spec at https://github.com/immersive-web/dom-overlays . There aren't any outstanding pull requests at this time, and the open issues are largely about clarifications and extensions for headsets, so please take a look and let us know what you think about the current state. Chrome currently supports this as an experimental API, and as of yesterday's Canary 81.0.4029.2 the implementation should match the draft spec. It requires an ARCore-compatible Android phone <https://developers.google.com/ar/discover/supported-devices> and enabling "WebXR AR Module" and "WebXR Incubations" in chrome://flags. There's a test page at https://storage.googleapis.com/chromium-webxr-test/latest.html?target=proposals/phone-ar-hit-test.html?debugSources=true%26iframe=true which includes a visualization of XR events and input source status, best viewed in landscape mode. The reddish square at the bottom right is a cross-origin iframe to demonstrate how that affects input events. (The draft spec has a section discussing that.) A slightly more fun example is this remote control car <https://klausw.github.io/a-frame-car-sample/index.html>, that uses DOM Overlay for an onscreen joystick and exit button.
Received on Friday, 17 January 2020 22:16:11 UTC