Open Bug 1824217 Opened 3 years ago Updated 2 years ago

Consider implementing the vibrationActuator API

Categories

(Core :: DOM: Device Interfaces, defect, P3)

defect

Tracking

()

People

(Reporter: twisniewski, Unassigned)

References

Details

(Keywords: parity-chrome, parity-safari)

The Safari 16.4 beta release notes confirm they intend to ship this API, meaning Blink and WebKit will now both support it. The spec is at https://github.com/w3c/gamepad/pull/68 according to the Chrome Platform Status page.

The severity field is not set for this bug.
:cmartin, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cmartin)

Setting this to low priority for now. This is one of those things that I agree would be nice-to-have; however, our current level of investment in Gamepad-related work is very low. It's unlikely that someone will work on this in the foreseeable future.

Severity: -- → S3
Flags: needinfo?(cmartin)
Priority: -- → P3

Hi, this is just a heads up to let you know that the vibrationActuator is being added to the main Gamepad API spec in https://github.com/w3c/gamepad/pull/190.

Duplicate of this bug: 1874639
You need to log in before you can comment on or make changes to this bug.