Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Extensions] GamepadHapticActuator#pulse bugs #50

Closed
Teflo opened this issue Dec 7, 2016 · 2 comments
Closed

[Extensions] GamepadHapticActuator#pulse bugs #50

Teflo opened this issue Dec 7, 2016 · 2 comments

Comments

@Teflo
Copy link

Teflo commented Dec 7, 2016 •
edited

Hello!

I was playing around with the Gamepad extensions in Chromium and stumbled upon these issues:

  • HapticActuator.pulse() does not work with my Logitech Gamepad F310. Is there a list of supported controllers for this? It works with my wireless Xbox360 Gamepad though.

  • HapticActuator.pulse() ignores the second parameter (duration) and my gamepad vibrates forever, until I plug it out, or call pulse() with a value of 0.

I hope these bugs can be reproduced by others and be solved soon!
@cynthia
Copy link
Member

cynthia commented Dec 27, 2016

This seems like a implementation bug rather than a spec bug. You might have better luck at https://bugs.chromium.org/ .

(Leaving this open as I'm not a spec owner)

@luser
Copy link
Contributor

luser commented Jan 3, 2017

Yeah, please file bugs on specific implementations with the browser in question. Thanks!

@luser luser closed this as completed Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cynthia @luser @Teflo