Therefore, as many as possible of the built-in input types should have support for a default value. I know that in Enonic CMS 4.7 this is possible with the text input (and implicitly also the dropdown input), but that’s not enough!
There are only positive consequences that result from this feature. Users get more happy because they don’t always need to fill out required fields, developers get a cleaner way to provide fallback values, and there is less need to rely on using help texts to give instructions.
This feature request is not for any current business-critical problem, but I’m sure that those will appear quite soon!
Hi…
We’ve discussed this - default values make more sense for some inputs than other - i.e. dropdowns or dates - any comments on what is most critical here?
The rest of the current InputTypes are “Nice to have” default values for. For example, I know that there have been feature requests for default values in TextArea and HtmlArea for CMS 4.7, so it can be expected that people will ask for this in XP as well, at some point.
Not really sure if it makes any sense to have a default value for that… there’s no “selected” attribute in the HTML5 spec for ‘datalist’ like there is for the ‘select’ element.
We absolutely need a default for ComboBox. I’m using ComboBox for things like default theme: light-dark and you have to pick one. That’s a bad example because with only two options, might as well use radiobuttons. But there are others where you want a dropdown to save space but you also want it required and it has an obvious “most likely” option.
