flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Landini (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (FLEX-34861) Date dst not considered with seconds/milliseconds
Date Wed, 27 May 2015 16:08:17 GMT

     [ https://issues.apache.org/jira/browse/FLEX-34861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex Landini updated FLEX-34861:
--------------------------------
    Comment: was deleted

(was: As a workaround I did:
{code}
var date:Date = new Date();
var cloned:Date = ObjectUtil.clone(date) as Date;
cloned.seconds = 0;
cloned.milliseconds = 0;
cloned.minutes += date.timezoneOffset - cloned.timezoneOffset;
{code}

cloned is the date with seconds and milliseconds sets to 0.)

> Date dst not considered with seconds/milliseconds
> -------------------------------------------------
>
>                 Key: FLEX-34861
>                 URL: https://issues.apache.org/jira/browse/FLEX-34861
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: .Unspecified - Framework
>    Affects Versions: Apache Flex 4.14.1
>         Environment: Windows, Flash player 16
>            Reporter: Alex Landini
>
> Settings seconds and milliseconds  on date during the dst change wrongly the timezone.
> For instance by executing the following code snippet across dst (Europe/Rome timezone):
> {code}
> var date:Date = new Date();
> trace(date);				
> date.seconds = 0;
> trace(date);	
> {code}
> it prints out: 
> {code}
> Sun Oct 25 02:17:22 GMT+0200 2015
> Sun Oct 25 02:17:00 GMT+0100 2015
> {code}
> The same happens for milliseconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message