Re: [w3ctag/design-reviews] User Activation Delegation through postMessages (#347)

@torgo: Thanks for raising the privacy implications question from data collection perspective.  I have created a detailed [privacy consideration doc](https://github.com/mustaqahmed/user-activation-delegation/blob/master/privacy_considerations.md) to analyze your concerns, and linked it from the explainer as well as from the security/privacy questionnaire.  Please let me know if this addresses your concerns.

---

@dbaron: Added a para in the explainer to further clarify the dependency with UAv2.

---

@plinss: I agree this is a low-level feature but as @annevk commented, all browsers rely on "user activation" for [many APIs](https://docs.google.com/document/d/1mcxB5J_u370juJhSsmK0XQONG2CIE3mvu827O-Knw_Y) already.  Moreover, many specs refer to this notion.  For example, check [fullscreen model](https://fullscreen.spec.whatwg.org/#model), also check how many times the phrase appears in the [HTML spec](https://html.spec.whatwg.org).

We have been discussing the spec problem with "user activation" [here](https://github.com/whatwg/html/issues/1903) for a while; this API here is just a follow-up proposal to Chrome's main proposal there to fix the problem.  Let's continue this discussion on that issue.

-- 
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/347#issuecomment-478074145