Re: [w3c/payment-request] Spec hasEnrolledInstrument (#830)

@danyao, definitely would like to get onto this, but we have a couple of constraints on us at the moment. Rest easy that none of the constraints prevents us from spec'ing this out! - just want to be clear on how we are going to do this:

 1. We can spin up a new branch for "hasEnrolledInstrument", and start adding the spec text into that. That should give you something to point to in your intent to ship, with the promise that it will be part of the Payment Request API version 1.1 (but not 1.0!). As part of that, we should collaborate to get the WP Tests ready - and we need to get implementation commitment from Safari too (they have been supportive, so should be no problem - but we need a bug filed on their side, and a "👍" from @aestes). 

 1. In parallel, we need to finish and merge the last [two PRs](https://github.com/w3c/payment-request/pulls). That will allow us to consider the spec ready for another "CR" round (that CR round will take around 6 weeks).
 
 1. We need to update the implementation report by re-running all the tests in the test suite (including the manual tests). We need to get 100% on two implementations. We are really close - but we are counting on the Chrome team here to help us get over the line. 

 1. Once the current 1.0 spec is at stable point and ready for Proposed Recommendation, we can start merging in the actual "hasEnrolledInstrument" method spec text into the spec. This can happen quite quickly, but we need to be at a stable point where we can do the 1.0 release.  

What would help a lot at this point is having a link to the Blink implementation for `hasEnrolledInstrument`. We can base the spec text around your implementation and keep everything in sync. 

Sound like a plan? Cc'ing @rsolomakhin so he is also aware of the plan. 

-- 
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-request/issues/830#issuecomment-459181940