Classic298 bbbe2b66b4 fix: use static month names in getTimeRange to prevent OS locale leaking into sidebar (#22454) ...

getTimeRange returns month names that are used as i18n translation keys
(consumed via \.t(chat.time_range) in the sidebar, search modal, etc.).
The keys must be exact English strings like 'January', 'February', etc.

Previously, toLocaleString('default', { month: 'long' }) was used to
generate these keys. The 'default' locale defers to the browser's locale
resolution, which in Firefox with intl.regional_prefs.use_os_locales=true
picks up OS regional settings instead of the browser language. This caused
German month names (e.g. 'Februar', 'Januar') to appear in the sidebar for
users whose OS region is set to Germany, even when both browser and app
language are set to English. Chrome was unaffected because it ignores OS
regional settings for the 'default' locale.

Since i18n has no translation key for 'Februar', the German string passed
through untranslated. Replace toLocaleString with a static MONTH_NAMES
array lookup to make the intent explicit and eliminate any browser/OS
locale dependency.

2026-03-08 16:44:03 -05:00

..

lib

fix: use static month names in getTimeRange to prevent OS locale leaking into sidebar (#22454)

2026-03-08 16:44:03 -05:00

routes

enh: code interpreter pyodide fs

2026-03-07 19:23:18 -06:00

app.css

refac

2026-02-25 20:17:39 -06:00

app.d.ts

…

app.html

refac

2026-02-22 18:58:47 -06:00

tailwind.css

chore: format

2026-02-28 21:28:59 -06:00