On 10/10/13 8:58 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote:
>I get it. > >So I will try to change the code so that it supports both the old >behavior (ie by subclassing) and new behavior (ie by styling). I'm sure some users will be very happy if you do that. You don't have to, you just have to judge how many people will be impacted and whether it will cause them to think poorly of Apache Flex. For example, for the FTETextField issue, we may decide that the FTETextField has always been behaving incorrectly and change the tests and tell folks they'll have to change any code affected by it because they were relying on buggy behavior. We will use performance considerations in that decision because there are often hundreds of FTETextFields on screen at once, whereas SplitViewNavigator probably only has a few. Thanks, Alex
