Re: [battery] Are there new use cases for battery API? (#64)

>I think my point stands, if, as Chrome does, .dischargingTime and .chargingTime both always return Infinity

This is not correct. Chrome (also on macOS) returns the time in seconds for both.

(You need to wait a while for the subsystem to calculate the estimates after you plug in or unplug. If you tested this quickly, you saw Infinity for that reason. This is per the spec.)

>@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?

I provided data that points to places where to look for real-world deployments in https://github.com/w3c/battery/issues/25#issuecomment-2136891965

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/battery/issues/64#issuecomment-2136934439 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 29 May 2024 09:14:46 UTC