- From: Nick Shearer <notifications@github.com>
- Date: Sat, 30 Apr 2016 18:00:27 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
Received on Sunday, 1 May 2016 01:01:22 UTC
> Without strong typing of what the items mean, any implementor is left to just figure it out and that is certain to fail. Wouldn't it be really confusing if your tax item was rendered first, then an actual good, then a discount, then another good? Isn't displayItems an ordered list? Is the concern here user agents won't respect the ordering? --- 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/163#issuecomment-216005929
Received on Sunday, 1 May 2016 01:01:22 UTC