Would be good to land after https://github.com/w3c/browser-payment-api/pull/451 to avoid conflicts. Notably this does not allow serving up multiple options with different locales and allowing the browser to choose between them. I guess that is a non-goal. It's also noteworthy that this matches NotificationOptions already, so that's good. Maybe we can consolidate this `Localizable` type into Web IDL or similar. /cc @annevk @beverloo @tobie. Notifications defaults `lang` to `""` BTW to represent, I guess, no language selected. That makes sense. Also, this standard says it represents a BCP 47 language tag, but that's not quite accurate; a developer could pass in "asdf" and there's no normative text rejecting that. You'll instead want something similar to the verbiage at https://notifications.spec.whatwg.org/#language. -- 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/pull/455#issuecomment-286311314
Received on Tuesday, 14 March 2017 03:26:17 UTC