danyao commented on this pull request. "Steps for showing the payment handler" looks good. From w3c/payment-request#684, it seems that Chrome may already behave this one, but I'll double check the code again (don't want to block you here). "Steps for applying modifiers" seem incomplete. I assume it's also meant to make last modifier win, for consistency? Shall we also add a WPT for this? > + <li>Break.</li> + </ol> + </li> + <li> + Use <var>restrictions</var>'s <a>supportedNetworks</a> member to constrain the card type inputs of the payment UI. + </li> + </ol> + </section> + <section> + <h2>Steps for applying modifiers</h2> + <p> + The steps for applying modifiers. + </p> + <ol class="algorithm"> + <li> + Let <var>modifiers</var> be This sentence seems incomplete? -- 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-method-basic-card/pull/69#pullrequestreview-214049459
Received on Wednesday, 13 March 2019 16:13:34 UTC