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

Justin Mclean resolved FLEX-22865.
----------------------------------

       Resolution: Fixed
    Fix Version/s: Apache Flex 4.10.0

Fixed and checked into develop branch.
                
> Changing a DateChooser's displayedMonth to X and then immediately changing it 
> back results in it showing month X instead of the original month
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-22865
>                 URL: https://issues.apache.org/jira/browse/FLEX-22865
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: mx: DateChooser
>    Affects Versions: Adobe Flex SDK 3.5 (Release)
>         Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Browser: Firefox 3.x
> Language Found: English
>            Reporter: Adobe JIRA
>             Fix For: Apache Flex 4.10.0
>
>
> Steps to reproduce:
> 1. Set a DateChooser's "displayedMonth" property to something other than its 
> current value.
> 2. Immediately afterward set the DateChooser's "displayedMonth" back to its 
> original value.
>  
>  Actual Results:
> The month displayed on the DateChooser is the intermediate value.
>  
>  
>  Expected Results:
> The month displayed on the DateChooser should be it's original value.
>  
>  
>  Workaround (if any):
>  Monkeypatch! Okay, there are probably other ways of working around it, but 
> that's how I did it.
> Additional Information
>  See attached file. It's an extremely simple example.
> I believe the problem lies in CalendarLayout's "set displayedMonth" function. 
> It checks the new value against "_displayedMonth" but I believe it should 
> check the new value against "displayedMonth" (no underscore) or possibly 
> "_proposedDisplayedMonth".

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

Reply via email to