Skip to content

i18n: locale-switch pending state and SW-upgrade catalog warm (lazy-locale polish) #2003

Description

@Chris0Jeky

Two non-blocking refinements from the PR #2002 Codex round (both declined for the merge under the severity stopping rule, tracked here):

  1. Bounded <html lang> mismatch while a locale chunk is in flight. Flip-first means AT briefly sees lang=it/es while English fallback renders (window = one chunk fetch; failure now reverts honestly). Options: flip-after-load with a pending/disabled state in the picker, or hold <html lang> until the catalog registers.
  2. Offline after a service-worker upgrade loses a previously-cached locale. Locale chunks are excluded from precache (deliberate, Decide how the i18n rollout is budgeted against the total-JS gate, before step 3 #1858) and runtime-cached by hash, so a new build's hashes aren't warm until the next online load — the persisted preference falls back to English offline until then. Option: on SW activate, warm the preferred locale's new chunk when the stored preference is non-en.

Neither affects correctness online, and English fallback is the documented degraded state. Do both together if the picker grows a pending state.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority IIIValuable but unscheduled: residuals, tech-debt, performance, depth work.dogfoodingFrom real personal/beta use; evidence-grade product feedback (exempt from intake severity bar).frontendPrimary implementation impact in Vue/TypeScript UI and client runtime.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions