Re: [w3c/browser-payment-api] Why is details.total.amount.value not a number? (#301)

I imagine to give flexibility to future currencies where there are VERY LONG floating point values so that we do not need to deal with precision when, in fact, nothing in the tool chain actually cares what the value is.  It is only really there for display purposes and to pass along to the next actor in the chain.

-- 
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/301#issuecomment-260326131