Guten Tag Sven Meier, am Donnerstag, 2. April 2015 um 12:40 schrieben Sie: > What do you mean by 'is not valid'? Whether null is accepted as input > will be decided by #isRequired().
setRequired is called with true as well, but specifying null as valid input to the component is wrong in my case and may have additional side effects in future or whatever. > You can change these texts, see #getNullValidDisplayValue() and > #getNullValidKey() or just change the text for "<id>.nullValid" in your > properties. I don't see the benefit of giving the key nullValid a wording like "null is invalid" instead. Additionally I would even have to remember this behavior for all DropDownChoices in a use case like this one with default value, only one choice needed and null being invalid. From my point of view this is better fixed in the component, at least for HTML5. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: [email protected] AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
