Re: [w3ctag/design-reviews] User Activation API (#300)

To make that question a little more concrete:  it feels like a bunch of the use cases for this might be better addressed by enhancements to the permission API to more clearly explain the permission state, e.g., building an API that's expressive enough to say "right now the permission is denied, but following user interaction your page would be able to prompt to ask for this permission"... and then probably also notify the page when that changes.  It seems like that sort of thing is an improvement in that it would mean less baking of knowledge of what browsers do (which may differ between browsers and may change over time) into the JS within applications.

-- 
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/300#issuecomment-461298158