[w3c/browser-payment-api] Ambiguous conformance requirement in constructor (#354)

The following seems to be an authoring requirement: 

> The methodData supplied to the PaymentRequest constructor SHOULD be in the order of preference of the caller.

The following assertion seems to be out of place in the algorithm: 

> Implementations MAY show payment methods in this order if possible but should prioritize the preference of the user when presenting payment methods.

The above should be placed somewhere closer to when they payment request is actually shown. 

-- 
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/browser-payment-api/issues/354