[JBoss JIRA] (RF-13574) Editor readonly mode
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13574?page=com.atlassian.jira.plugin.s... ]
Matej Novotny updated RF-13574:
-------------------------------
Description:
With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer.
I checked the attributes editor should have, the bean where via which it is controlled and found no problems there.
I also tried creating editor with readonly='true' which does not work either.
One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere.
There is a test prepared for this: [testReadonly()|https://github.com/richfaces/richfaces-qa/blob/master/meta...]
was:
With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer.
I checked the attributes editor should have, the bean where via which it is controlled and found no problems there.
I also tried creating editor with readonly='true' which does not work either.
One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere.
There is a test prepared for this: [testToolbar()|https://github.com/richfaces/richfaces-qa/blob/master/metam...]
> Editor readonly mode
> --------------------
>
> Key: RF-13574
> URL: https://issues.jboss.org/browse/RF-13574
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 5.0.0.Alpha4
> Environment: Wildfly, Firefox, Metamer (master branch)
> Reporter: Matej Novotny
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha4
>
>
> With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer.
> I checked the attributes editor should have, the bean where via which it is controlled and found no problems there.
> I also tried creating editor with readonly='true' which does not work either.
> One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere.
> There is a test prepared for this: [testReadonly()|https://github.com/richfaces/richfaces-qa/blob/master/meta...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13574) Editor readonly mode
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13574?page=com.atlassian.jira.plugin.s... ]
Matej Novotny edited comment on RF-13574 at 3/18/14 8:47 AM:
-------------------------------------------------------------
Thanks for explanation [~lfryc]!
I saw the test results in Jenkins and modified few tests accordingly.
The problem persists though - I tried to deploy components-demo and even there I am unable to change editor to readOnly mode just via attributes.
In components-demo there is the same approach creating editor with attribute readonly (only the value is taken from the bean) as in Metamer example:
{code}
<r:editor readonly='true/false' id='whatever' ..../>
{code}
Try as I might, this way I cannot accomplish setting it readOnly - the editor stays the same for me.
was (Author: manovotn):
Thanks for explanation [~lfryc]!
I saw the test results in Jenkins and modified few tests accordingly.
The problem persists though - I tried to deploy components-demo and even there I am unable to change editor to readOnly mode just via attributes.
In components-demo there is the same approach creating editor with attribute readonly (only the value is taken from the bean) as in Metamer example:
{code}
<r:editor readonly='true/false' id='whatever' ..../>
{code}
Try as I might, this way I cannot accomplish setting it readOnly - the editor stays the same for me.
Furthermore I tried using XPath to locate the element (textarea) which is affected by this attribute. When you attempt to change the attribute textarea has following state:
{code}
<textarea id="form:editorInput" class="rf-ed-inp" onchange="RichFaces.ajax(this,event,{"parameters":{"javax.faces.behavior.event":"change","org.richfaces.ajax.component":"form:editor"} ,"sourceId":this} )" style="width: 100%; height: 200px; visibility: hidden;" readonly="readonly" name="form:editor"/>
{code}
(this was taken from Metamer, the one from components-demo is very similar)
The attribute readonly has value "readonly", which seems rather weird. Could there still be a problem, or am I doing something incorrectly?
> Editor readonly mode
> --------------------
>
> Key: RF-13574
> URL: https://issues.jboss.org/browse/RF-13574
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 5.0.0.Alpha4
> Environment: Wildfly, Firefox, Metamer (master branch)
> Reporter: Matej Novotny
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha4
>
>
> With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer.
> I checked the attributes editor should have, the bean where via which it is controlled and found no problems there.
> I also tried creating editor with readonly='true' which does not work either.
> One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere.
> There is a test prepared for this: [testToolbar()|https://github.com/richfaces/richfaces-qa/blob/master/metam...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13574) Editor readonly mode
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13574?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13574:
------------------------------------
Thanks for explanation [~lfryc]!
I saw the test results in Jenkins and modified few tests accordingly.
The problem persists though - I tried to deploy components-demo and even there I am unable to change editor to readOnly mode just via attributes.
In components-demo there is the same approach creating editor with attribute readonly (only the value is taken from the bean) as in Metamer example:
{code}
<r:editor readonly='true/false' id='whatever' ..../>
{code}
Try as I might, this way I cannot accomplish setting it readOnly - the editor stays the same for me.
Furthermore I tried using XPath to locate the element (textarea) which is affected by this attribute. When you attempt to change the attribute textarea has following state:
{code}
<textarea id="form:editorInput" class="rf-ed-inp" onchange="RichFaces.ajax(this,event,{"parameters":{"javax.faces.behavior.event":"change","org.richfaces.ajax.component":"form:editor"} ,"sourceId":this} )" style="width: 100%; height: 200px; visibility: hidden;" readonly="readonly" name="form:editor"/>
{code}
(this was taken from Metamer, the one from components-demo is very similar)
The attribute readonly has value "readonly", which seems rather weird. Could there still be a problem, or am I doing something incorrectly?
> Editor readonly mode
> --------------------
>
> Key: RF-13574
> URL: https://issues.jboss.org/browse/RF-13574
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 5.0.0.Alpha4
> Environment: Wildfly, Firefox, Metamer (master branch)
> Reporter: Matej Novotny
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha4
>
>
> With the refactored editor I am unable to set readonly mode using attributes (but via JS API it works) in Metamer.
> I checked the attributes editor should have, the bean where via which it is controlled and found no problems there.
> I also tried creating editor with readonly='true' which does not work either.
> One possibility is that the attribute was changed in the reworked component but I cannot seem to find such change anywhere.
> There is a test prepared for this: [testToolbar()|https://github.com/richfaces/richfaces-qa/blob/master/metam...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-12214) Pack plain skin with UI components distribution (the resource plugin needs to be fixed)
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12214?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-12214:
-------------------------------
Labels: (was: needs-qe)
> Pack plain skin with UI components distribution (the resource plugin needs to be fixed)
> ---------------------------------------------------------------------------------------
>
> Key: RF-12214
> URL: https://issues.jboss.org/browse/RF-12214
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.2.1.Final
> Reporter: Nicolas Daniels
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The plain skin is not packed/compresses as other styles, mainly because images generation is failing due to null property values.
> It could be good to have it as well. Beside it, probably that image generation with null value should be handled.
> Of course, any failed image generation should not be referenced in resulting css.
> (Fyi, currently, generating plain skin is working despite the warnings but missing images are still referenced in resulting css. This is not really good for resources optimization ;-))
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (RF-13082) Change the orderingList component to use the new orderingList widget
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13082?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-13082:
-------------------------------
Labels: (was: needs-qe)
> Change the orderingList component to use the new orderingList widget
> --------------------------------------------------------------------
>
> Key: RF-13082
> URL: https://issues.jboss.org/browse/RF-13082
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Attributes to be dropped in the RF5 implementation:
> * disabledClass
> * headerClass
> * itemClass
> * selectItemClass
> * listWidth
> * onlist*
> It is felt that the *Class attributes are redundant. Custom component styling can be achieved with the combination of the CSS class specified by the _styleClass_ attribute, along with the relevant stateful CSS class (_disabled_, _header_, _ui-selectee_, ui-selected_).
> Similarly the width CSS attributes are better set with CSS styles, rather than via facelet attributes.
> We will drop the onlist* event handlers, as there is considerable overlap with their on* counterparts. For instance, are there really use cases that require differentiating between onmouveover and onlistmouseover?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months