[JBoss JIRA] (RF-12978) collapsibleSubTable ignores rowClasses
by Edward I (JIRA)
[ https://issues.jboss.org/browse/RF-12978?page=com.atlassian.jira.plugin.s... ]
Edward I updated RF-12978:
--------------------------
Description:
The rowClasses is ignored in the following:
{code:xml}
<rich:collapsibleSubTable value="#{item.items}" var="comp" rowClasses="oddRow, evenRow">
{code}
DataTable works correctly with the same rowClasses.
was:
The rowClasses is ignored in the following:
> collapsibleSubTable ignores rowClasses
> --------------------------------------
>
> Key: RF-12978
> URL: https://issues.jboss.org/browse/RF-12978
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component
> Affects Versions: 4.3.1
> Environment: Firefox 20.0, Linux
> Reporter: Edward I
>
> The rowClasses is ignored in the following:
> {code:xml}
> <rich:collapsibleSubTable value="#{item.items}" var="comp" rowClasses="oddRow, evenRow">
> {code}
> DataTable works correctly with the same rowClasses.
--
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, 10 months
[JBoss JIRA] (RF-12977) a4j:queue breaks tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12977?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12977:
-------------------------------
Affects Version/s: 4.3.2
> a4j:queue breaks tabPanel
> -------------------------
>
> Key: RF-12977
> URL: https://issues.jboss.org/browse/RF-12977
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.2
> Environment: This happens in RF 4.3.2.CR1, but I can't select such version in JIRA.
> Reporter: Bernard Labno
> Priority: Critical
>
> There is clearly a bug in tabPanel.js
> {code}
> execAjax : function (oldPanel, newPanel) {
> var options = $.extend({}, newPanel.getTogglePanel().options["ajax"], {});
> this.__setActiveItem(newPanel);
> rf.ajax(newPanel.id, null, options);
> if (oldPanel) { // HERE IS THE BUG
> this.__setActiveItem(oldPanel);
> }
> return false;
> },
> {code}
> If the tab panel works in ajax mode and we attach a4j:queue with requestDelay="1000" then rf.ajax... will just add request to queue, but meanwhile the active item will be changed to old value.
--
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, 10 months
[JBoss JIRA] (RF-12977) a4j:queue breaks tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12977?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12977:
-------------------------------
Fix Version/s: 5-Tracking
> a4j:queue breaks tabPanel
> -------------------------
>
> Key: RF-12977
> URL: https://issues.jboss.org/browse/RF-12977
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.2
> Environment: This happens in RF 4.3.2.CR1, but I can't select such version in JIRA.
> Reporter: Bernard Labno
> Priority: Critical
> Fix For: 5-Tracking
>
>
> There is clearly a bug in tabPanel.js
> {code}
> execAjax : function (oldPanel, newPanel) {
> var options = $.extend({}, newPanel.getTogglePanel().options["ajax"], {});
> this.__setActiveItem(newPanel);
> rf.ajax(newPanel.id, null, options);
> if (oldPanel) { // HERE IS THE BUG
> this.__setActiveItem(oldPanel);
> }
> return false;
> },
> {code}
> If the tab panel works in ajax mode and we attach a4j:queue with requestDelay="1000" then rf.ajax... will just add request to queue, but meanwhile the active item will be changed to old value.
--
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, 10 months
[JBoss JIRA] (RF-12976) rich:tabPanel using @binding: switching tabs invokes itemChangeListener multiple times
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12976?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12976:
------------------------------------
>From a comment on a similar issue ([JAVASERVERFACES-2740|https://java.net/jira/browse/JAVASERVERFACES-2740]), [~edburns] says:
{quote}
It is strongly recommended that application developers place managed
beans that are pointed at by component binding expressions in
“request” scope, and not any other scope. This is because placing it
in session or application scope would require thread safety, since
UIComponent instances depends on running inside of a single
thread. There are also potentially negative impacts on memory
management when placing a component binding in “session” or “view”
scopes.
{quote}
> rich:tabPanel using @binding: switching tabs invokes itemChangeListener multiple times
> --------------------------------------------------------------------------------------
>
> Key: RF-12976
> URL: https://issues.jboss.org/browse/RF-12976
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.2
> Environment: Apache Tomcat 7.0.34
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0, IE9, IE10, Chrome 24
> Metamer 4.3.2.20130510-Final
> Reporter: Jiří Štefek
> Labels: regression
> Fix For: 4.3.2
>
> Attachments: TabPanelBindingTest-4.3.0.Final.war
>
>
> Regression against RichFaces 4.3.1.Final. (not working in 4.3.2.CR1|Final)
> See steps to reproduce.
--
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, 10 months