Re: [w3c/gamepad] Added GamepadPose (#25)

The Geometry spec seems fine to me. I'm not sure why Chrome has not implemented it, but perhaps because there are only a few APIs on the platform that use it (and those are using the legacy non-standard `ClientRect` type in Chrome). I'd encourage you to implement them in Chrome as part of Web VR and the Gamepad API!

It's true that there are libraries to work around the awkwardness you are imposing on developers. That isn't how we should design the platform. Similarly, we shouldn't assume that the platform can be as user-unfriendly and cryptic as it wants because people will just wrap it in libraries.

I don't really have an opinion on representing a quaternion with a type named point. That seems like a reasonable concern, but I don't think it justifies switching to a type named array.

It's not possible to avoid the mutability while using typed arrays. There are two possibilities: fully mutable, or fully immutable (the latter using frozen). What DOMPointReadOnly gives you is readonly: i.e., mutable by the creator (the user agent), but immutable from the program. That is what is necessary for this API.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/pull/25#issuecomment-236488166