Hi Mike,
Now that Roger has confirmed that we can fix in the RI, we don't
have a "disabledClass" on select tag and we only have it on options. So
our fix would be to render "disabled" on select if the attribute is
specified. Does that make sense ?
Thanks
-Jayashri.
Roger Kitain wrote:
> I think since "disabled" is already an attribute on the component itself
> the patch can be applied to the renderer accordingly.
>
> -roger
>
> Jayashri Visvanathan wrote:
>
>> Hi Mike,
>> I looked at the Std. HTML Renderkit docs and it doesn't mention
>> anything specifically about how "disabled" should be handled with
>> respect to options. That said, this sounds like a bug to me. If the
>> component is "disabled", shouldn't we render "disabled" on select
>> element, applying the disabledClass in addition to disabling the
>> options that are disabled.
>> Roger, does the Spec need to clarify this or can we just fix this in
>> the RI ?
>> Thanks
>> -Jayashri
>>
>> Michael Youngstrom wrote:
>>
>>> I'm using a selectManyListbox. When I disable the component only
>>> the options get the disabledClass applied to them. This is fine
>>> except if the listBox is empty then it doesn't look disabled. I
>>> think it would be nice to applying disabledClass to the select
>>> element as well as the options for selectManyListbox and maybe the
>>> other select components. What do you think? I could probably
>>> create and issue and a patch however I'm not sure what kind of spec
>>> implications it has.
>>>
>>> Mike
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
>> For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
> For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net
>