Activation requirements for safety limits #344
Description
Originally posted by @martinthomson in #237
Useful links for managing the user activation part of the Big Bird algorithm:
https://html.spec.whatwg.org/#user-navigation-involvement
https://html.spec.whatwg.org/#tracking-user-activation
Right now, it seems like consuming transient activation is the right answer, which would keep things relatively simple. However, consumption creates the risk that this affects other APIs that depend on activation, so we would need to look at that carefully. (These API calls are not in direct response to a user action, particularly showing impressions.)
In addition to that, we'd need to flag the window/document to say that the API is good to call for this site. So that sites that gain access to the API can keep access for (for example) multiple impressions.