demo · v143

Localised fields explorer

The structured-JSON shape lets each account field be a string OR an object keyed by BCP47 language tag. Pick a viewer locale and watch the chooser re-render with names, emails, and CTAs all in the right script — Spanish for an Argentine user, Korean for the Seoul team, English for everyone else.

Pick a viewer locale

The IdP's JSON

How the chooser resolves a locale

  1. Each field can be a plain string OR a { <locale-tag>: string } object.
  2. Chrome matches the user's UI locale against the object's keys using BCP47 fallback (e.g. es-AR → es → first available).
  3. If only a plain string is given, that string is used regardless.
  4. This page implements the same resolution algorithm — useful for IdP operators sanity-checking their localisation.
// IdP returns:
{
  "id": "u_001",
  "name": { "en": "Maria Garcia", "es": "María García" },
  "email": "maria@example",
  "approve_button_text": { "en": "Continue", "es": "Continuar", "ko": "계속" }
}

see also