- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Mar 2018 13:46:54 +0000
- To: public-device-apis-log@w3.org
FWIW, my hunch is that the [severity of breakage](https://docs.google.com/document/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit#heading=h.u5ya6jvru7dl) is likely to be very small. If there's a compelling reason to lock this down, then (as long as we have the FP opt-in) I suspect we could get away with it. All that said, I have heard of people using coarse grained battery status data to do A/B tests for power-saving optimizations. If that's what a lot of this usage is actually doing in practice (eg. some ad network script), then it seems like a pretty beneficial use case and argument for NOT locking this down (at least until there's a good WebPerf API around power usage). -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/battery/pull/13#issuecomment-373380878 using your GitHub account
Received on Thursday, 15 March 2018 13:46:55 UTC