- From: Jeff Burdges <notifications@github.com>
- Date: Thu, 31 Mar 2016 06:39:14 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Thursday, 31 March 2016 13:40:08 UTC
There is plenty you can do in the existing model, so I'm not exactly sure if a richer dialog is necessary. I have not paid a close enough attention to the use cases probably. In any case, browser vendors have already abandoned older more permissive extensions frameworks like XUL to standardize on WebExtensions, which specifically disallows this for extensions. It's more complex anytime you poke holes in someone security model. --- 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/browser-payment-api/issues/109#issuecomment-203940947
Received on Thursday, 31 March 2016 13:40:08 UTC