Can we use Web Driver instead of this?

[marcoscaceres]

I wonder if there is a way of removing a lot of the Chrome (and webkit) specific code in the utils by making this use Web Driver BiDi instead?

It seems weird to hook into testing internals... it feels like Web Driver would solve for this.

[alcooper91]

Hey Marcos,

The intention of this spec is to serve as an API for a test interface in WPTs to mock out a fake device so that we can control that to validate expected behavior on a page. (E.g. "If the world looks like this, what values do we get back from a hit test"). I don't think anything precludes you all from using WebDriver yourselves, and in fact this seems like more of an issue on the webxr-utils.js file that's checked in with the WPTs? If that's the case, I'm not sure where is the best place to file an issue like that, but I think it's beyond the scope of what this repo is intended to be.

[alcooper91]

That being said, if you feel there's some simpler way to do this than we currently have implemented (which I thought also ran in WebKit?) I'd definitely be interested in trying to simplify things; but I don't have much bandwidth to make a large Chrome-side change like that at the moment.