Mailing-List: contact issues-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Date: Fri, 12 Sep 2014 10:50:34 +0000 (UTC)
From: "Isha Hura (JIRA)" <jira@apache.org>
To: issues@flex.apache.org
Message-ID: <JIRA.12601327.1343984364000.17613.1410519034164@Atlassian.JIRA>
In-Reply-To: <JIRA.12601327.1343984364000@Atlassian.JIRA>
References: <JIRA.12601327.1343984364000@Atlassian.JIRA>
 <JIRA.12601327.1343984364250@arcas>
Subject: [jira] [Commented] (FLEX-33156) focusInHandler() in spark Scroller
 doesn't null check focusManager property before using
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FLEX-33156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131368#comment-14131368 ] 

Isha Hura commented on FLEX-33156:
----------------------------------

This is still reproducible in flex sdk 4.6.0 with air 4.0 build number 1628.

> focusInHandler() in spark Scroller doesn't null check focusManager property before using
> ----------------------------------------------------------------------------------------
>
>                 Key: FLEX-33156
>                 URL: https://issues.apache.org/jira/browse/FLEX-33156
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: Scroller
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>            Reporter: Roland Zwaga
>            Assignee: Carol Frampton
>             Fix For: Adobe Flex SDK Next
>
>         Attachments: Scroller.as.patch
>
>
> the focusHandler() method wrongfully assumes that the focusManager is always a valid instance. When checking the focusManager property in UIComponent it is clear that in certain cases this property can return a null value.
> So in some cases this can lead to an RTE. I have encountered this once in my current project but find it very hard to reproduce. Basically a Scroller instance that was displayed in a popup window gave this RTE after the popup was removed.
> Reproducable or not, I believe the null check should be added seeing the fact that the focusManager property explicitly returns null in some cases.
> I have attached a patch file which adds the null check.


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