Wrong date calculation in certain chrome version after using setZone()

    var isoString = "2019-10-10T10:00:00.000Z";
    var start = DateTime.fromISO(isoString);
    
    for (var i = 0; i < 24; i++) {
        var nozone = start.plus( Duration.fromObject({ hours: i }));
        var withZone = nozone.setZone("Asia/Beirut");
        console.log("iso nozone", nozone.toISODate(), nozone.toISOTime());
        console.log("iso withzone", withZone.toISODate(), withZone.toISOTime());
        console.log("nozone", nozone.day);
        console.log("withZone", withZone.day);
    }

you will notice the withZone day go from 10 -> 12 -> 11

around the record for the wrong date, the iso string goes from “iso withzone 2019-10-10 23:00:00.000+03:00” to “iso withzone 2019-10-12 00:00:00.000+27:00” to “iso withzone 2019-10-11 01:00:00.000+03:00”

in the browser versions that go wrong.

Doesn’t happen in Version 78.0.3904.97 (Official Build) (64-bit)

Does happen in: Version 80.0.3966.0 (Official Build) canary (64-bit) Version 80.0.3964.0 (Official Build) dev (64-bit) Version 80.0.3964.0 (Official Build) dev (32-bit)

[icambron]

The good folks at Google have informed me this is in fact according to spec. Which is means that basically the “workaround” is here to stay. Which is fine; it works.

[icambron]

@notlikethis1 It’s now in the main Chrome channel. I wrote this update because I’ve had an influx of new reports by devs who aren’t on the latest version of Luxon.

I’m also going to try out a slightly cleaner fix once I have a chance to test that it works on other browsers and supported Node versions