> 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. Yeah. Non-goal I think. > 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. I was thinking the same.... would be great to have this in Web IDL. Maybe we can craft `Localizable` here first, and then push it to WebIDL? > Notifications defaults lang to "" BTW to represent, I guess, no language selected. That makes sense. Will fix. > 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. Yeah, that's some good wording. -- 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-286321529
Received on Tuesday, 14 March 2017 04:51:23 UTC