- From: Rouslan Solomakhin <notifications@github.com>
- Date: Thu, 02 May 2019 11:11:45 -0700
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 2 May 2019 18:12:07 UTC
Yes, Ian, specializations of PaymentItem would give merchants the power to explicitly opt-in to passing some display items to the payment apps, if they so desire. Our specs and docs would need to be very explicit that specialized PaymenItems go to the payment app. --Rouslan On Thu, May 2, 2019 at 2:07 PM ianbjacobs <notifications@github.com> wrote: > Hi @rsolomakhin <https://github.com/rsolomakhin>, > > Do you think it would help achieve this goal if we were to give merchants > specializations of PaymentItem [1]. Maybe this has already been suggested; > I don't recall. What if we offered specializations for sub-total, tax, and > shipping. This would allow the browser to pass through those > specializations, but not instance of the parent class. > > Ian > > [1] https://w3c.github.io/payment-request/#dom-paymentitem > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/payment-handler/issues/91#issuecomment-488773834>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAH3EGO5ZJFGNBE2XOXSCZTPTMUV5ANCNFSM4C4ZY6GQ> > . > -- 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/payment-handler/issues/91#issuecomment-488775232
Received on Thursday, 2 May 2019 18:12:07 UTC