You can make it accept enter by adding
searchWhenChanged="true" to the input line. Two examples for you -- the first a text input and the second a timepicker (so you don't have to submit, just change the time and the search runs):
<input type="text" token="UCInetID" searchWhenChanged="true"/>
<input type="time" searchWhenChanged="true"> <default>Last 4 hours</default> </input>
On the text input, hitting return will cause the search to run.
I just ran across an old input form which did not allow to execute on a text input. I made the change I mentioned above and it works great. If you tried this and it worked for you, please vote this up.
The UX is a lot better if the user, after having changed some search text in a text input can simply press ENTER without having to click "Submit". Removing the submit button is not an option where longer running searches are involved.
hi, certainly worth a look.
i do have forms where there is a text inputfield and a time range picker... the searches are costly since it involves several dbx backends and several costly ldap queries (realtime) so i am not sure if it is a good workarround. I really would like to have the form.submit button be the default for pressing enter in a form text field.