Skip to content

v26.x: Intl.DateTimeFormat specification bugs when formatting Temporal objects #67484

Open

Description

@craig-o-curtis

Version

v26.12.1 (V8 14.6.202.34-node.40, ICU 78.3)

Platform

Darwin 27.0.0 arm64

Subsystem

intl (V8 Temporal formatting)

What steps will reproduce the bug?

const ym = Temporal.PlainYearMonth.from({ calendar: "gregory", year: 2026, month: 10 });
console.log("1", ym.toLocaleString("en-US", { calendar: "gregory", era: "short" }));
const date = Temporal.PlainDate.from("2024-12-25");
console.log("2", date.toLocaleString("zh-CN", { calendar: "gregory", year: "numeric", month: "long", day: "numeric" }));
console.log("3", date.toLocaleString("ja-JP", { calendar: "gregory", year: "numeric", month: "long", day: "numeric" }));

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.

What do you see instead?

1 AD
2 2024/12/25
3 2024/12/25

Additional information

Both are fixed in V8, after the 14.6 branch:

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

Activity

  1. 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
  2. added
    v8 engineIssues and PRs related to the V8 dependency.
    v26.xIssues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch.
    on Nov 17, 2026
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

    v26.xIssues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch.v8 engineIssues and PRs related to the V8 dependency.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions