time zone name not displayed when set via timeZoneName in ECMAScript Internationalization API - by dstorey [MSFT]

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

ID 795321 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 7/29/2013 5:14:34 PM
Access Restriction Public



http://jsfiddle.net/dstorey/YwnsR/ (default time zone)
http://jsfiddle.net/dstorey/gLnvQ/ (UTC time zone, long name)
http://jsfiddle.net/dstorey/gLnvQ/1/ (UTC time zone, short name)


0. Load the URLs above in IE11
1. Open F12 console
2. Click Run


For first URL, in the console,  it should show the hour and time zone name that you are currently in, using short representation.

I'm in Pacific Time, so in Chrome, it displays:

"4 PM PT " (it should probably be PDT as it is daylight savings time)

For http://jsfiddle.net/dstorey/gLnvQ/ it should show the hour and time zone using UTC, using long representation.

In Chrome it displays "12 AM GMT+00:00", but I suppose it could also use the full name of the time zone, such as "Coordinated Universal Time". I don't think the spec defines exactly where the values of the time zone name should be.


Only the hour is displayed in IE11:

Such as

"4 PM" (first link)
"12 PM" (second link)


* The timeZoneName property is being set correctly on the DateTimeFormat, so it is just not being used when formatting the string. This makes the formatted date/time ambiguous. 

* This is less of an issue as in IE, you can only use the default time zone and UTC. Chrome allows you to to set any time zone (the spec says only "utc" and undefined are needed, but others can be implemented in certain situations).


* http://www.ecma-international.org/ecma-402/1.0/#sec-6.4
* http://www.ecma-international.org/ecma-402/1.0/#sec-12.3.2
Sign in to post a comment.
Posted by Microsoft on 8/21/2013 at 12:49 PM
Thank you again for your feedback. We were able to validate your feedback. However we will not be able to address this bug during the current release.

Your feedback is very important to us, and it helps us improve the quality of Internet Explorer. We continue to welcome more feedback, so please don't hesitate to report other ways that we can improve Internet Explorer.

Best regards,
The Internet Explorer Team
Posted by Microsoft on 7/31/2013 at 3:26 PM
Thank you for your feedback. We will be investigating this issue further.

Best regards,

The Internet Explorer Team
Posted by dstorey [MSFT] on 7/29/2013 at 9:41 PM
FWIW, here is the data for the time zone names: http://www.unicode.org/cldr/charts/by_type/timezones.north_america.html (that link is for North America, but the others are linked at the top)

If I’m using "undefined" for timeZone and "short: for timeZoneName, in the "en" locale, and I'm in Seattle, it should be:
"PDT" http://www.unicode.org/cldr/charts/by_type/timezones.north_america.html#3015d691a6575945

Using timeZoneName: "long" it should be:
"Pacific Daylight Time" http://www.unicode.org/cldr/charts/by_type/timezones.north_america.html#398cc9f22c64ea56
Posted by dstorey [MSFT] on 7/29/2013 at 5:19 PM
The IE TestingCenter includes tests for this, which it passes:

* http://samples.msdn.microsoft.com/ietestcenter/Javascript/testcases_intl.html#19-30
* http://samples.msdn.microsoft.com/ietestcenter/Javascript/testcases_intl.html#19-31

This is misleading, as it does support the timeZoneName with the correct values, but does nothing with them. In effect, it is useless for developers. Or worse than useless, as it makes it harder to test for support when it is actually implemented so that it is used in the formatting of the date.