The situation is that this API is pretty stable (basically 2 implementations and 3rd on the way), so implementers are reluctant to change stuff without a really strong reason - or in a manner that is now backwards compatible. There is not a strong reason to make the change I originally requested here (apart from architectural purity). Thus, this should be closed. -- 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/299#issuecomment-281113172
Received on Monday, 20 February 2017 15:49:04 UTC