Battery status/geolocation/device check-in not available in service workers

[Fratopolis]

We use these to track our school district Chromebooks and the health of the Chromebooks battery. As well, we use a trigger located in the background page for interval check-ins to our fleet Management. On version 3 these are not available. And the check-in interval is reset when all browser tabs are closed on a Chromebook and reopened. The check-in also completely stops if tabs are not re-opened

[Rob--W]

For clarity, this issue is asking about

• The Battery Status API - https://developer.mozilla.org/en-US/docs/Web/API/Battery_Status_API
  • Not available to workers.
  • This has been removed from Firefox a few years ago, but there is a feature request for an extension-specific one at https://bugzilla.mozilla.org/show_bug.cgi?id=1314076
• The geolocation API - https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API
  • Not available to workers.

What's the "device check-in" part of the report about?

This issue can probably be merged with #72

[Fratopolis]

The check in let's us know when our Chromebooks are online and who is using the Chromebook. This helps us ensure the student or staff member using the Chromebook is the one it is checked out to.

[Fratopolis]

I thought this was for Google chrome not Firefox. Am I posting in the wrong area?

[Fratopolis]

I just realized what you meant by that question. It's a timer that kicks off. In this instance every fifteen minutes. When all tabs are closed on the Chromebook the timer ends. And restarts all over when a new tab is then opened initiating a logon event and resetting the fifteen minute timer.

[Rob--W]

From your description, it looks like you could be using the alarms API as a replacement for your timer (setTimeout?), combined with whatever triggers you are using to set/reset the timer.

I thought this was for Google chrome not Firefox. Am I posting in the wrong area?

This repository & issue tracker tracks issues related to cross-browser extension APIs.

You've mentioned some Chrome bugs, and for completeness I added the perspective of Firefox to the report.

If you'd like to report a browser-specific issue, use crbug.com (see the pinned issue for more information).

[carlosjeurissen]

@Fratopolis To report a browser-specific issue please see:
#155

[owengo]

We are also a company with a fleet of chromebooks, we have a custom extension force-installed which allows us to monitor the state of the devices and with MV3 we can't get access to battery information.