Re: [w3c/permissions] Gauging interest in a Permission Handler API? (#224)

Although there is overlap, I think the Permission API serves a different purpose (specific for "powerful features" and permission policy checks)... "payments" itself being a powerful feature. 

In the future, I guess we could look at something like:

```JS 
await navigator.permissions.query({
  name: "payments",
  data: { 
     handler: 'https://account.rakuten.com/me',
     name: 'order-history',
  }
}
```

But being able to communicating with an arbitrary third-party payment handler over this mechanism feels very unpalatable to me.



-- 
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/224#issuecomment-844725290