[jira] [Resolved] (FLEX-33156) focusInHandler() in spark Scroller doesn't null check focusManager property before using

["Carol Frampton (JIRA)" <ji...@apache.org>]

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

Carol Frampton resolved FLEX-33156.
-----------------------------------

    Resolution: Fixed

Author: cframpton
Date: Tue Dec  4 15:30:50 2012
New Revision: 1416993

URL: http://svn.apache.org/viewvc?rev=1416993&view=rev
Log:
Fix RTE in focusInHandler when focusManager is null.

Modified:
    incubator/flex/sdk/branches/develop/frameworks/projects/spark/src/spark/components/Scroller.as

                
> 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 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