Better indication for disabled text fields

Andrew · 2014-05-27 02:36

There are a few text fields controlled by a checkbox, such as the following (there may be more of course):

1) When the checkbox is unchecked if the corresponding text field gets disabled/grayed out then that would look and behave in a more standardized manner IMO.

2) Similarly there are text fields controlled by a radio button (such as the following, just one example) and if the corresponding radio button is not selected it would be nice if the field got disabled:

A side-effect of the non-disabled text fields is that if you try and edit them the corresponding checkbox or radio button immediately becomes checked/selected, which may not be what was intended. It also leads to situations where for example if the checkbox/radio button is not checked/selected and you delete what's in the field, now the checkbox/radio button gets checked/selected even though the field's completely empty! If the field gets disabled these problems will be avoided.

Last edited by Andrew (2014-05-27 02:37)

den4b · 2014-06-04 15:41

It is a common practice to automatically select the corresponding radio button or checkbox when associated text field is being edited.

In my experience it works very well. For example, when you need to add a Delete rule to delete a portion from a certian delimiter, you simple click on the delimiter field and type. I think it is more intuitive than having to click the radio button first to enable the field.

As for the "side-effect", simply don't edit text fields when you don't need to...

den4b Forum

#1 2014-05-27 02:36

Better indication for disabled text fields

#2 2014-06-04 15:41

Re: Better indication for disabled text fields

Board footer