> But as a general (high level) idea, what do you think on keep the required > attribute, but this time as a shortcut for a new NotEmptyValidator opt. > attached to input elements)
This would only work if all form fields were guaranteed to be TextInputs, which they are not. There is no way to generically ensure that a "required" field has a value, because there is no API in Component such as "hasValue():boolean" (nor do I think there should be). My opinion is that the "required" property should be eliminated. Even if support were added to TerraFormSkin to paint a "required" state, the flag is still likely to cause confusion, since it implies that Form will execute some validation logic (which it doesn't). The definition of "required" is simply too application-specific. G
