- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Jun 2017 18:14:40 +0000
- To: public-device-apis-log@w3.org
> @RByers, did I read you right that you'd be supportive of limiting this API to the top-level browsing context assuming we'd add an appropriate policy directive for battery? Top-level-only by default with an opt-in to enable frames to be granted access (just like vibrate) - yes that seems like a reasonable design to me. But we'd have to examine the [web compat implications](https://docs.google.com/document/u/2/d/1RC-pBBvsazYfCNNUSkPqAVpSpNJ96U8trhNkfV0v9fk/edit?usp=drive_web) to determine if we could make such a breaking change in Chrome (according to our [removal process](https://www.chromium.org/blink/removing-features)). -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/battery/issues/10#issuecomment-309522125 using your GitHub account
Received on Monday, 19 June 2017 18:14:47 UTC