Chrome 63 Unleashes Generic Sensors API: Web Developers' Guide & Origin Trial
Stay updated with the latest advancements from the Device and Sensors Working Group! This bi-weekly report covers everything you need to know about the new Generic Sensors API in Chrome 63, including how to experiment with it and provide feedback. We’ll also dive into key discussions around Web Bluetooth, privacy reviews, and the rechartering process.
Latest GitHub Activity: Minimal Changes, Maximum Stability
- Focus has shifted: With the v1 specifications finalized and recently shipping, activity has been light over the past two weeks.
- Stay informed: Check out the latest digests for a summary of the work:
Activate Generic Sensors in Chrome 63: Origin Trial Now Available!
Chrome 63 now includes the v1 Generic Sensors API. Now is the time to experiment with its capabilities. Here’s how to get started:
Enabling Sensors via Flags
- Motion Sensors: Enable the motion sensors flag at:
chrome://flags/#enable-generic-sensor - Environmental Sensors: Enable the environmental sensors flag at:
chrome://flags/#enable-generic-sensor-extra-classes
Origin Trial: Enable Sensors for All Users
Want to enable motion sensors for all Chrome 63+ users visiting your site, without requiring them to change their browser flags? Enroll in the Origin Trial.
- Get Your Free Token: Sign up at http://bit.ly/OriginTrialSignup.
- Developer Documentation: Learn how to bind the token to your origin: https://developers.google.com/web/updates/2017/09/sensors-for-the-web
TPAC Device APIs Breakout: Web Bluetooth in the Spotlight
The Device APIs breakout session at TPAC sparked important discussions. Here's a quick recap:
- Agenda: https://www.w3.org/wiki/TPAC/2017/SessionIdeas#Device_APIs_session
- Minutes: https://www.w3.org/2017/11/08-device-api-minutes.html
- Web Bluetooth: The primary focus was whether Web Bluetooth should advance to the standards track under this WG.
- Current Stance: The prevailing sentiment was to keep the API within its Community Group for now.
- Provide Your Feedback: Share your thoughts on this topic in the relevant issue: https://github.com/w3c/dap-charter/issues/28
Generic Sensors Wide Review: Privacy and Internationalization
Ensuring privacy and broad applicability are key. Here’s an update on the ongoing reviews:
Privacy Review Complete
- Privacy Interest Group (PING): Alex and Anssi attended PING calls and meetings to address privacy concerns.
- Positive Feedback: PING is generally satisfied with the specifications.
- Editorial Suggestions: Expect minor editorial suggestions to formally acknowledge the completed review.
- PING Minutes: https://www.w3.org/2017/11/09-privacy-minutes.html#item05
- Wide Review Tracker: https://github.com/w3c/sensors/issues/299
Internationalization (i18n) Review
- No i18n Implications: The group determined that these specifications do not raise internationalization concerns.
- No Explicit Review Needed: Consequently, the group is not seeking a formal i18n review.
- More Information: https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0033.html
Device and Sensors WG Rechartering: Shape the Future!
The Device and Sensors WG is preparing for rechartering. Your input is crucial!
- Charter Submission: Expect the charter to be submitted for AC review around mid-December.
- Review the Draft: Provide your comments and address any concerns.
- Draft Charter: https://w3c.github.io/dap-charter/DeviceAPICharter.html
- Open Issues: https://github.com/w3c/dap-charter/issues
HTML Media Capture: Approaching Recommendation Status
Good news for media capture on the web!
- CfC Passed: The call for consensus (CfC) has passed.
- Proposed Recommendation: The Proposed Recommendation of HTML Media Capture will be published as early as November 16th.
- CfC Details: https://lists.w3.org/Archives/Public/public-device-apis/2017Oct/0028.html
- Staged PR Snapshot: https://rawgit.com/w3c/html-media-capture/pr/index.html
