demo · v143 · deprecation

Getter vs getter matrix

For any locale, calls the legacy property getter and the new method side by side. Reports whether your browser still serves both, whether they return equal values, and which accessors are already gone. The summary row tells you how much of your code will break the day the legacy path is removed.

probed
0
both match
0
differ
0
getter removed
0

What "differ" means here

In Chrome 143 the legacy getter still works. If you see a diff, it usually means the getter returns a slightly older snapshot of the data; both APIs are correct but the method form is the spec'd one.

"Getter removed" — Chrome's already pulled the legacy version. Calls to .foo will be undefined. Code reading the property crashes at runtime.

const l = new Intl.Locale("ar-EG");
l.calendars              // legacy — deprecated, may be removed
l.getCalendars()         // current — TC39-spec'd

see also