>Well, we can close it as 'works as designed', I think ? Adobe used to have >formal specs for how these controls were meant to respond in various states, >and I >expect there are tests that check the control meets them. OK
You'd be able to get the disable on max/min behaviour with a custom skin and subclass of the component, I think ? > I don't know. Maurice -----Message d'origine----- De : Tom Chiverton [mailto:t...@extravision.com] Envoyé : jeudi 9 janvier 2014 15:49 À : dev@flex.apache.org Objet : Re: Easy test/ Easy fix bugs Well, we can close it as 'works as designed', I think ? Adobe used to have formal specs for how these controls were meant to respond in various states, and I expect there are tests that check the control meets them. You'd be able to get the disable on max/min behaviour with a custom skin and subclass of the component, I think ? Tom On 09/01/2014 14:31, Maurice Amsellem wrote: > Tom, what do you think about closing the ticket? > > If it's an issue, then someone can reopen it. > > Maurice > > -----Message d'origine----- > De : piotr.zarzycki [mailto:piotrzarzyck...@gmail.com] > Envoyé : jeudi 9 janvier 2014 15:23 > À : dev@flex.apache.org > Objet : RE: Easy test/ Easy fix bugs > > I think same. Maybe this ticket could be close. > > > > ----- > Flex/Air developer open to new job offers and challenges. > piotrzarzyck...@gmail.com > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/Easy-test-Easy-fix-bugs-tp33347p33843.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > >
