- From: Andrey Logvinov via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Oct 2017 16:07:15 +0000
- To: public-device-apis-log@w3.org
I think the wake lock approach is does not address the privacy and security reasons why sensor data is available only to visible tabs in the first place. It is just forcing the tab to remain technically visible. Also I am not sure if a screen wake lock can be implemented without also keeping the CPU awake which would be wasteful as modern devices are capable of collecting sensor data using a low-power co-processor while the CPU is powered down and only occasionally waking up the CPU to process a new batch. Perhaps a distinction should be made between cases when a tab is invisible due to the screen being turned off and cases when a tab is invisible because it is not the foreground tab or the browser is not the foreground app. Also per definition https://w3c.github.io/page-visibility/#dfn-steps-to-determine-the-visibility-state merely turning the screen off does not render a document invisible, not sure how implementations handle this case in reality. -- GitHub Notification of comment by andrey-logvinov Please view or discuss this issue at https://github.com/w3c/sensors/issues/323#issuecomment-338710225 using your GitHub account
Received on Monday, 23 October 2017 16:07:20 UTC