You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature predates the explainer era, but its MDN entry serves as a good starting point.
Other comments:
Due to complexity of revising a Recommendation under the old process, TR for this specification did not receive these latest updates informed by implementation experience, but they were incorporated into the Editor's Draft instead. This caused some unfortunate confusion among readers not closely watching the specification. To clear this confusion, supported by reinvigorated interest and process improvements for revising a Recommendation, this API is now being revived on the Recommendation Track to allow bringing the updates from the ED back to TR and to allow for further improvements using the modern streamlined publication flow.
Thank you for your review!
The text was updated successfully, but these errors were encountered:
Thank you @pes10k and PING folks! We provided initial responses in the issues and are open to discuss your feedback at TPAC subject to your availability.
In the issue title above add the document name followed by the date of this request, then the date of your proposed deadline for comments.
name of spec to be reviewed: Vibration API
URL of spec: https://w3c.github.io/vibration/ (Why ED? See "Other comments")
What and when is your next expected transition? After TPAC 2024
What has changed since any previous review?
Please see the commit history for details and the changes section for an overview of the changes since the latest published version. Diff between the latest published version and the staged snapshot is available at htmldiff.
This feature predates the explainer era, but its MDN entry serves as a good starting point.
Other comments:
Due to complexity of revising a Recommendation under the old process, TR for this specification did not receive these latest updates informed by implementation experience, but they were incorporated into the Editor's Draft instead. This caused some unfortunate confusion among readers not closely watching the specification. To clear this confusion, supported by reinvigorated interest and process improvements for revising a Recommendation, this API is now being revived on the Recommendation Track to allow bringing the updates from the ED back to TR and to allow for further improvements using the modern streamlined publication flow.
Thank you for your review!
The text was updated successfully, but these errors were encountered: