- From: Domenic Denicola <notifications@github.com>
- Date: Mon, 12 Jun 2017 12:34:42 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 12 June 2017 19:35:25 UTC
> @domenic was mentioning technically this might not be that bad given how the webidl works... To expand: if we change the type to DOMString, - `supportedMethods: ["foo"]` will be treated by implementations as `supportedMethods: "foo"`, which does not break anyone's apps. - `supportedMethods: ["foo", "bar"]` will be treated by implementations as `supportedMethods: "foo,bar"`, which will break things. (This is because converting to DOMString via Web IDL is basically the same as calling `x.toString()`, and `toString()` for arrays behaves like the above.) So it only breaks when people are already using multiple supported methods (with the same data), which seems less likely today. -- 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/549#issuecomment-307896123
Received on Monday, 12 June 2017 19:35:25 UTC