Oh, you are right. I just thought that I have seen a disabled option in an optiongroup somewhere.. maybe that was some javascript magic.
On 12/17/05, Patrick Casey <[EMAIL PROTECTED]> wrote: > > Does the html spec even allow you to selectively disable one option > in an optiongroup? My copy of the spec seems to imply that its supposed to > inherit the disabled property from its containing <Select> rather than each > <option> havning its own private disabled flag. > > <!ELEMENT OPTION - O (#PCDATA) -- selectable choice --> > <!ATTLIST OPTION > %attrs; -- %coreattrs, %i18n, %events -- > selected (selected) #IMPLIED > disabled (disabled) #IMPLIED -- unavailable in this context -- > label %Text; #IMPLIED -- for use in hierarchical menus -- > value CDATA #IMPLIED -- defaults to element content -- > > > > Note the "unavailable in this context" description of disabled. > > --- Pat > > > -----Original Message----- > > From: Ted Steen [mailto:[EMAIL PROTECTED] > > Sent: Saturday, December 17, 2005 3:16 AM > > To: Tapestry users > > Subject: disable an element in a propertyselection. > > > > I can't find a way to disable a single element in a propertyselection. > > I was hoping to find an isEnabled() method on the > > PropertySelectionModel > > am I missing something here? > > -- > > /ted > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- /ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
