You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2023. It is now read-only.
I'm currently running PhantomJS through Chutzpah in VS2017, with my local time zone set to "Canberra, Melbourne, Sydney". It seems though that the engine is having issues when creating dates around the transition between Australian Daylight Time and Australian Standard Time.
The issue is reproducible with a test that does the following:
var result = new Date(2017, 3, 1, 16);
expect(result.getHours()).toBe(16);
This will actually fail, specifying that getHours() returned 17.
The test doesn't fail, nonetheless, when it is run within a browser (Tested in Chrome, FF and IE).
A couple questions, then:
Why is the time being offset on "01/04/2017 16:00" if the offset was actually in effect on "02/04/2017 3:00"
If I don't provide a time zone for the date, shouldn't the engine assume that I need exactly the specified date/time on the current time zone, as opposed to attempting to offset it?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Due to our very limited maintenance capacity, we need to prioritize our development focus on other tasks. Therefore, this issue will be automatically closed (see #15395 for more details). In the future, if we see the need to attend to this issue again, then it will be reopened. Thank you for your contribution!
Hi.
I'm currently running PhantomJS through Chutzpah in VS2017, with my local time zone set to "Canberra, Melbourne, Sydney". It seems though that the engine is having issues when creating dates around the transition between Australian Daylight Time and Australian Standard Time.
The issue is reproducible with a test that does the following:
This will actually fail, specifying that getHours() returned 17.
The test doesn't fail, nonetheless, when it is run within a browser (Tested in Chrome, FF and IE).
A couple questions, then:
Thanks in advance.
The text was updated successfully, but these errors were encountered: