- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Jun 2017 18:33:31 +0000
- To: public-device-apis-log@w3.org
If we want to change the default, then I think there definitely should be a policy opt-in. This is pretty trivial to add these days - @clellend can help. I don't know how easy it is for cases like Maps and YouTube to get container pages to update their `<iframe>` elements, but it's at least something (and consistent with the other "interventions" we've done like blocking vibrate in iframes by default). Also +1 to there being legitimate power-monitoring use cases here. I don't know details but I've heard that major mobile apps have been able to detect power regressions in the wild based ONLY on rough telemetry of how often they see a 2-digit battery meter tick down by 1%. If true, that's pretty powerful for empowering sites to improve their battery overheads. That case could, of course, be addressed with lower fingerprint risk by some sort of relative API instead of an absolute one. -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/battery/issues/10#issuecomment-309101737 using your GitHub account
Received on Friday, 16 June 2017 18:33:39 UTC