This content has been marked as final. Show 3 replies
This was a bug in the Flex 2 release. It has been fixed in internal builds and will be included in the next public drop of Flex, which will be soon.
As a workaround, you can remove the NumberValidator.isRealValue() method and your validator will validate correctly. NumberValidator.isRealValue() was adding an unnecessary isNaN check that caused the bug.
Thanks for your reply, i wonder if this bug happens on other validator subclasses.
You said that as a workaround i should remove a method, but what you mean by remove? extend the component, override the method and have an empty implementation? Or do you mean to modifiy the flex original source code to remove this?
Thanks again for the quick reply
You can hack the original source code, but the better way would be to extend NumberValidator and override the isRealValue() method to do exactly the logic in Validator.isRealValue().