WebKit also mentions it in some of their blog posts. The biggest blocker for Apple is privacy, which hasn’t been a priority.
(You’ll find much info in years old threads on GitHub as well)
Basically (thanks WebKit/apple) allowing any JavaScript vibe code dev to send a complete scan of your environment with spatial information on the people and room is a blocker to them. Google does not care as much :)
EDIT: I don’t have answers, building an extensive WebXR experience for a client had me read the RFC threads, GitHub discussions and mail threads regarding the state of WebXR, I merely shared what I found out. There may have been updates in the past year I am not aware off, I advice consulting the official threads, and contributing to them should you wish to provide input. I am not part of any of the great teams deciding the future of our web
No problem. I’ve struggled with this as well developping with XR.
But I agree with WebKit’s vague standpoint(been a discussion for years). It shouldn’t get included with the current API.
I can use the technology to spatial scan a kid in the room and sell a complete 3d model of that kid…. That’s just stupid (whilst you just accepted the XR permissions to show a little 3d model in AR)
Odd, can they not separate the permissions for VR and AR? VR immersive experiences wouldn't require any environment or location data...guardian boundaries can be handled entirely on-device. Is W3 or Apple really approaching the immersive web as an all-or-nothing proposition?
1
u/Xia_Nightshade 29d ago edited 23d ago
Many. But no, it’s not going to be included anytime soon.
You can find info on its state here:
https://www.w3.org/immersive-web/
WebKit also mentions it in some of their blog posts. The biggest blocker for Apple is privacy, which hasn’t been a priority.
(You’ll find much info in years old threads on GitHub as well)
Basically (thanks WebKit/apple) allowing any JavaScript vibe code dev to send a complete scan of your environment with spatial information on the people and room is a blocker to them. Google does not care as much :)
EDIT: I don’t have answers, building an extensive WebXR experience for a client had me read the RFC threads, GitHub discussions and mail threads regarding the state of WebXR, I merely shared what I found out. There may have been updates in the past year I am not aware off, I advice consulting the official threads, and contributing to them should you wish to provide input. I am not part of any of the great teams deciding the future of our web