Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Date: Mon, 5 Nov 2012 19:38:12 +0000 (UTC)
From: "Alex Harui (JIRA)" <jira@apache.org>
To: flex-dev@incubator.apache.org
Message-ID: <288803171.70050.1352144292967.JavaMail.jiratomcat@arcas>
Subject: [jira] [Resolved] (FLEX-29003) Event.clone() does not copy
 properties target and currentTarget
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Harui resolved FLEX-29003.
-------------------------------

    Resolution: Won't Fix
      Assignee: Alex Harui

This is a runtime issue/limitation
                
> Event.clone() does not copy properties target and currentTarget
> ---------------------------------------------------------------
>
>                 Key: FLEX-29003
>                 URL: https://issues.apache.org/jira/browse/FLEX-29003
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Events
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>         Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>            Reporter: Adobe JIRA
>            Assignee: Alex Harui
>
> Steps to reproduce:
> 1. recieve Event e with e.target != null, e.currentTarget != null
> 2. var myevent:Event = e.clone();
>  
>  Actual Results:
>  myevent.target == null
>  myevent.currentTarget == null
>  
>  Expected Results:
>  myevent.target == event.target;
>  myevent.currentTarget == event.currentTarget;
>  
>  
>  Workaround (if any):
>  X-(
>  tested
>  SDK 3.6: Problem present
>  SDK 4.5.1: Problem present
>  SDK 4.6: Problem present
>  Desided by design?
>  (not mentioned in reference http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/events/Event.html#clone%28%29 )

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira