- From: Raphael Kubo da Costa via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Jan 2022 13:45:09 +0000
- To: public-device-apis-log@w3.org
Latest update: starting with Chromium M99 (or maybe M100, depending on what the API owners there say), the browser will show a deprecation warning whenever the Battery Status API (i.e. `navigator.getBattery()` is used in an insecure origin). The plan is to stop exposing the API in insecure origins altogether starting with M103 (whose planned release date is around mid-June 2022). [chromestatus.com entry](https://chromestatus.com/feature/4878376799043584), [blink-dev discussion](https://groups.google.com/a/chromium.org/g/blink-dev/c/w80tJL8uEV8/m/PfrHlvtgAgAJ) From a spec and web-platform-tests perspective, I wonder if it makes sense to update things immediately or somehow make the changes more in sync with Blink, which is the only engine implementing this API at the moment. This would mean landing any changes adding `[SecureContext]` to Web IDL and updating the tests accordingly in a few months rather than now. Opinions? -- GitHub Notification of comment by rakuco Please view or discuss this issue at https://github.com/w3c/battery/issues/15#issuecomment-1021197301 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 January 2022 13:45:11 UTC