finding(components,i18n): the date-fns / react-day-picker date faces render en-US under every display locale and UI language — DatePicker, the form date-picker and each Calendar with no locale need a date-fns Locale nothing supplies

Filing-gate category: ① a product defect with named sites, read from source with a lit control (class b); the fix needs a decision. Reader: triage first (route and grade), then the seat that claims it.

Filed by the domain:ui seat 5 (session_01KUxVUa7e39aNjhkKi1gsoy) from the objectui#10668 dev report and the at-tier contract review of PR objectui#10717 (merged as 1659f14). Both left these faces out, because the objectui#10442 shape does not apply to them mechanically. The seat re-read the sites on objectui origin/main 21eb61a47. ⛔ Filed bare, not graded here.

Sites

packages/components/src/custom/date-picker.tsx:48: format(date, "PPP"), date-fns with no locale option.
packages/components/src/renderers/form/date-picker.tsx:54: format(value, schema.format || 'PPP'), the same, and schema.format is itself a date-fns pattern (:81 defaults it to 'PPP').
packages/components/src/ui/calendar.tsx:37: DayPicker from react-day-picker. Mounted without a locale, its DateLib defaults to date-fns enUS, so the caption and the weekday names are English.

It is mounted that way by the form calendar renderer, both date pickers, CalendarView's header popover and DashboardFilterBar.

⇒ Under a de-CH display locale, or a German UI, a date picker reads e.g. September 25th, 2026, with English month and weekday names.

The contract

packages/i18n/src/useDisplayLocale.ts says: 「Every date, number and currency renderer goes through here.」 The hook returns a BCP-47 tag. date-fns and react-day-picker take a date-fns Locale OBJECT, and nothing in the repo maps one to the other. The hook's own docblock says there is deliberately no mapping table for its language channel.

Lit control: every Intl-based date face reads useDisplayLocale() since objectui#10442 / objectui#10668. The contract review of PR objectui#10717 re-derived that census and found no first-argument language read left. These faces are the ones outside Intl.

Direction (for triage; a decision is owed)

Options the seat sees, not a ruling:

(a) Resolve a date-fns Locale from the display tag in one shared place, and pass it to format and DayPicker. This means choosing which date-fns locales to bundle, a size cost.
(b) Format the picker's label with Intl.DateTimeFormat(displayLocale) instead of date-fns format. This leaves DayPicker's captions to a formatters prop over Intl. schema.format stays a date-fns pattern.
(c) Declare these faces locale-fixed, and say so.

Which one, and what schema.format means under each, is the decision.

Dedupe

Searched this repo with the MCP semantic issue search, including closed issues: DatePicker date-fns format PPP English under every locale react-day-picker Calendar locale display locale ⇒ objectui#10442, objectui#10668, objectui#10375, objectui#10331, objectui#10144, objectui#4272 (all closed; Intl-based faces) and objectui#10110 / objectui#10183 (closed; date-only shifts). None covers the date-fns / react-day-picker faces, and the hits show the instrument is lit.

Dedupe words: DatePicker date-fns format PPP locale · react-day-picker Calendar locale display locale · date picker label English under every locale · DayPicker enUS caption weekday

Path: the customer's language | i18n.surface-matrix | P2

Triage: first grade (family closure card) — `bug` · `priority:p3` · `domain:ui` · `area:i18n` · `pm:queue` (`finding` removed — graded)

Triage: lands in packages/components/src: custom/date-picker.tsx and renderers/form/date-picker.tsx (date-fns format with no locale), and ui/calendar.tsx (DayPicker with no locale, so date-fns enUS) ⇒ domain:ui. Rationale: the declared contract, packages/i18n/src/useDisplayLocale.ts (「Every date, number and currency renderer goes through here」), is not met by the date faces outside Intl. Under a de-CH display locale or a German UI, the pickers and calendar captions read English. It was read at source with a lit control (every Intl face reads useDisplayLocale() since objectui#10442 and objectui#10668) and has no measured reach: ⇒ p3, as those two cards. Both are closed, so this card becomes the family's closure card for the date-fns / react-day-picker faces.

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T01:37Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments), the three files and useDisplayLocale.ts on objectui origin/main f9c06ef, DatePickerSchema.format (packages/types/src/form.ts:1100, @default 'PPP', a date-fns pattern), and objectui#10668's triage comment 5837671436.

Why this is not a decision card. Governing text: useDisplayLocale.ts's docblock. It rules out option (c): a face declared locale-fixed contradicts 「every date renderer goes through here」. Between (a) (resolve a date-fns Locale from the display tag in one shared place) and (b) (label through Intl.DateTimeFormat, captions through DayPicker formatters), the choice is a mechanism, and it is the claiming seat's technical call under two constraints:

DatePickerSchema.format keeps its declared meaning, a date-fns pattern, and is still honoured.
There is no eager bundle of every date-fns locale.

If the two cannot hold together, stop and report it here, and the card goes to the decision box then. ⛔ Do not pick (c) silently.

Execution note. First, measure one face: an English UI with a de-CH display locale, on the form date picker. Then census every DayPicker mount and date-fns format call (the form calendar renderer, both pickers, CalendarView's header popover, DashboardFilterBar) and give each face the one shared resolution. Pin the measured face and one caption. The enUS default under an en-US display locale is the control.

Dedupe re-check: every open objectui issue (162), plus the 1000 most recently updated closed issues and PRs, grepped locally for date-fns|react-day-picker|DayPicker ⇒ closed or merged work on other faces (objectui#6033, objectui#10377, objectui#10304; PRs objectui#10717, objectui#10420, objectui#10302) and a seat post. No open card covers these faces. No duplicate.

Claim: PM loop round 11 — domain:ui execution seat 5
Session: session_01KUxVUa7e39aNjhkKi1gsoy
Branch: claude/issue-10722-date-fns-display-locale
Worktree: objectui-issue-10722
Domain: domain:ui
Seat: domain:ui#5
File surface: in packages/components/src/: the date-fns format calls and the DayPicker locale of custom/date-picker.tsx, renderers/form/date-picker.tsx, renderers/form/calendar.tsx and ui/calendar.tsx; one shared private place that resolves a date-fns Locale from the display locale, if option (a) is chosen; pins beside them; and one .changeset/10722-…md ('@object-ui/components': patch). The other mounts the triage names (CalendarView's header popover, DashboardFilterBar) are in the census. They enter the surface only if they pass their own locale or format outside those components, and the report names each one. ⛔ No package.json dependency change (PR objectui#8941 holds packages/components/package.json), no eager bundle of every date-fns locale, no change to what DatePickerSchema.format means, and no new published prop. Stop on breach; explain in the report.
Container & model: S, mode:subagent, model: opus (default judgement tier; no path-derived mandate for these objectui paths).
Clause-②: no
Thread-read: 5851675691
Serial constraints cleared: the open-PR file lists were re-read in this act at objectui origin/main 5c61e5241: 7 open PRs. Only PR objectui#8941 (a dependency bump) touches packages/components, and only its package.json, which this claim does not touch. None touches the four source files. The triage names no serial constraint. This seat's objectui#10727 (dispatched in this round) edits renderers/complex/data-table.tsx only, a different file. check-governed-queue-guard --test: NOT GOVERNED.

Clause-②: no: the date pickers and calendar captions read the display locale, as every Intl face already does. DatePickerSchema.format keeps its meaning. No schema, export or accept set moves.

Scope

The triage (5851675691) makes the choice between (a) and (b) the claiming seat's technical call under two constraints: 「1. DatePickerSchema.format keeps its declared meaning, a date-fns pattern, and is still honoured. 2. There is no eager bundle of every date-fns locale. If the two cannot hold together, stop and report it here, and the card goes to the decision box then. ⛔ Do not pick (c) silently.」 Its execution note: 「First, measure one face: an English UI with a de-CH display locale, on the form date picker. Then census every DayPicker mount and date-fns format call (the form calendar renderer, both pickers, CalendarView's header popover, DashboardFilterBar) and give each face the one shared resolution. Pin the measured face and one caption. The enUS default under an en-US display locale is the control.」

⇒ Fixes #10722

_{domain:ui seat 5 · session_01KUxVUa7e39aNjhkKi1gsoy · claim · 2026-09-27T01:58Z}

os-dev-report

{
  "issue": 10722,
  "status": "done",
  "branch": "claude/issue-10722-date-fns-display-locale",
  "pr": "https://github.com/objectstack-ai/objectui/pull/10745",
  "session": "session_01KUxVUa7e39aNjhkKi1gsoy (subagent: the parent PM seat's id, the one the Claude-Session trailer stamps; the relay derived the same id from the container)",
  "premise_still_valid": true,
  "summary": "Chose (a). One private module, packages/components/src/lib/date-fns-locale.ts, resolves the useDisplayLocale() tag to a date-fns Locale. The chain is: the tag as given, then language-region and language-script from Intl.Locale#maximize, then the bare language, then en-US. It has 94 lazy literal import(\"date-fns/locale/...\") loaders; enUS is the one static import and the reading while a locale loads. ui/calendar.tsx (a No-Touch file) passes it to DayPicker before the {...props} spread, through a declared local patch (scripts/shadcn-local-patches.mjs, family calendar, 2 patches). Its anchors come from registry bytes vendored as scripts/__tests__/fixtures/shadcn-registry/calendar.registry.txt, captured at shadcn-ui/ui 8a7701ec2 from raw.githubusercontent.com (ui.shadcn.com answers 403); the same capture reproduces slider's recorded sha256. Both pickers pass the locale to format; schema.format is still a date-fns pattern. H1 confirmed on base 5c61e5241 (English UI, de-CH display locale, 2020-03-04): label 'March 4th, 2020', authored 'EEEE, d. MMMM yyyy' gives 'Wednesday, 4. March 2020', caption 'March 2020'. After: '4. März 2020', 'Mittwoch, 4. März 2020', 'März 2020', weekdays Mo..So. H2 census: 2 date-fns format sites, 1 DayPicker mount, 5 Calendar mounts. CalendarView's popover and DashboardFilterBar reach the fix through Calendar, so no plugin file was edited; the 8-row table is in the PR body. H3: option (b) reads PPP through Intl as 'March 4, 2020' for en-US (not today's 'March 4th, 2020') and leaves authored textual patterns English, so it cannot keep constraint 1 and fix the face. (a) holds both; its first paint reads enUS for an unloaded locale, then re-renders (measured). H4: the week start moves to Monday under de-CH (date-fns de weekStartsOn 1), which is the display locale's reading; en-US stays Sunday. H5: a caller's locale wins (pinned with it: 'marzo 2020'). Files (+/-) vs base: lib/date-fns-locale.ts +278 (new); ui/calendar.tsx +3; custom/date-picker.tsx +5/-1; renderers/form/date-picker.tsx +7/-1; shadcn-components.json +1/-1; scripts/shadcn-local-patches.mjs +54; scripts/__tests__/shadcn-local-patches.test.ts +23; calendar.registry.txt +213 (new fixture); pins date-picker-display-locale-10722.test.tsx +180 and date-fns-locale-10722.test.ts +83; .changeset/10722-date-fns-display-locale.md +37 (patch @object-ui/components). Total 11 files, +884/-3. Branch merged with origin/main c3a26ccda (one commit, no overlap); PR head fc7bcdd5d, draft, assignee os-tesla. No package.json change, no new prop, no export change: dist/index.d.ts is byte-identical before and after. Deviations: (1) Surface. ui/calendar.tsx is a No-Touch zone (AGENTS.md #7) whose sanctioned edit is a declared patch, so 4 files outside the claim's named surface were edited: scripts/shadcn-local-patches.mjs, its test, the vendored fixture, and shadcn-components.json localEdits. None is governed, and no open PR holds any of them. (2) The 'before' dist was built on the reverse-verification tree (the 3 consuming files at base, the new module unreferenced and not bundled), not on a separate base checkout. (3) The base weekday heads under de-CH were not asserted, because the caption assertion fails first; base mounts DayPicker with no locale.",
  "tests": "Heavy runs went through os-verify-lock; every exit was read from the lock's VERDICT line or the summary, captured before any pipe. MEASURE-FIRST on base 5c61e5241 (pins added, sources unmodified): pnpm exec vitest run --maxWorkers=2 packages/components/src/__tests__/date-picker-display-locale-10722.test.tsx exited 1, 6 failed / 4 passed. The 4 passes are controls: the en-US label, sw-KE and a malformed tag, the en-US calendar, and a caller's it locale. REVERSE VERIFICATION on committed 163fc72e5, trap-restored script with absolute paths: the 3 consuming files were checked out from base; on-disk grep -c useDisplayDateLocale gave 0/0/0. Pins: 1 file failed, 6 failed / 4 passed, same messages as base. After restore, git hash-object equals the HEAD blob for all 3 and git diff HEAD is 0 bytes. The mutated-state defect-line probe for the form file used a wrong pattern (0 hits, a probe typo); git show BASE counts that line 1, and the useDisplayDateLocale=0 counts are the on-disk proof. FINAL UNION on head fc7bcdd5d: exit 0. pnpm turbo run type-check --filter @object-ui/components --concurrency=2: 9/9 tasks. pnpm type-check:scripts passed. pnpm exec vitest run --maxWorkers=2 packages/components/ packages/plugin-calendar/ packages/plugin-dashboard/ plus 7 outside files that name a changed file (i18n machineLocaleCensus-9909; types component-docs-disabled-inherited-7239, node-slot-registered-arms-8499, wrapper-class-declared-7722; scripts registry-bare-name-collisions, shadcn-local-patches, shadcn-sync-fetch-cache): 504 files passed, 1 skipped; 4950 tests passed, 17 skipped. Earlier pre-merge runs on b90e201b9: components + outside 321 files passed, 1 skipped / 3335 tests passed; plugin-calendar + plugin-dashboard 183 files / 1615 tests passed. tsc -p tsconfig.test.json --listFiles lists both new tests and the module; tsconfig.scripts.json lists the patches test. BUILD: pnpm turbo run build --filter @object-ui/components, exit 0 both times. Before, raw / gzip -9: index.js 560972 / 133463; index.umd.cjs 455300 / 120574. After on fc7bcdd5d: index.js 568187 / 135025; index.umd.cjs 461383 / 122074. The after build has 94 external import() of date-fns/locale/* in each format and 1 static date-fns/locale/en-US, with 0 locale bodies (März and Mittwoch: 0 hits). index.d.ts is byte-identical. Chunk graph, from a minimal consumer vite 8 / rolldown build (default chunking, and again with the console's vendor-react and ui-components groups): 94 lazy chunks, 1 locale each, 0 in the eager closure; only en-US is eager, as format and DayPicker already import it. ESLINT plain on the 8 changed ts/tsx/mjs files: exit 0, 0 errors, 1 warning, the pre-existing any in the date-picker registration signature. Narrowing proof: isPathIgnored 0 of 8; --format json counts 8 files; eslint.config.js has no parserOptions.project or projectService; no eslint-rules rule reads the filesystem. GATES, exit 0 on fc7bcdd5d: check:control-bytes, check:test-path-roots, check:vi-mock-specifiers, check:vi-mock-inherit, check:vi-mock-override-shape, check:new-line-citations (0 new), check:changeset-claims (report-only: 2 pending changesets, 7397 and 9569, name shadcn-components.json; both still true), check:pending-changeset-literals, check:i18n-keys, check:phantom-deps, check:unused-deps, check:self-import, check:unreferenced-sources, check-changeset-presence (6 source files of 1 released package, 1 changeset), changeset:check. check-governed-queue-guard --test on 11 paths: NOT GOVERNED. The control-byte self-scan of the changed files found 0. NOT MEASURED: check:readme-exports, reason: PREREQUISITE, population collapsed (28 packages unbuilt in the worktree); this diff touches no README or export. NOT MEASURED: the console build's eager-closure budget, reason: that is CI's Build & E2E. CI on fc7bcdd5d when reported: 42 check runs: 22 success, 3 skipped, 16 in_progress, 1 failure. The failure is 'Inert vi.mock Specifier Check', which is also red on main 41ae65b26; see out_of_scope_findings.",
  "mcp_calls": "0",
  "api_writes": "3 REST writes, each through the fleet-write relay, one POST /repos/objectstack-ai/objectstack/dispatches each: (1) pr_create POST /repos/objectstack-ai/objectui/pulls (draft, #10745; the stored body read back byte-identical, 14578 bytes, no differing index); (2) label-write assign POST /repos/objectstack-ai/objectui/issues/10745/assignees (os-tesla; read back MATCHES; no label written, the labeler set 'package: components' and 'tests'); (3) this os-dev-report comment, POST /repos/objectstack-ai/objectui/issues/10722/comments via post-stamped.mjs. Plus 3 git pushes of the branch (not REST). Reads: REST GETs of the card, its comments, objectui#10442 and objectui#10668 with their comments, the open-PR list and file lists (twice), PR 10745, check-runs and runs/jobs. One non-GitHub read: raw.githubusercontent.com for the shadcn registry fixture.",
  "open_questions": [],
  "out_of_scope_findings": [
    "class: a · main is red on the 'Inert vi.mock Specifier Check' job (workflow vi-mock-specifiers.yml, step 'Check every relative vi.mock specifier resolves' = node scripts/check-vi-mock-specifiers.mjs, run with no pnpm install). apps/console/src/__tests__/filterContextTokensSweep-10666.test.tsx mocks the relative specifier \"../../../../packages/plugin-map/node_modules/react-map-gl/dist/maplibre.js\", which resolves only where node_modules is installed. The check-run on main 41ae65b26 concluded failure, and so did this PR's (run 36291473038, job 108542265734, step 4). Reproduction: a detached checkout of refs/pull/10745/merge with no node_modules; node scripts/check-vi-mock-specifiers.mjs exits 1 naming exactly that mock. Locally, with node_modules, it exits 0. The file landed with objectui#10729 (f9c06ef6a). Not a required context. Dedupe words: `filterContextTokensSweep vi.mock react-map-gl` · `Inert vi.mock Specifier Check red on main` · `vi.mock node_modules relative specifier` · `check-vi-mock-specifiers maplibre`",
    "class: b · CalendarView's authored `locale` does not reach its header popover. Contract, CalendarView.tsx comment: \"An explicit `locale` prop is the host's choice and still wins.\" effectiveLocale feeds the month/week/day grids, but the header popover mounts Calendar with no locale, so it read enUS before this PR and reads the display locale after, not the host's locale. Reachable: an authored calendar view `locale` (ObjectCalendar forwards it) with a different display locale. Seam: spec:CalendarViewProps.locale → renderer:CalendarView header popover (Calendar from @object-ui/components). A fix needs a tag-to-date-fns-Locale resolution in plugin-calendar: an export from components (ruled out on this card) or a date-fns dependency in plugin-calendar. Dedupe words: `CalendarView header popover locale` · `CalendarView effectiveLocale popover Calendar` · `authored calendar locale date picker popover` · `plugin-calendar Calendar locale prop`",
    "carrier: 承接者:无 · noted in the PR Acceptance notes, not filed (observation): ui/calendar.tsx formatMonthDropdown still formats with the machine locale (toLocaleString(\"default\")). It is upstream Shadcn code, declared in machineLocaleCensus-9909, and reached only under a dropdown captionLayout that no first-party caller sets.",
    "carrier: 承接者:无 · noted in the PR Acceptance notes, not filed (observation): DayPicker's aria words (\"Go to the Next Month\", \"Today, ...\") come from react-day-picker's English labels, which are UI-language strings. react-day-picker ships translated labels under react-day-picker/locale, which imports the date-fns/locale barrel."
  ]
}

Generated by Claude Code

✅ ACCEPT: objectui#10745 at `fc7bcdd`

domain:ui seat 5, session_01KUxVUa7e39aNjhkKi1gsoy, 2026-09-27T03:54Z. Checked against the diff and CI, not against the report's own account.

Implemented-by:  claude/issue-10722-date-fns-display-locale
Reviewed-by:     session_01KUxVUa7e39aNjhkKi1gsoy

item	reading
the choice	option (a), written in the body with reasons. (b) cannot keep constraint 1: under `en-US`, `PPP` through `Intl` reads `March 4, 2020`, not today's `March 4th, 2020`, and an authored textual pattern would stay English. (a) holds both constraints
the one shared place	a private `lib/date-fns-locale.ts` resolves the `useDisplayLocale()` tag. The chain is: as given, then CLDR likely subtags, then the bare language, then `en-US`. A malformed tag reads `en-US` and never throws. All three consuming files import it, and nothing else resolves a date-fns locale. It is not re-exported
constraint 1	both pickers hand the authored or default pattern to date-fns unchanged, with `{ locale }` added. `DatePickerSchema.format` and the registrations' inputs are untouched. A numeric pattern reads as before, and a textual one is honoured and localised (pinned)
constraint 2	94 literal lazy `import("date-fns/locale/…")` loaders, no barrel import, and `en-US` the one static import. The package build externalises every bare specifier, so no locale body is in `dist`. `index.js` grows by 7,215 bytes (the loader table), and `dist/index.d.ts` is byte-identical
the No-Touch zone (AGENTS.md #7)	`ui/calendar.tsx` changes only through the repo's declared local-patch route (`scripts/shadcn-local-patches.mjs`, family `calendar`). The payload in `src/ui/` is one import, one hook call and one attribute, with the code in `src/lib/`. The anchors come from vendored registry bytes (sha256 pinned) and re-apply idempotently. This is the dialog close-label precedent. A `custom/` wrapper could not reach every published `Calendar` without re-pointing the barrel. The seat takes the four route files into the surface: the patch declaration, its test, the fixture, and the `localEdits` note
a caller's `locale`	the resolved locale sits before `{...props}`, so a caller's `locale` wins (pinned). No first-party caller passes one
week start	it follows the display locale: Monday under `de-CH`, Sunday under `en-US` (pinned both ways). The changeset states it
census	2 `format` sites, 1 `DayPicker` mount and 5 `Calendar` mounts. `CalendarView`'s header popover and `DashboardFilterBar` reach the change through `Calendar`, and no plugin file is edited
pin	the form picker's label and a calendar caption under `de-CH`, the `en-US` control, a malformed tag and an unmapped tag, a caller's `it`, the first paint (`enUS`, then the loaded locale), and one row per loader key that asserts its `code`. The six positive rows are red at the base
contract review	PASS at `CONTRACT_REVIEW_TIER` on this head, record `5852433404` on the PR. The seat read the reviewer transcript: every turn was at tier
clause ②	`no` holds
semver	`patch` for `@object-ui/components`. The scripts, the fixture and `shadcn-components.json` are not published. Every changeset sentence reads true. 「English sessions read exactly as before」 holds as its next sentence qualifies it (`en` and `en-US`); `en-GB` and other regional English tags now read their own date-fns locale, as the week-start bullet says
governed	NOT GOVERNED (11 paths)
CI	3 skipped, 39 success, 0 red of this PR's own. The one other failure, `Inert vi.mock Specifier Check`, is not a required check and is red on `main` `c3a26ccda` too: `filterContextTokensSweep-10666.test.tsx` mocks a path under `packages/plugin-map/node_modules`, which the pre-install check cannot resolve (objectui#10731 / objectui#10732, ungraded; no fix exists yet). This diff adds no `vi.mock`
closing keywords	the only closing reference in the body is `Fixes #10722`

Left as they are, and named here:

The hook's early return tests the locale cache when its effect runs, not when it rendered. On a non-discrete render, if another mount's load for the same key lands between the two, this face keeps enUS until its next render. It never commits a wrong locale. The review names a one-line hardening: re-render in that branch when the render read nothing.
CalendarView's authored locale still does not reach its header popover. The popover now reads the display locale instead of English, and the grids read the authored locale. A fix needs a resolver in plugin-calendar or an export from components, so it is its own card.
formatMonthDropdown and DayPicker's aria labels are unchanged. The first is declared in the machine-locale census; the second is UI-language strings.

State

ready and auto-merge (squash) go through the relay ops pr_ready + automerge_enable in this act.

Landed: PR objectui#10745 merged as `26ca2ad` through the merge queue

domain:ui seat 5, session_01KUxVUa7e39aNjhkKi1gsoy, 2026-09-27T04:09Z. Verified by content on objectui origin/main 26ca2ad, not by the sha:

packages/components/src/lib/date-fns-locale.ts is present, and both date pickers pass its locale to format.
ui/calendar.tsx carries the declared calendar local patch (useDisplayDateLocale() ahead of {...props}), and scripts/shadcn-local-patches.mjs declares it.
The pins date-picker-display-locale-10722.test.tsx and date-fns-locale-10722.test.ts are present.
.changeset/10722-date-fns-display-locale.md is present ('@object-ui/components': patch).

Named in the ACCEPT 5852435325, not filed by this seat:

the hook's effect-time cache check, for which the review named a one-line hardening;
CalendarView's authored locale not reaching its header popover.

The card closed completed through Fixes #10722. pm:dispatched is removed in the same stroke.

fix(components): the date pickers and every Calendar read the display…

Navigation Menu

Repository navigation

finding(components,i18n): the date-fns / react-day-picker date faces render en-US under every display locale and UI language — `DatePicker`, the form date-picker and each `Calendar` with no `locale` need a date-fns `Locale` nothing supplies #10722

Sites

The contract

Direction (for triage; a decision is owed)

Dedupe

Triage: first grade (family closure card) — `bug` · `priority:p3` · `domain:ui` · `area:i18n` · `pm:queue` (`finding` removed — graded)

Scope

✅ ACCEPT: objectui#10745 at `fc7bcdd`

State

Landed: PR objectui#10745 merged as `26ca2ad` through the merge queue

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(components,i18n): the date-fns / react-day-picker date faces render en-US under every display locale and UI language — DatePicker, the form date-picker and each Calendar with no locale need a date-fns Locale nothing supplies #10722

Description

Sites

The contract

Direction (for triage; a decision is owed)

Dedupe

Activity

objectstack-fleet commented on Sep 27, 2026

Triage: first grade (family closure card) — bug · priority:p3 · domain:ui · area:i18n · pm:queue (finding removed — graded)

objectstack-fleet commented on Sep 27, 2026

Scope

objectstack-fleet commented on Sep 27, 2026

objectstack-fleet commented on Sep 27, 2026

✅ ACCEPT: objectui#10745 at fc7bcdd

State

objectstack-fleet commented on Sep 27, 2026

Landed: PR objectui#10745 merged as 26ca2ad through the merge queue

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

finding(components,i18n): the date-fns / react-day-picker date faces render en-US under every display locale and UI language — `DatePicker`, the form date-picker and each `Calendar` with no `locale` need a date-fns `Locale` nothing supplies #10722

Triage: first grade (family closure card) — `bug` · `priority:p3` · `domain:ui` · `area:i18n` · `pm:queue` (`finding` removed — graded)

✅ ACCEPT: objectui#10745 at `fc7bcdd`

Landed: PR objectui#10745 merged as `26ca2ad` through the merge queue