> Logging the issue as a question made it unclear exactly what the issue was. Just to be clear, we started logging issues as questions because there were some folks in the group that (understandably) felt like our proposals were too aggressive by suggesting concrete changes. The question poses a problem and requests that the browser API editors provide their thoughts on how this problem should be addressed by the browser API. The use case cannot be addressed by the HTTP API because it has no way of accessing the in-browser payment apps. This is definitely a browser API issue, and it remains unaddressed. We've been holding off on opening the signed offer/payment request can of worms until the group got its footing a bit more established. Happy to do that now if that's what you're asking us to do @adrianhopebailie --- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/35#issuecomment-226381102
Received on Thursday, 16 June 2016 03:45:10 UTC