navigator.vibrate doesn't actually work

Bug #1593232 reported by Chris Coulson on 2016-06-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Chris Coulson

Bug Description

This functionality has no tests, so I thought I'd write some, only to discover that the feature doesn't actually work (the empty device::VibrationManager stub in Chromium is always used)

Chris Coulson (chrisccoulson) wrote :

So, this broke with, which moved it to a frame service rather than a process service.

We really need to stop adding features like this with no tests.

Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
status: New → In Progress
importance: Undecided → Critical
milestone: none → branch-1.17
Chris Coulson (chrisccoulson) wrote :
Changed in oxide:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers