[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12802:
----------------------------
Assignee: (was: Lukáš Fryč)
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.M1
> Reporter: Pavol Pitonak
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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
11 years, 7 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak updated RF-12802:
-------------------------------
Description:
As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
was:As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> Move page fragments from repository qa to richfaces5
> ----------------------------------------------------
>
> Key: RF-12802
> URL: https://issues.jboss.org/browse/RF-12802
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Affects Versions: 5.0.0.M1
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
>
> As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
> We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations.
--
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
11 years, 7 months
[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-12802:
----------------------------------
Summary: Move page fragments from repository qa to richfaces5
Key: RF-12802
URL: https://issues.jboss.org/browse/RF-12802
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build/distribution
Affects Versions: 5.0.0.M1
Reporter: Pavol Pitonak
Assignee: Lukáš Fryč
As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework.
--
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
11 years, 7 months
[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-12768:
----------------------------
Summary: Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18 (was: Metamer: rich:tabPanel: Tabs are not clickable and can't be removed)
> Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18
> ---------------------------------------------------------------------------------
>
> Key: RF-12768
> URL: https://issues.jboss.org/browse/RF-12768
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final
> Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1
> Reporter: Petr Mensik
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed.
--
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
11 years, 7 months
[JBoss JIRA] (RF-12759) rich:hotkey doesn't handle Ctrl+A key binding
by Edilmar Alves (JIRA)
[ https://issues.jboss.org/browse/RF-12759?page=com.atlassian.jira.plugin.s... ]
Edilmar Alves commented on RF-12759:
------------------------------------
Firefox16/17/18, Chrome 14/15/16/17/18.
Same behaviour.
> rich:hotkey doesn't handle Ctrl+A key binding
> ---------------------------------------------
>
> Key: RF-12759
> URL: https://issues.jboss.org/browse/RF-12759
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.2.3.Final
> Environment: Linux Fedora 16 x64, NetBeans 7.2, GlassFish 3.1.1, CDI/Weld/CODI, JSF2, RichFaces4.2.3, Hibernate3.2.5, Firebird 2.5.1
> Reporter: Edilmar Alves
> Assignee: Lukáš Fryč
> Labels: hotkey, waiting_on_user
> Attachments: test.java, test.xhtml
>
>
> When I try to use rich:hotkey with a4j:commandButton, it doesn't work. A detailed explanation about this is in the forum.
--
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
11 years, 7 months
[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12768:
---------------------------------
Juraj, the tabs are clickable and can be removed with {{4.3.1-SNAPSHOT}} using Firefox 18.0.
> Metamer: rich:tabPanel: Tabs are not clickable and can't be removed
> -------------------------------------------------------------------
>
> Key: RF-12768
> URL: https://issues.jboss.org/browse/RF-12768
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final
> Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1
> Reporter: Petr Mensik
> Assignee: Lukáš Fryč
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed.
--
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
11 years, 7 months
[JBoss JIRA] (RF-12577) rich:select - can't select different value after deleting the old one
by Alex Andreenko (JIRA)
[ https://issues.jboss.org/browse/RF-12577?page=com.atlassian.jira.plugin.s... ]
Alex Andreenko edited comment on RF-12577 at 2/19/13 7:12 AM:
--------------------------------------------------------------
I can't believe that RF 4.3 was released with this high bug.
The component is completely ruined...
was (Author: angrymb):
I can't believe that RF 4.3 with this bug.
The component is completely ruined...
> rich:select - can't select different value after deleting the old one
> ---------------------------------------------------------------------
>
> Key: RF-12577
> URL: https://issues.jboss.org/browse/RF-12577
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.0.M2
> Environment: RichFaces 4.3.0.20121024-M2
> Metamer 4.3.0.20121024-M2
> Weld Servlet (Uber Jar) 20120106-1159
> Apache Tomcat 7.0.32
> Java(TM) SE Runtime Environment 1.7.0_07-b10 @ Linux
> Firefox 16.0 @ Linux x86_64
> RichFaces 4.3.0.20121024-M2
> Metamer 4.3.0.20121024-M2
> JBoss Application Server: Weld Integration 7.1.1.Final
> JBoss AS 7.1.1.Final
> Java(TM) SE Runtime Environment 1.7.0_07-b10 @ Linux
> Firefox 16.0 @ Linux x86_64
> Reporter: Jan Papousek
> Fix For: 5-Tracking
>
>
--
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
11 years, 7 months