1198543 - toLocaleString with no parameters caches timezone

Status: RESOLVED DUPLICATE of bug 1300110

(Core :: JavaScript: Internationalization API, defect)

Description

[Zibi Braniecki [:zbraniecki][:gandalf]]

When I pass first parameter to toLocaleString it does use the current timezone properly, but if I omit the first parameter, it does use the old timezone.

Steps to reproduce:

1) Set a timezone on your device to America/Los Angeles
2) Restart a phone
3) (new Date()).toLocaleString(navigator.languages); // proper local datetime with America/Los Angeles timezone
4) (new Date()).toLocaleString(); // proper local datetime with America/Los Angeles timezone
5) Change time zone to America/New York
6) (new Date()).toLocaleString(navigator.languages); // proper local datetime with America/New York timezone
7) (new Date()).toLocaleString(); // old datetime with America/Los Angeles timezone

Expected result:

In setp 7) the datetime should use America/New York

Comment 1

[Zibi Braniecki [:zbraniecki][:gandalf]]

[16:40:12] Waldo:	gandalf: it's a bug, we're trying to cache a formatter a bit too hard

Comment 2

[Jeff Walden [:Waldo]]

Bug 1205546 fixed some aspects of this, on systems that notify when the system time zone changes.

But if you move between time zones with identical time zone adjustment, no change will be detected -- e.g. you might see a stale "MST" in a string instead of "PDT", if you moved between the two.  So this is partially fixed.

Comment 3

[André Bargull [:anba]]

Let's dup this to bug 1300110 for the missing time zone updates (and bug 1300110 for the identical time zone adjustment issue).