User activation is the mechanism to maintain active-user-interaction state that limits use of "abusable" APIs (e.g. opening popups or vibrating). The web exposed behavior varies widely among major browsers. To unify the web, this feature defines a new user activation model that is simple enough for cross-browser implementation. The main changes introduced by this model are: (a) there is no concept of token passing, and (b) activation visibility changes from stack-scoped to frame-scoped.
Demos
Documentation
Specification
Status in Chromium
Enabled by default (tracking bug) in:
- Chrome for desktop release 72
- Chrome for Android release 72
- Chrome for iOS release 72
Consensus & Standardization
After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.
- No signal
- No signal
- No signal
- Positive
Owner
Last updated on 2020-11-09
Comments
Another popular (but misleading) term that often denotes user activation is "user gesture". For example a swipe or flick gesture by the user does not activate a page, and hence is not from a script standpoint a user gesture.