Allow ICU to normalize time zones

src/js/i18n.js

 // Copyright 2013 the V8 project authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // ECMAScript 402 API implementation.
 
 /**
  * Intl object is a single object that has some named properties,
  * all of which are constructors.
  */
@@ skipping 1556 matching lines @@
     timeZone: {writable: true},
     timeZoneName: {writable: true},
     tz: {value: tz, writable: true},
     weekday: {writable: true},
     year: {writable: true}
   });
 
   var formatter = %CreateDateTimeFormat(
     requestedLocale, {skeleton: ldmlString, timeZone: tz}, resolved);
 
-  if (!IS_UNDEFINED(tz) && tz !== resolved.timeZone) {

[adamk, 2015/12/10 17:33:13]

I'd be curious why the old code was specifically checking for a match. Did you
find anything in archeology?

[Dan Ehrenberg, 2015/12/10 17:55:36]

Not sure; it's been there since Jochen's snapshot. I was assuming it's because
this is a way of checking which works 99% of the time and makes intuitive sense
(why should it change, anyway? you'd think).

[adamk, 2015/12/10 19:34:07]

Given the lack of any test coverage for this if statement previously, I guess
the best we can do is give this a try.

+  if (resolved.timeZone === "Etc/Unknown") {
     throw MakeRangeError(kUnsupportedTimeZone, tz);
   }
 
   %MarkAsInitializedIntlObjectOfType(dateFormat, 'dateformat', formatter);
   ObjectDefineProperty(dateFormat, 'resolved', {value: resolved});
 
   return dateFormat;
 }
 
 
@@ skipping 525 matching lines @@
     }
 
     var locales = %_Arguments(0);
     var options = %_Arguments(1);
     return toLocaleDateTime(
         this, locales, options, 'time', 'time', 'dateformattime');
   }
 );
 
 })