Re: [w3c/gamepad] Should fire events instead of using passive model (#4)

If you wait until rAF to draw any changes, and you received both axischange events by then, it should correctly handle simultaneous X/Y changes. I think a more interesting question is how to handle that with getCoalescedEvents(). Will the coalesced events for different axes be guaranteed to have the same number of updates at the same time? Perhaps it could combine axes and fire events for them simultaneously to avoid this?

-- 
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/issues/4#issuecomment-355006140