The current implementation uses PaymentDetails structure when creating
PaymentRequest object and calling updateWith(). But some parameters like error
are only allowed in the updateWith(). If developer tries to use error parameter
when creating PaymentRequest, then throws exception. So, to solve the problem
in the latest spec[1][2], common parts are combined and each different parts
are separated into PaymentDetailsInit and PaymentDetailsUpdate.
This change only affects input dictionaries and doesn't break existing behavior.
Therefore, we don't need a intent to implement and ship.
[1] https://w3c.github.io/browser-payment-api/#paymentdetailsinit-dictionary
[2] https://w3c.github.io/browser-payment-api/#paymentdetailsupdate-dictionary
Comment 1 by rouslan@chromium.org
, Mar 22 2017Owner: zkoch@chromium.org
Status: Untriaged (was: Assigned)