Intent to Implement - Gamepad Touchpad

[steve....@sony.com]

Contact emails

steve....@sony.com aixi...@sony.com kelvi...@sony.com

Spec

https://github.com/knyg/gamepad/

Summary

The Gamepad specification includes a description of the buttons and axes expected to be present on a standard gamepad. The Gamepad specification will be extended to describe the touchpads available on some gamepads and to add a new API that supports basic touch inputs.

Motivation

Support for gamepads with touchpads enables game developers to create game experiences that are not currently possible with the existing API.  A limited level of support could be provided via extending gamepad buttons and axes, but this solution would create more of a burden on the application side.  Additionally, without a specification, browser implementations can diverge creating inconsistency which creates an even greater burden for the application. Providing a specific touchpad API will ease application implementation while providing greater functionality.

Risks

As this is a new feature, the main risk is lack of adoption. However, this risk is mitigated because touch based gestures are typically a progressive enhancement of the user experience.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes.

Link to entry on the feature dashboard

https://www.chromestatus.com/feature/4782975812108288

Requesting approval to ship?

No

[Mounir Lamouri]

I can't find an explainer or a draft of the API changes. Do you have something for us all to look at?

-- Mounir

> --
> You received this message because you are subscribed to the Google
> Groups "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to blink-dev+...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b1475bd1-537f-4db1-856d-e3b233237649%40chromium.org.

[Ian Kilpatrick]

Hi,

Can you make sure that you follow the intent to implement process specified here?

https://docs.google.com/document/d/1vlTlsQKThwaX0-lj_iZbVTzyqY7LioqERU8DK3u3XjI/edit#bookmark=kix.p5nalpch13qw

Specifically filing a TAG review, and having an explainer of the changes - before landing any code would be good.

Thanks,

Ian

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1526462934.667051.1373908104.1CA676E3%40webmail.messagingengine.com.

[PhistucK]

Congratulations on your first intent (woo hoo, Sony!)!

Plus, either re-send this with a colon (Intent to ship:) instead of space-and-dash (Intent to ship -) in the subject, otherwise the automated intent tracking scripts will not see this intent, or make sure that someone adds this intent to the intent list.

Thank you!

☆PhistucK

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJL3UpQFq_Kk59MHqhU%3D%2Bwitb8DuoeG2n2MKfZV%3DqkLOH2Ycjw%40mail.gmail.com.

[Yoav Weiss]

Added it to the table

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABc02_%2BGwQc75P9y9x6ZchXkotA9jc8Y9Ev7SxVWZHgcpe6zDw%40mail.gmail.com.

[steve....@sony.com]

Thanks!

Will resend with the correct subject line using a colon and link to an explainer.

[Daniel Vogelheim]

This sounds like it would increase the finger-printing surface quite a bit. Could you please add a 'privacy & security' section to one of the docs?

For Chromium, I think most hardware access (camera, microphone, USB, Bluetooth, etc.) already requires a per-site permission drop-down ("This page is accessing..."). If gamepads are already covered by one of those, this would be a good solution for the finger-printing issue.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.