-
Notifications
You must be signed in to change notification settings - Fork 28
Closed
Labels
concerns: annoyanceThe technology described in this proposal could be used to do things that may annoy the userThe technology described in this proposal could be used to do things that may annoy the userconcerns: device independenceProposal is hardware- or OS-specific, in a way that may risk the device independence of the WebProposal is hardware- or OS-specific, in a way that may risk the device independence of the Webconcerns: integrationCan't be used w/ other web platform features (or unclear what happens if used together)Can't be used w/ other web platform features (or unclear what happens if used together)concerns: portabilityThis proposal may be impossible or difficult to implement on at least one important platformThis proposal may be impossible or difficult to implement on at least one important platformconcerns: powerThis feature may have negative impact on battery lifeThis feature may have negative impact on battery lifeconcerns: use casesThe use case for this proposal are not stated or are unclearThe use case for this proposal are not stated or are unclearposition: opposetopic: device apisSpec relates to device APIs: access to device-specific hardware, sensors, and interfacesSpec relates to device APIs: access to device-specific hardware, sensors, and interfacesvenue: W3C Devices and Sensors WG
Description
WebKittens
No response
Title of the spec
Vibration API (Second Edition)
URL to the spec
https://w3c.github.io/vibration/
URL to the spec's repository
https://github.com/w3c/vibration/
Issue Tracker URL
https://github.com/w3c/vibration/issues
Explainer URL
No response
TAG Design Review URL
No response
Mozilla standards-positions issue URL
mozilla/standards-positions#907
WebKit Bugzilla URL
No response
Radar URL
No response
Description
In their words "The API is specifically designed to address use cases that require simple tactile feedback only. Use cases requiring more fine-grained control are out of scope for this specification. This API is not meant to be used as a generic notification mechanism. Such use cases may be handled using the Notifications API [NOTIFICATIONS] specification. In addition, determining whether vibration is enabled is out of scope for this specification."
otabekshoyimov
Metadata
Metadata
Assignees
Labels
concerns: annoyanceThe technology described in this proposal could be used to do things that may annoy the userThe technology described in this proposal could be used to do things that may annoy the userconcerns: device independenceProposal is hardware- or OS-specific, in a way that may risk the device independence of the WebProposal is hardware- or OS-specific, in a way that may risk the device independence of the Webconcerns: integrationCan't be used w/ other web platform features (or unclear what happens if used together)Can't be used w/ other web platform features (or unclear what happens if used together)concerns: portabilityThis proposal may be impossible or difficult to implement on at least one important platformThis proposal may be impossible or difficult to implement on at least one important platformconcerns: powerThis feature may have negative impact on battery lifeThis feature may have negative impact on battery lifeconcerns: use casesThe use case for this proposal are not stated or are unclearThe use case for this proposal are not stated or are unclearposition: opposetopic: device apisSpec relates to device APIs: access to device-specific hardware, sensors, and interfacesSpec relates to device APIs: access to device-specific hardware, sensors, and interfacesvenue: W3C Devices and Sensors WG