Privacy/Reviews/OSIdleAPI: Difference between revisions

Jump to navigation Jump to search
Line 121: Line 121:
* Prevent the web page from knowing the real timing of when the user goes idle. A fuzz factor/time has been added to the 'idle' and 'active' notifications to mitigate this risk.
* Prevent the web page from knowing the real timing of when the user goes idle. A fuzz factor/time has been added to the 'idle' and 'active' notifications to mitigate this risk.
* When the user stops using the device, i.e. becomes 'idle' the web page is notified after the requested idle time registered with the Idle API, has elapsed plus a random fuzz time.  
* When the user stops using the device, i.e. becomes 'idle' the web page is notified after the requested idle time registered with the Idle API, has elapsed plus a random fuzz time.  
* When the user starts using the device again, i.e. becomes 'active' or comes 'back' the web page is notified after a fuzz amount of time.
* When the user starts using the device again, i.e. becomes 'active' the web page is notified after a fuzz amount of time.
* The user 'idle' and 'back' status is platform specific.
* The user 'idle' and 'active' status is platform specific.
** On platforms that do NOT support obtaining system idle time, if the user stops using the web browser but continues to use another application currently executing on the device then the web page is specifically notified that the user is idle despite the fact that the user is using another application. E.g. Linux, Android.  
** On platforms that do NOT support obtaining system idle time, if the user stops using the web browser but continues to use another application currently executing on the device then the web page is specifically notified that the user is idle despite the fact that the user is using another application. E.g. Linux, Android.  
** The web page is notified that the user is 'active'/'back' only when the user specifically interacts with the web page.
** The web page is notified immediately that the user is 'active' only when the user specifically interacts with the web page.
** On platforms that do support obtaining system idle time such as Windows, the web page is notified of user idle status only when the user is completely away from the device.  
** On platforms that do support obtaining system idle time such as Windows, the web page is notified of user idle status only when the user is completely away from the device.  
** The web page is notified that the user is 'active'/ 'back' as soon as the user interacts with any application executing on the device. The user does not need to be directly interfacing with the web page.
** The web page is notified that the user is 'active' with a fuzz time added when the user interacts with any application executing on the device. The user is not directly interacting with the web page.




76

edits

Navigation menu