[JBoss JIRA] (RF-12733) Metamer: rich:treeToggleListener: unable expand tree in second level [myFaces]
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12733?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12733:
-------------------------------
Fix Version/s: 5-Tracking
> Metamer: rich:treeToggleListener: unable expand tree in second level [myFaces]
> ------------------------------------------------------------------------------
>
> Key: RF-12733
> URL: https://issues.jboss.org/browse/RF-12733
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tree
> Affects Versions: 4.3.0.CR1
> Environment: RichFaces 4.3.0.CR1
> Metamer 4.3.0.20130114-CR1
> Weld Servlet (Uber Jar) 20120106-1159
> Apache Tomcat 7.0.32
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 17.0 @ Linux i686
> Metamer:
> 2023898d4b163a889955c1d028149a31 metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war
> Reporter: Ján Jamrich
> Labels: myfaces
> Fix For: 5-Tracking
>
> Attachments: metamer-treeToggleListener-expand-2nd-level-tree-problem.png
>
>
> Cannot expand second level in tree in rich:treeToggleListener demo.
> Getting Error status instead.
> See screenshot for more info.
--
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, 11 months
[JBoss JIRA] (RF-12728) rich:fileUpload doesn't accept valid file after its unsuccessful multiple upload
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12728?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12728:
-------------------------------
Fix Version/s: 4.3.0.Final
> rich:fileUpload doesn't accept valid file after its unsuccessful multiple upload
> --------------------------------------------------------------------------------
>
> Key: RF-12728
> URL: https://issues.jboss.org/browse/RF-12728
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.0.CR1
> Environment: RichFaces 4.3.0.CR1
> Metamer 4.3.0.20130114-CR1
> Weld Servlet (Uber Jar) 20120106-1159
> Apache Tomcat 7.0.34
> Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux
> Firefox 16.0 @ Linux x86_64
> RichFaces 4.3.0.CR1
> Metamer 4.3.0.20130114-CR1
> JBoss Application Server: Weld Integration 7.1.1.Final
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux
> Firefox 16.0 @ Linux x86_64
> Reporter: Jan Papousek
> Labels: regression
> Fix For: 4.3.0.Final
>
> Attachments: to_upload.png
>
>
> Using 4.3.0.M3 I've successfuly uploaded 3 files from the attachment in one time.
--
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, 11 months
[JBoss JIRA] (RF-12720) mobile showcase and android: rich:list and a4j:param demos do not not work properly
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12720?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12720:
-------------------------------
Summary: mobile showcase and android: rich:list and a4j:param demos do not not work properly (was: mobile showcase and android: rich:list and a4j:param demos: do not not work properly)
> mobile showcase and android: rich:list and a4j:param demos do not not work properly
> -----------------------------------------------------------------------------------
>
> Key: RF-12720
> URL: https://issues.jboss.org/browse/RF-12720
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core, mobile, showcase
> Affects Versions: 4.3.0.M3, 4.3.0.CR1
> Environment: Apache Tomcat 7.0.32
> richfaces-showcase-4.3.0.CR1-myfaces.war
> Motorola Xoom (Android 4.0.3) -- browser Safari
> Reporter: Jiří Štefek
>
> See the steps to reproduce.
> There are no problems on iPad (iOS 5.1.1).
> Also not worked in 4.3.0.M3.
--
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, 11 months