You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v26.x: Intl.DateTimeFormat specification bugs when formatting Temporal objects #67484
How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior? Why is that the expected behavior?
1 10/2026 AD
2 2024年12月25日
3 2024年12月25日
Chrome for Testing 158.0.8127.18 prints these lines.
Line 1: an era option alone does not count as a year or month field, so the year-month defaults still apply and the year and month are printed next to the era.
Lines 2 and 3: the caller asked for month: "long". In Node 26, new Intl.DateTimeFormat("zh-CN", { year: "numeric", month: "long", day: "numeric" }).format(new Date(2024, 11, 25)) prints 2024年12月25日, so toLocaleString should print the same. Passing the PlainDate to that formatter's format() prints 2024/12/25 too.
main is on V8 15.6, so it has the second fix, and the open V8 15.7 and 15.8 updates would bring the first. Could both be backported to v26.x?
Lines 2 and 3 are only the case where the formatter keeps every field. When a Temporal type drops a field (for example PlainYearMonth drops day), V8 still prints a numeric month. That part is not fixed in V8 yet: https://issues.chromium.org/issues/553245554
changed the title [-]v26.x: please backport two V8 Temporal formatting fixes (d785c2ad7a2c, 93603e3f07a9)[/-][+]v26.x: Intl.DateTimeFormat specification bugs when formatting Temporal objects[/+]on Nov 17, 2026
Activity
docs(upstream): list the 2026-11-15 filings and link each to its reti…
[-]v26.x: please backport two V8 Temporal formatting fixes (d785c2ad7a2c, 93603e3f07a9)[/-][+]v26.x: Intl.DateTimeFormat specification bugs when formatting Temporal objects[/+]