> They will likely be used by a lot of payment methods but it's not clear that we should try to standardize them at the top-level yet. Yes, but we're making a decision where we may never be able to standardize them at the top-level due to the way the PaymentRequest constructor is currently designed. I agree that we may not want to standardize the top-level yet, but we're specifically making a decision where we cannot standardize it at the top-level later on. If someone can produce a well designed strategy for standardizing at the top level later on, that would go a long way to alleviating my concerns around digital signatures and this API. -- 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/291#issuecomment-267347571
Received on Thursday, 15 December 2016 14:58:17 UTC