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

Overall, +1 to unifying the definitions. The one here is primarily just so we had a term for "features that need permission".

Some history:
* The term was originally used in https://www.w3.org/TR/2014/WD-powerful-features-20141204/#powerful-feature and was taken out in https://github.com/w3c/webappsec-secure-contexts/commit/e42072e001b84fe972d4c1742d59721aca8f2cde.
* I added it to this spec in https://github.com/w3c/permissions/pull/97, where I defined it as "A feature of a UA that some code might not be allowed to access, for example because its _environment settings object_ doesn't satisfy some criteria, or because the user hasn't given permission." That cites https://www.w3.org/2016/06/08-webappsec-minutes.html, but I couldn't find the discussions on what term to use.
* The narrowing to only cover features that require permission happened in https://github.com/w3c/permissions/commit/f439e8513666c5b7d031f029e0481b80e5163c34 with no linked review or discussion. @marcoscaceres, am I missing a place where people got to weigh in on whether the narrower definition was an improvement?

I think there's a useful distinction between the sort of features that Permissions and Design Principles are talking about, and features like `SharedArrayBuffer` which aren't supposed to expose the user's information but that do require care in their design to make sure that goal is achieved. I've always felt that "powerful" isn't quite the right word, but it's always been the best we could come up with.



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

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