Re: [w3c/permissions] Capability Model (#148)

I mean it is not necessarily the the responsibility of a given specification to police developer creativity to such an extent that a single, lowest-common-denominator, homogeneous, UX will prevail regardless of the individual Web App, business requirement, or user demographic.

Note that the capability model (where applicable) is a given as the "best" user experience today, but this was not always the case and conceivably may not be so in the future. It is also highly likely that a certain cultural demographic may actually prefer up-front or install time permission dialog.

My point is that its is over-reach and out of the terms of reference of spec developers to insist that you can have any colour Model-T as long as it is Black. Let user-demand/market-forces dictate what is a preferable or successful UX. No offence to the Mozilla people intended but I hope they'll agree that their current presence on the mobile platform suggest they have not always been right in knowing what people want.

Anyway, the real answer to your question is, I don't understand how a ServiceWorker can use the capability model to prompt for user permission with context when there is no active UI. Does that make more sense?  

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