- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 May 2024 17:39:41 +0000
- To: public-device-apis-log@w3.org
@anssiko, for an API that is available in at least one engine (and since that engine is Blink, multiple browsers) I'd like us to move past prospective use cases and look at real-world deployments. Can you point at any sites that are making user-visible decisions based on the Battery Status API? The Akamai use case (described in [their paper](https://arxiv.org/pdf/2003.06477)) doesn't really count as user-visible. The other examples from [the Chromium issue](https://issues.chromium.org/issues/40491831) are limited to kiosk-mode applications and browser extensions which could be given access to this information without providing it to every web site. A number of positive user benefits have been proposed but it's unclear that any site has actually implemented them. I would like to see that evidence before advocating one way or the other for continuing work on this specification. -- GitHub Notification of comment by reillyeon Please view or discuss this issue at https://github.com/w3c/battery/issues/64#issuecomment-2135789035 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 May 2024 17:39:42 UTC