I'm using Flex 3.5 with Adobe Flex Builder 3. I have found that if you very rapidly click between multiple headers of an accordion component or the tabs of TabNavigator, these components will begin to exhibit odd, unexpected behavior. Once this behavior has been evoked, even trying to set the selectedIndex programmatically does not end in the desired result. Specifically, if set the selectedIndex to zero (or click on the first tab/header) it might temporarily hop to that index but then will finish on a different index.

Has anyone else experienced this behavior and do you know of a patch that can prevent the user from getting in a situation where the tab/header they click on is not the one made visible?