Re: [w3c/browser-payment-api] Behavior for multiple modifiers for the same payment method is not defined (#309)

I can't find too many precedents, but I think first match wins is reasonable.

Most precedents I can find (e.g. referrer policy headers, CSS) are about "last supported value" semantics. See e.g. https://w3c.github.io/webappsec-referrer-policy/#unknown-policy-values. But that doesn't apply here; the problem is differently structured.

-- 
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/309#issuecomment-290320938

Received on Thursday, 30 March 2017 07:04:22 UTC