Removed conflicts from Jake Archibald pull request#327
Conversation
|
Hi @rsolomakhin and @jakearchibald, I endeavored to resolve the merge conflicts between Jake's pull request: and the current draft of the spec. @rsolomakhin, I removed the bits you suggested be removed. I did not (yet) review the full algorithm to see whether it still makes sense in light of the edits. Ian |
rsolomakhin
left a comment
There was a problem hiding this comment.
Looks good, but need to preserve the fields in PaymentRequestEvent.
| <dd> | ||
| The result of executing the <a>MethodData Population | ||
| Algorithm</a> | ||
| </dd> |
There was a problem hiding this comment.
Let's keep total, paymentRequestId, instrumentKey, and modifiers in the PaymentRequestEvent for now.
| </dd> | |
| </dd> | |
| <dt> | |
| <a data-lt="PaymentRequestEvent.total">total</a> | |
| </dt> | |
| <dd> | |
| A <a>structured clone</a> of the total field on | |
| the <a>PaymentDetailsInit</a> from the corresponding | |
| <a>PaymentRequest</a>. | |
| </dd> | |
| <dt> | |
| <a data-lt="PaymentRequestEvent.paymentRequestId">paymentRequestId</a> | |
| </dt> | |
| <dd> | |
| The [[\details]].<a>id</a> from the <a>PaymentRequest</a>. | |
| </dd> | |
| <dt> | |
| <a data-lt="PaymentRequestEvent.instrumentKey">instrumentKey</a> | |
| </dt> | |
| <dd> | |
| The <a>instrumentKey</a> of the selected <a>PaymentInstrument</a>, | |
| or the empty string if none was selected. | |
| </dd> | |
| <dt> | |
| <a data-lt="PaymentRequestEvent.modifiers">modifiers</a> | |
| </dt> | |
| <dd> | |
| The result of executing the <a>Modifiers Population Algorithm</a>. | |
| </dd> |
| <dd> | ||
| The result of executing the <a>Modifiers Population | ||
| Algorithm</a>. | ||
| </dd> |
There was a problem hiding this comment.
Could you move these fields from canmakepayment event to paymentrequest event, please?
- total
- paymentRequestId
- instrumentKey
rsolomakhin
left a comment
There was a problem hiding this comment.
Almost missed this :-)
The field names in canmakepayment event should be associated with CanMakePaymentEvent, not the PaymentRequestEvent.
| </p> | ||
| <dl> | ||
| <dt> | ||
| <a data-lt="PaymentRequestEvent.topOrigin">topOrigin</a> |
There was a problem hiding this comment.
| <a data-lt="PaymentRequestEvent.topOrigin">topOrigin</a> | |
| <a data-lt="CanMakePaymentEvent.topOrigin">topOrigin</a> |
| </dd> | ||
| <dt> | ||
| <a data-lt= | ||
| "PaymentRequestEvent.paymentRequestOrigin">paymentRequestOrigin</a> |
There was a problem hiding this comment.
| "PaymentRequestEvent.paymentRequestOrigin">paymentRequestOrigin</a> | |
| "CanMakePaymentEvent.paymentRequestOrigin">paymentRequestOrigin</a> |
| PaymentRequest was initialized. | ||
| </dd> | ||
| <dt> | ||
| <a data-lt="PaymentRequestEvent.methodData">methodData</a> |
There was a problem hiding this comment.
| <a data-lt="PaymentRequestEvent.methodData">methodData</a> | |
| <a data-lt="CanMakePaymentEvent.methodData">methodData</a> |
| selected. | ||
| </dd> | ||
| <dt> | ||
| <a data-lt="PaymentRequestEvent.modifiers">modifiers</a> |
There was a problem hiding this comment.
| <a data-lt="PaymentRequestEvent.modifiers">modifiers</a> | |
| <a data-lt="CanMakePaymentEvent.modifiers">modifiers</a> |
#305
The following tasks have been completed:
Implementation commitment:
Preview | Diff