Re: [w3ctag/design-reviews] User Activation v2 (#295)

Thanks @dbaron, I definitely plan to update the spec and add tests as we go ahead.

Re the middle category: avoiding consumption allows possible chaining with other activation-gated APIs.  E.g. a page may want to go fullscreen only if it can access [current location](https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API), or only if certain [Bluetooth device](https://webbluetoothcg.github.io/web-bluetooth/) is present.  [Here](https://docs.google.com/document/d/1mcxB5J_u370juJhSsmK0XQONG2CIE3mvu827O-Knw_Y/edit#heading=h.wq9moots9aoj
) is a somewhat-out-of-date list of Chrome APIs most of which don't consume at all.  This is _not_ a perfect list but it can suggest other possible ways to chain.

Another related point is that in Chrome we have seen internal "sequencing" that also points to the need for non-consuming calls (e.g. certain pre-navigation tasks are done only with transient activation, but the activation is consumed at a later stage of the navigation).  I can look up some details if you want more info.

(And I don't think web compatibility is a constrain here.)




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/295#issuecomment-434431661