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

Jim Brown commented on FLEX-34781:
----------------------------------

Alex

My steps 4 and 5 were reversed.
I close the first modal popup immediately after I create and open the 
second modal popup.
They are NOT nested. My mistake.
Selection event (2.5) function makes two consecutive calls: open second 
modal and upon return close first modal.

1. Create a Flex application window
2. open first modal popup
(2.5. select from list to drive operation of second modal popup)
3. open second modal popup
4. close first modal popup
5. close second modal popup
6. main window will still have blur applied to it






> The main window still has blur applied to it after nested modal popups are 
> closed
> ---------------------------------------------------------------------------------
>
>                 Key: FLEX-34781
>                 URL: https://issues.apache.org/jira/browse/FLEX-34781
>             Project: Apache Flex
>          Issue Type: Bug
>    Affects Versions: Apache Flex 4.14.0, Apache Flex 4.15.0
>         Environment: Macintosh OS X 10.9, Flash Builder 4.7, Apache Flex 
> 4.14.0 Nightly build for Feb 28
>            Reporter: Jim Brown
>
> Steps to reproduce:
> 1. Create a Flex application window
> 2. open first modal popup
> 3. open second modal popup (opened by first modal popup)
> 4. close second modal popup
> 5. close first modal popup
> 6. main window will still have blur applied to it
> Actual Results:
> The main window still has blur applied to it. It is not reset when all modal 
> popups are closed.
> Expected Results:
> The main window should not have blur applied after all modal popups are 
> closed.
> Workaround (if any):
> Open and close a modal popup. Blur is removed from main window.
> Notes:
> This worked correctly in 4.13 and earlier releases.
> It is definitely broken in 4.14.0 and 4.14.0 Nightly build Feb 28.
> I have not tried more recent builds.
> No obvious open bugs for this problem.



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

Reply via email to