Return DefaultLocale() when calling Intl.Locale() with an absent/undefined tag argument? about proposal-intl-locale

[littledan]

I'd be fine with this. Any other opinions? @zbraniecki

[zbraniecki]

This should return und. Just like

let loc = new Intl.Locale(undefined, {
  calendar: "gregorian"
}); // "und-u-ca-gregorian"

[zbraniecki]

Per BCP47 4.1.5:

       *  The 'und' (Undetermined) primary language subtag identifies
          linguistic content whose language is not determined.  This
          subtag SHOULD NOT be used unless a language tag is required
          and language information is not available or cannot be
          determined.  Omitting the language tag (where permitted) is
          preferred.  The 'und' subtag might be useful for protocols
          that require a language tag to be provided or where a primary
          language subtag is required (such as in "und-Latn").  The
          'und' subtag MAY also be useful when matching language tags in
          certain situations.

[littledan]

My understanding is that ECMA 402 has been avoiding exposing the root locale. If we start throwing und around, we'd be breaking that.

My understanding is that this was discussed at the ECMA 402 call, and the conclusion was to continue to require a locale argument.

[littledan]

We discussed this possibility in the March Intl call and concluded that we should continue to require the string parameter. There was some debate about the semantics, whether it should default to und or the system locale, but both had disadvantages an unclear motivation.