Re: [w3c/pointerlock] Specification status report for TPAC 2019 (#50)

@marcoscaceres Thanks for pinging me on the issue. I guess I missed it before. Here is the update:

> What progress has your spec made in the last 12 months?

Aside from some editorial changes and whatnot, we have started adding a new capability to the request API so that it matches more platform like features such as disabling mouse acceleration. We are still working on it to get more feedback from other vendors and also investigate how different underlying platforms could support the feature.
Aside from this new feature we wanted to clear the coordinate space for some of the attributes as part of this [issue](https://github.com/w3c/pointerlock/issues/42) but . We have 

> Is anything blocking your spec from moving to CR?

Nothing actually. I believe we should be okay if we land the new capability above and also hopefully rewrite parts of the spec to make it more like a procedural/algorithmic spec it should be ready to go for V2.

> What do you want to achieve for your spec in the next two days (of breakout sessions)?

Although the discussions are already happening on the [issue](https://github.com/w3c/pointerlock/issues/36) if anyone has any comment I'd love to hear in person. I do like to hear if other vendors have heard any new requirements that we might need to address in V2. 



-- 
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/pointerlock/issues/50#issuecomment-527497701