- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Sep 2022 08:12:57 +0000
- To: public-device-apis-log@w3.org
@m32b64 thank you for providing the GH label timeline. Here's an update on the recent developments: The WG discussed the Battery Status API and the privacy-enhancing high-level API proposal at its [15 September 2022 meeting](https://www.w3.org/2022/09/15-dap-minutes.html#t15). The WG [made a resolution](https://www.w3.org/2022/09/15-dap-minutes.html#r04) to "Understand the use cases behind current usage of the API, and if compelling, seek positions from other implementers for interest for the high-level Battery proposal." The WG specified [SecureContext] restriction https://github.com/w3c/battery/pull/51 and landed this into the implementation earlier this year. Due to the substantial usage of the current API (~10% of page loads in Chrome), the WG believes normative changes to the current API benefit from a data-driven assessment and need a deprecation plan for implementers. Interested folks are welcome to contribute use cases (#52) and propose enhancements to the privacy and security considerations sections. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/battery/issues/28#issuecomment-1257660961 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 September 2022 08:12:58 UTC