AW: disabled .vs readonly

PROTECTED] [mailto:[EMAIL PROTECTED]Im Auftrag von Yee CNGesendet: Donnerstag, 8. Dezember 2005 03:56An: 'MyFaces Discussion'Betreff: RE: disabled .vs readonly I believe that the real issue is that HTML check boxes and radio buttons dont know about the readonly attribute. So you ca

FW: disabled .vs readonly

] Subject: AW: disabled .vs readonly Hi! I would like to give you a hint to the displayValueOnly attribute, which exists for the selectOneRadio tag, for example. It might be an alternative for the readonly attribute in some contexts. Regards, Matthias

disabled .vs readonly

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

Re: disabled .vs readonly

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.

Re: disabled .vs readonly

Comments below:On 12/7/05, Andrew Robinson [EMAIL PROTECTED] wrote: Many thick client controls have the same properties. The usualdebate/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

RE: disabled .vs readonly

December 2005 3:01 AM To: MyFaces Discussion Subject: Re: disabled .vs readonly Comments below: On 12/7/05, Andrew Robinson [EMAIL PROTECTED] wrote: 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