Re: [w3c/uievents] Gamepad-specific DOM keys / location? (#79)

As I mentioned on the code review, I don't think we should be adding any default useragent behavior that cannot be detected and preventDefault()ed by web authors.  The problem is that there's no sane way to preventDefault browser behaviors with the poll-based gamepad API -- it really needs an event-based model.  (I guess this is also a problem with the gamepad scrolling behavior we've already allowed into Chrome, which we might want to revisit.)

The most natural solution would be to simply forward the artificial gamepad keyboard events which Android framework is already supplying to Chromium.  In general I think it's a reasonable philosophy to forward to JS without information loss all input events that are provided to us by the OS, even if this reveals certain platform differences.  (As long as we're only *revealing* them rather than introducing them.)  That's usually preferable to dropping useful information on the floor even if that would create an artificial cross-platform consistency.

---
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/uievents/issues/79#issuecomment-218651881