The Mojo interfaces in vr_service.mojom and related classes like VRDeviceBase and VRDevice resemble WebVR and/or are otherwise showing their age. We should refactor them to make them reflect WebXR, which itself includes API improvements, and be easier to understand.
may want to only have one "session" type, merging VRMagicWindowProvider and VRPresentationProvider because RequestHitTest makes sense for both types of sessions.
I'm going to resolve this as fixed. The current mojo shape mirrors webxr better and we aren't blocked from implementing any of the currently spec'd behavior with the current mojo interface.
That said, there is still more cleanup to do, but I'd rather have small targeted bugs for specific issues so we don't approach it as "lets redesign everything". Moreover, given the still ongoing spec changes in webxr, I'd like the service to be somewhat more general than the current spec so we don't need mojo changes when the spec changes - in particular we shouldn't necessarily need to use the same names for mojo and webxr.
Comment 1 Deleted