-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gamepad Trigger Rumble Extension #934
Comments
Hi @gabrielsanbrito thanks for this - can you clarify where this stands in the working group process at this point? Is this due to be merged with the gamepad spec and is there is consensus in the group to do so? Is this in "horizontal review"? /cc @marcoscaceres |
Hi @torgo, thanks for having a look! Yes, there is consensus in the group to include this in the specification (the proposed changes can be found at w3c/gamepad#195). We would still like TAG to have a "horizontal" look on our proposal. However, any type of comment is welcome. |
Hi @gabrielsanbrito thanks for this response. On this basis we are happy to close and to see the work go forward. |
Hi, @torgo Thank you very much for looking into this! |
こんにちは TAG-さん!
I'm requesting a TAG review of Gamepad Trigger Rumble.
Currently, there are gamepads, like the Microsoft's Xbox and the Razer Wolverine Ultimate Controllers, which comes equipped with "impulse triggers" capable of providing trigger-rumble feedback to the user. While the GamepadHapticActuator, part of the Gamepad API, already provides support for dual-rumble effect, it does not allow developers to have access to trigger-rumble yet. This extension will allow game developers to equip their web applications with a wider set of haptics feedback options, making it possible for their users to have a richer and more engaging experience on the web.
Further details:
You should also know that...
Both Chromium and WebKit already have this extension implemented and working behind a feature flag. Moreover, this is an extension to what the Gamepad API spec maintainers now view as a legacy API and we expect future haptic effects will use a new API.
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify @gabrielsanbrito, @SteveBeckerMSFT
Thanks!
The text was updated successfully, but these errors were encountered: