Many thick client controls have the same properties. The usual debate/answer that I find is this:
1) if the control should never be edited, mark it as read-only 2) if the control is temporarily disabled (i.e. you need to select a radio button to enable the associated controls), then use disabled. In general, a read-only controls is something to display data, not a form control for submitting data. Since radio buttons and check boxes are rarely ever used for display only, then it may make sense that they do not support a read-only state. My $0.02 -Andrew On 12/7/05, Bobby Rosenberger <[EMAIL PROTECTED]> wrote: > Hello, > > Can someone help me make a distinction between the disabled and readonly > tags? After some testing I've come to the conclusion that the only real > difference is that the 'readonly' attrib will disable an input field without > affecting its visual properties, whereas the 'disabled' attrib (a > pass-through attrib) WILL affect the visual props. > > Interestingly, the 'readonly' attrib seems to have no affect on several of > the tags I tested with (ie. selectBooleanCheckbox, selectOneMenu, etc) > > Any further clarification would be great. I'm trying to determine the > appropriate place to use these tags. > > Thanks, > > Bobby > >
