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

So I think one other question is:  to what extent are users of this API not going to be doing things similar to https://github.com/w3ctag/design-reviews/issues/300#issuecomment-434684782, but instead using it because they want to predict browser behavior in other spaces, such as permission prompts.  For example, if we end up with sites using this API to predict what browsers are going to do when specific permissions are requested, that will both (a) make things harder for minority browsers that have different models for when to allow sites to request those permissions and (b) make it harder for all browsers to improve their UI around permission requests.  So if those use cases are likely to be important, it may be valuable to address them *first* via improvements to the permissions API that expose more information to sites about when permissions can be requested and why they can't be.

-- 
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-448430352