[w3c/permissions] Definition of Powerful Features (Issue #451)

Hi folks - this is in reference to our [design principles issue](https://github.com/w3ctag/design-principles/issues/481) which is about harmonizing what we say in design principles with what you're saying here - to avoid confusion and make sure we're in sync. In [§3.3 of your doc](https://www.w3.org/TR/permissions/#powerful-features) you state:

>  A powerful feature is a web platform feature (usually an API) for which a user gives [express permission](https://www.w3.org/TR/permissions/#dfn-express-permission) before the feature can be used."  

We say in [§2.2 of design principles](https://www.w3.org/TR/design-principles/#require-user-activation) 

> Some powerful APIs can produce intrusive UI (eg. auto-playing audio), expose user data (eg. interacting with the clipboard), perform a background activity without an obvious indicator to the user (eg. accessing local storage), or prompt the user to interact with [trusted UI](https://www.w3.org/TR/design-principles/#trusted-ui) (eg. permission prompts, device hardware features). These APIs should be designed to require some indication of user intention (such as user activation) in order to function. This indicates that the user is intentionally interacting with the web page in question.

Do y'all agree that this is a good definition of *powerful features*?  Could we coalesce on one definition which we could both reference? Also we are saying "user activation" and you're saying "express permission". Maybe this indicates there are two different levels of powerful features we're talking about? Or should **design principles** strengthen our recommendation to also recommend express permission?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/permissions/issues/451
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/permissions/issues/451@github.com>