[JBoss JIRA] (RF-13348) pickList - columnClass attribute behaves differently than in RF4
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13348:
----------------------------------
Now I can see that it is similar to
https://github.com/richwidgets/richwidgets/issues/124
Should be this one closed as it is expected with JSF 2.1 ?
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
> Key: RF-13348
> URL: https://issues.jboss.org/browse/RF-13348
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?
--
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
12 years, 4 months
[JBoss JIRA] (RF-13346) orderingList - maxListHeight & minListHeight need to have set units along with number to work
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.s... ]
Michal Petrov edited comment on RF-13346 at 11/14/13 9:08 AM:
--------------------------------------------------------------
The issue is with jQuery, and it's strange that it's not being handled. The problem is here:
{code}
_setHeightMin: function(height) {
this.selectList.find('.scroll-box').css('min-height', height);
}
{code}
it doesn't work when height is just a number in string form, i.e.
* {{200}} - works
* {{"200px"}} - works
* {{"200"}} - does not work; yet it works for {{height}}
I'm guessing in RichWidgets the value is autocast to number, but in CDK string will remain a string. This will be an issue for every component. I will look for a workaround but I think the easiest way is to keep a list of options for each component and and parse them in the Bridge.
was (Author: michpetrov):
The issue is with jQuery, and it's strange that it's not being handled. The problem is here:
{code}
_setHeightMin: function(height) {
this.selectList.find('.scroll-box').css('min-height', height);
}
{code}
it doesn't work when height is just a number in string form, i.e.
* {{200}} - works
* {{"200px"}} - works
* {{"200"}} - does not work
I'm guessing in RichWidgets the value is autocast to number, but in CDK string will remain a string. This will be an issue for every component. I will look for a workaround but I think the easiest way is to keep a list of options for each component and and parse them in the Bridge.
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13346
> URL: https://issues.jboss.org/browse/RF-13346
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13346) orderingList - maxListHeight & minListHeight need to have set units along with number to work
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13346?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13346:
------------------------------------
The issue is with jQuery, and it's strange that it's not being handled. The problem is here:
{code}
_setHeightMin: function(height) {
this.selectList.find('.scroll-box').css('min-height', height);
}
{code}
it doesn't work when height is just a number in string form, i.e.
* {{200}} - works
* {{"200px"}} - works
* {{"200"}} - does not work
I'm guessing in RichWidgets the value is autocast to number, but in CDK string will remain a string. This will be an issue for every component. I will look for a workaround but I think the easiest way is to keep a list of options for each component and and parse them in the Bridge.
> orderingList - maxListHeight & minListHeight need to have set units along with number to work
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13346
> URL: https://issues.jboss.org/browse/RF-13346
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Jiří Štefek
> Assignee: Michal Petrov
>
> {{pickList}} attributes:
> * {{minListHeight}} and {{maxListHeight}}
> need to have set units along with the number value (e.g. 200px) in order to work correctly.
> In RF4 and in RichWidgets, these attributes can be left without units.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13323) FileUploadEvent listener reset the list value with Viewscope
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13323:
----------------------------------
[~wish79] what version of JSF-API are you using?
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
> Key: RF-13323
> URL: https://issues.jboss.org/browse/RF-13323
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.4
> Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>
> Reporter: Mohammad Weshah
> Assignee: Jiří Štefek
> Labels: rich:fileUpload
> Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();
>
> public void FileUploadlistener(FileUploadEvent event) throws Exception {
> UploadedFile item = event.getUploadedFile();
> UploadedImage file = new UploadedImage();
> file.setLength(item.getData().length);
> file.setName(item.getName());
> file.setData(item.getData());
>
> files.add(file);
> }
> {code}
>
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>
> Regards
> Wish79
--
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
12 years, 4 months
[JBoss JIRA] (RF-13343) Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13343?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13343:
---------------------------------
Brian, we don't need any JSON parsing, that's I'm advocating avoiding JSON library.
The RichFaces component bootstrap is not even strict JSON, so I consider the implementation quite fragile.
> Page Fragments: Re-implement setupFragmentFromWidget() methods using component options access
> ---------------------------------------------------------------------------------------------
>
> Key: RF-13343
> URL: https://issues.jboss.org/browse/RF-13343
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: page-fragments, qe
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> As we have discussed in RF-13335, we have two options available for accessing component options:
> * component uses {{BaseComponent}} (RF4 components)
> {code}
> RichFaces.component("j_idt108").options
> {code}
> * component uses {{jQuery UI Widget Factory}} (RF5 components)
> {code}
> $(document.getElementById("j_idt163:j_idt165Input")).autocomplete("option", "autoFocus")
> {code}
> We can use WebDriver's {{JavascriptExecutor}} to access widget settings.
--
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
12 years, 4 months
[JBoss JIRA] (RF-13327) pickList - setting of multiple attributes does not have any effect on the component
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13327?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13327:
----------------------------------
All other attributes (value change listener as well), are working now.
> pickList - setting of multiple attributes does not have any effect on the component
> -----------------------------------------------------------------------------------
>
> Key: RF-13327
> URL: https://issues.jboss.org/browse/RF-13327
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Setting of these attributes on a {{pickList}} has no effect on the rendered component (I am trying to group them somehow).
> *Buttons text*
> * addAllText
> * addText
> * removeAllText
> * removeText
> * downBottomText
> * downText
> * upText
> * upTopText
> *List style*
> * maxListHeight
> * minListHeight
> * style
> * columnClasses
> *Other RW options*
> * switchByClick
> * switchByDblClick
> *Callbacks*
> * onremoveitems
> * onadditems
> * value
> * valueChangeListener
> I guess that it is because they are not passed in the [renderer template|https://github.com/richfaces/richfaces/blob/master/framework/src...] ?
--
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
12 years, 4 months
[JBoss JIRA] (RF-13323) FileUploadEvent listener reset the list value with Viewscope
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13323:
----------------------------------
[~bleathem], I have found that the issue with MediaOutput, mentioned in [this comment|https://issues.jboss.org/browse/RF-13323?focusedCommentId=1292265...], is already reported here -- [RF-11585|https://issues.jboss.org/browse/RF-11585].
[~wish79], sorry, I still can't reproduce it. Got the same result, which you can see on screenshots.
I've attached another maven project from archetypes with your code.
Could you try it? Just build with maven (_mvn package_) and deploy on container and open http://localhost:8080/RF13323/ .
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
> Key: RF-13323
> URL: https://issues.jboss.org/browse/RF-13323
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.4
> Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>
> Reporter: Mohammad Weshah
> Assignee: Jiří Štefek
> Labels: rich:fileUpload
> Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();
>
> public void FileUploadlistener(FileUploadEvent event) throws Exception {
> UploadedFile item = event.getUploadedFile();
> UploadedImage file = new UploadedImage();
> file.setLength(item.getData().length);
> file.setName(item.getName());
> file.setData(item.getData());
>
> files.add(file);
> }
> {code}
>
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>
> Regards
> Wish79
--
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
12 years, 4 months
[JBoss JIRA] (RF-13323) FileUploadEvent listener reset the list value with Viewscope
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13323?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13323:
----------------------------------
Sorry, just now I've noticed that you have upgraded JSF version of your container. I'll try that with your version.
> FileUploadEvent listener reset the list value with Viewscope
> ------------------------------------------------------------
>
> Key: RF-13323
> URL: https://issues.jboss.org/browse/RF-13323
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.4
> Environment: Jboss 7.1
> Richfaces 4.3.4
> JSF 2.1.9
>
> Reporter: Mohammad Weshah
> Assignee: Jiří Štefek
> Labels: rich:fileUpload
> Attachments: RF-13323-2.zip, RF-13323-SessionScoped.png, RF-13323-ViewScoped.png, RF-13323.zip, TestRichFacesWebProject.rar, TestRichFacesWebProject.war
>
>
> Hello All,
> i make an example of upload file from richfaces showcase it is working successfully , but i notice if i changed the backing bean to viewscope the files list inside the FileUploadEvent listener will be rest every time that i upload new file , the code as follow :
>
> {code}
> protected List<UploadedImage> files = new ArrayList<UploadedImage>();
>
> public void FileUploadlistener(FileUploadEvent event) throws Exception {
> UploadedFile item = event.getUploadedFile();
> UploadedImage file = new UploadedImage();
> file.setLength(item.getData().length);
> file.setName(item.getName());
> file.setData(item.getData());
>
> files.add(file);
> }
> {code}
>
> but when i changed the scope to session the files still contain the old files, is it mandatory to the backing be session or there is something wrong ?
>
> Regards
> Wish79
--
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
12 years, 4 months