Summary
Kibana now consults the browser's `Accept-Language` header on all deployment types, not only serverless, when neither a user profile language nor a `KBN_LOCALE` cookie applies; self-managed users may see the UI language change on upgrade. The diff also adds a precedence rule the PR body does not mention: an explicitly configured `i18n.defaultLocale` (any value other than the built-in `en`) now outranks browser detection, contradicting the body's claim that the priority chain ordering is unchanged. The internationalization settings reference page (docs/reference/configuration-reference/internationalization-settings.md in the kibana repo) was updated as part of the PR itself and the published page already describes the new five-step resolution chain.
Why this needs docs: Why this needs docs: the reference page was already updated inside the PR, so no new drafting is needed, but the PR body understates the change (explicit i18n.defaultLocale now outranks Accept-Language) and the docs update introduced a section-level applies_to badge (stack: ga 9.5) that conflicts with inline self-managed GA tags on bullets in the same section, so a badge-coherence and release-note verification pass is warranted; confidence reduced for the partially accurate premise.
Resources
- PR #275996 — [Per-User Translations] "Use browser default" for all environments
Availability
| Channel |
Details |
| Stack |
v9.5.0 |
| Serverless |
Jul 13–Jul 17 |
| Feature flag |
None — active by default |
Created with Docs Quest Scanner by @florent-leborgne
Suggested edits
Internationalization settings in Kibana > Per-user language selection > Resolution priority
- What the docs say: Section badge renders as '(Elastic Cloud Serverless: Generally available, Elastic Stack: Planned)' while a bullet inside the same section is tagged '(Self-managed Elastic deployments: Generally available) User Profile page'. The resolution list already describes the new chain: profile → cookie → explicitly set i18n.defaultLocale → Accept-Language → default.
- What to add: Content was already updated in the PR; the remaining work is verification, not drafting. Check the applies_to scoping: the new section-level 'stack: ga 9.5' badge contradicts the inline 'self-managed: GA' tag on the User Profile bullet, leaving the availability of per-user language selection on earlier stack versions ambiguous. The PR also replaced the old serverless-only Accept-Language description outright, so pre-9.5 stack readers now rely solely on the section badge to know browser detection did not apply to them; confirm that scoping is intentional per cumulative docs rules. Finally, confirm the 9.5 release notes mention that self-managed users may see the UI language change on upgrade, and that the explicit i18n.defaultLocale precedence (missing from the PR's release note text) is captured. Applies from 9.5.0 and in serverless (serverless already used browser language detection).
Summary
Kibana now consults the browser's `Accept-Language` header on all deployment types, not only serverless, when neither a user profile language nor a `KBN_LOCALE` cookie applies; self-managed users may see the UI language change on upgrade. The diff also adds a precedence rule the PR body does not mention: an explicitly configured `i18n.defaultLocale` (any value other than the built-in `en`) now outranks browser detection, contradicting the body's claim that the priority chain ordering is unchanged. The internationalization settings reference page (docs/reference/configuration-reference/internationalization-settings.md in the kibana repo) was updated as part of the PR itself and the published page already describes the new five-step resolution chain.
Why this needs docs: Why this needs docs: the reference page was already updated inside the PR, so no new drafting is needed, but the PR body understates the change (explicit i18n.defaultLocale now outranks Accept-Language) and the docs update introduced a section-level applies_to badge (stack: ga 9.5) that conflicts with inline self-managed GA tags on bullets in the same section, so a badge-coherence and release-note verification pass is warranted; confidence reduced for the partially accurate premise.
Resources
Availability
Created with Docs Quest Scanner by @florent-leborgne
Suggested edits
Internationalization settings in Kibana > Per-user language selection > Resolution priority