Oxide

navigator.vibrate() not supported

Bug #1440863 reported by Alexandre Abreu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
Medium
Alexandre Abreu
Oxide branch-1.14
webapps-sprint
Fix Released
Medium
Alexandre Abreu
webapps-sprint sprint-18

Bug Description

navigator.vibrate() is not currently supported and is not bound to qtfeedback

See original description

Related branches

lp:~abreu-alexandre/oxide/vibrate
Chris Coulson: Approve
Diff: 305 lines (+169/-0)
10 files modified
qt/build/system.gyp (+17/-0)
qt/core/browser/oxide_qt_browser_platform_integration.cc (+6/-0)
qt/core/browser/oxide_qt_browser_platform_integration.h (+2/-0)
qt/core/browser/oxide_qt_vibration_manager.cc (+57/-0)
qt/core/browser/oxide_qt_vibration_manager.h (+56/-0)
qt/core/core.gyp (+3/-0)
shared/browser/oxide_browser_platform_integration.cc (+4/-0)
shared/browser/oxide_browser_platform_integration.h (+5/-0)
shared/browser/oxide_content_browser_client.cc (+18/-0)
shared/browser/oxide_content_browser_client.h (+1/-0)
lp:~oxide-developers/oxide/packaging.xenial.trunk
lp:~oxide-developers/oxide/packaging.wily.trunk
lp:~oxide-developers/oxide/packaging.trusty.trunk
lp:~oxide-developers/oxide/packaging.vivid.overlay.trunk
lp:~oxide-developers/oxide/packaging.xenial.next
lp:~oxide-developers/oxide/packaging.wily.next
lp:~oxide-developers/oxide/packaging.trusty.next
lp:~oxide-developers/oxide/packaging.vivid.overlay.next
lp:~oxide-developers/oxide/packaging.yakkety
Alexandre Abreu (abreu-alexandre)
Changed in oxide:
milestone: none → branch-1.8
assignee: nobody → Alexandre Abreu (abreu-alexandre)
importance: Undecided → Medium
status: New → Confirmed
Alexandre Abreu (abreu-alexandre)
description: updated
summary: - navigator.notification.vibrate not supported
+ navigator.vibrate() not supported
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

How familiar are you with mojo, and have you seen ContentBrowserClient::OverrideRenderProcessHostMojoServices? It looks like it would be possible to use this to override the default devices::VibrartionProvider with our own implementation.

Revision history for this message
Alexandre Abreu (abreu-alexandre) wrote :

Yes I quickly had a look when I filed the bug to see how feasible it was, found the targeted area, I wasn't familiar w/ mojo but now I am, I saw that you can indeed quickly replace the current impl apparently w/ our own in devices/

Alexandre Abreu (abreu-alexandre)
Changed in oxide:
milestone: branch-1.8 → branch-1.9
Alexandre Abreu (abreu-alexandre)
Changed in oxide:
status: Confirmed → In Progress
Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: branch-1.9 → branch-1.11
Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: branch-1.11 → branch-1.12
Alexandre Abreu (abreu-alexandre)
Changed in webapps-sprint:
milestone: none → sprint-17
assignee: nobody → Alexandre Abreu (abreu-alexandre)
importance: Undecided → Medium
status: New → In Progress
Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: branch-1.12 → branch-1.13
Alexandre Abreu (abreu-alexandre)
Changed in webapps-sprint:
milestone: sprint-17 → sprint-18
Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: branch-1.13 → branch-1.14
status: In Progress → Fix Released
Alexandre Abreu (abreu-alexandre)
Changed in webapps-sprint:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.