I currently develop some forms in a desktop application. There is the idea to use placeholder texts in some input fields (edits) as known from HTML forms or touch systems like smartphones. But ...
Should a check box field be disabled or removed from an interface if is it not going to be used? [duplicate]
I have a web page set up wizard that guides a user through several steps to create an object. One of the steps in the wizard requires the users to pick via check boxes a property to their object. ...
Is it ok to disable the next button until all of the required fields on a wizard form have been completed? [duplicate]
I'm considering disabling the next and done buttons on my wizard until all of the required fields on the corresponding step have been completed. My first thought is that if something shouldn't be ...
How should an input field appear when it is disabled? One idea is to show 'Disabled' as value within the input field. Is there a better idea to indicate an input text field is disabled? The input box ...
How do you think about disabling the submit-button until the user has completed the form or the required fields? I find similar questions here on ux.se and somebody answered that the user will think ...
We have a list of complicated things, which the user can click on to get a new view in which they can edit all the details stored for that thing. The edit view already has a Cancel exit mechanism ...
We have a few different forms as part of a web-based medical application. These forms have quite a few fields - 10-20 depending on the form. Each has at least 5 or so required fields. We currently ...
Possible Duplicate: Don't hide or disable menu items? On a create/edit form, where the options available to the end user will depend on their previous input, in order to give the user ...
Let say we have a form with 50 or so elements. It is a data entry form and is in the format the user is expecting based on standardized industry paperwork. My question is should required fields ...