myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leonardo Uribe <lu4...@gmail.com>
Subject Re: Attribute "readonly=true" can be rendered as "readonly=readonly" as before.
Date Thu, 04 Aug 2011 16:01:39 GMT
Hi

Ok, I commit the fix related to rename 'readonly' as 'readOnly'.

So, now readonly="true" will be rendered again for h:commandButton,
h:inputText or h:inputTextarea. For cases like h:selectOneXXX or
h:selectManyXXX, readonly="readonly" is used.

Thanks for the hint.

regards,

Leonardo Uribe

2011/8/4 Ivan <xhhsld@gmail.com>:
> There is a typo error on the line 280 of the code generation
> script componentClass20.vm, the attribute name should 'readonly', not
> 'readOnly', so the configured readOnly value is not kept in
> the commonPropertiesSet.
>
> 2011/8/4 Shawn Jiang <genspring@gmail.com>
>>
>> Hi Devs,
>>
>> Geronimo tck has some regressions on inputtext attribute render cases due
>> to recent myfaces  2.0.8-snapshot changes .     The jsf contain a input text
>> with attribute "readonly=true",  and expect render result is
>> "readonly=readonly" .   But the result is ""  instead of
>> "readonly=readonly"  now.
>>
>> I added a breadpoint in
>> org.apache.myfaces.shared.renderkit.html.HtmlResponseWriterImpl.writeAttribute(String,
>> Object, String)  and found myfaces DOES write the attribute for the
>> component.   But the result html does not contain the attribute somehow.
>>
>> Is there any filter things added to not allow "readonly" attribute to be
>> rendered ?
>>
>> --
>> Shawn
>
>
>
> --
> Ivan
>

Mime
View raw message