Re: [w3ctag/design-reviews] Fenced frames with local unpartitioned data access (Issue #975)

> 
> This still puts a lot of responsibility on whatever consent screen appears behind that popup: if users have concluded that the surrounding page already knows their cross-site identity, the consent screen has to counteract that in order to [get an accuration notion of the user's intent](https://w3ctag.github.io/privacy-principles/#principle-consent-user-preference). Is that plausible?

the click could lead to many possible user experiences, depending on the consumer API in the embedding context, e.g. request storage access, FedCM, PaymentHandler or simply creating a pop-up, etc. so it seems a bit out of scope of this review, as there can be many possible UX's based on the click.
At the same time, showing a personalized button gives the user more context about what they can expect will happen when they click on the button, allowing them to make a more informed choice, closer to their preferences, as per https://w3ctag.github.io/privacy-principles/#consent-principles.



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

Message ID: <w3ctag/design-reviews/issues/975/2523688586@github.com>