May 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12980) Resource Optimizer: doesn't compile JS/CSS files when build executed from top-level directory

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12980?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12980: ---------------------------- Original Estimate: 1 hour Remaining Estimate: 1 hour > Resource Optimizer: doesn't compile JS/CSS files when build executed from top-level directory > --------------------------------------------------------------------------------------------- > > Key: RF-12980 > URL: https://issues.jboss.org/browse/RF-12980 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.Alpha1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12980) Resource Optimizer: doesn't compile JS/CSS files when build executed from top-level directory

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12980: ------------------------------- Summary: Resource Optimizer: doesn't compile JS/CSS files when build executed from top-level directory Key: RF-12980 URL: https://issues.jboss.org/browse/RF-12980 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 5.0.0.Alpha1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Critical Fix For: 5.0.0.Alpha1 -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12943) ExtendedDataTable: filterType custom and clearing of filter input doesnt work correctly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12943?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12943: ------------------------------- Fix Version/s: 4.3.3 > ExtendedDataTable: filterType custom and clearing of filter input doesnt work correctly > --------------------------------------------------------------------------------------- > > Key: RF-12943 > URL: https://issues.jboss.org/browse/RF-12943 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.1 > Environment: Tomcat 7, Mojarra 2.1.21 > Reporter: dako ak > Labels: testcase_provided > Fix For: 4.3.3, 5-Tracking > > Attachments: JSF2-RichFaces-Test.zip > > > According to my appended test project: > I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. The filterType attribute with value "custom" is ignored because the default input text is rendered too. > The second problem with the input filter is that I can't clear this filter input text components by a a4j:commandButton. The table is correct filtered but the filter input text fields are not cleared. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12943) ExtendedDataTable: filterType custom and clearing of filter input doesnt work correctly

by Pere Palou (JIRA)

[ https://issues.jboss.org/browse/RF-12943?page=com.atlassian.jira.plugin.s... ] Pere Palou commented on RF-12943: --------------------------------- I have the same problem, I'm using RF 4.3.2.CR1 > ExtendedDataTable: filterType custom and clearing of filter input doesnt work correctly > --------------------------------------------------------------------------------------- > > Key: RF-12943 > URL: https://issues.jboss.org/browse/RF-12943 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.1 > Environment: Tomcat 7, Mojarra 2.1.21 > Reporter: dako ak > Labels: testcase_provided > Fix For: 5-Tracking > > Attachments: JSF2-RichFaces-Test.zip > > > According to my appended test project: > I have a simple extendedDataTable with one column (firstName) with a filter input component within the header. This is the default filter input created by the extendedDataTable. The second column (city) has a filterType="custom" and an inputText componenent within the header. The filterType attribute with value "custom" is ignored because the default input text is rendered too. > The second problem with the input filter is that I can't clear this filter input text components by a a4j:commandButton. The table is correct filtered but the filter input text fields are not cleared. -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12979) rich:contextMenu inside rich:accordion displays incorrectly

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12979?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated RF-12979: ------------------------------ Attachment: rich_contextMenu.png > rich:contextMenu inside rich:accordion displays incorrectly > ----------------------------------------------------------- > > Key: RF-12979 > URL: https://issues.jboss.org/browse/RF-12979 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.1 > Reporter: Jan Papousek > Attachments: rich_contextMenu.png > > -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12979) rich:contextMenu inside rich:accordion displays incorrectly

by Jan Papousek (JIRA)

Jan Papousek created RF-12979: --------------------------------- Summary: rich:contextMenu inside rich:accordion displays incorrectly Key: RF-12979 URL: https://issues.jboss.org/browse/RF-12979 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.3.1 Reporter: Jan Papousek -- 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

1
0
0 / 0

[JBoss JIRA] (RF-12977) a4j:queue breaks tabPanel

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/RF-12977?page=com.atlassian.jira.plugin.s... ] Bernard Labno updated RF-12977: ------------------------------- Workaround Description: Usually you will not attach a4j:queue to the panel, but to a form or create global queue. If this is the case, then as a workaround you an add <a4j:attachQueue requestDelay="0"/> to tabPanel. > 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

1
0
0 / 0

[JBoss JIRA] (RF-12965) Graph validator's behavior changed in Mojarra 2.1.18

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12965?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12965 at 5/14/13 1:52 AM: ---------------------------------------------------------- We can't reproduce the issue on a minimal sample in framework tests (to be committed to {{richfaces5}} repo). The behavior we can reproduce on a minimal sample is same as in 2.1.17 and 2.1.21 - it means "the validation error for regular bean validation isn't shown when group is selected in graph validator". This behavior is consistent with what you can see in Metamer in 2.1.21. We don't know why it behaved differently in Metamer with Mojarra 2.1.17 yet. After discussion with Brian and Pavol we don't consider that priority to investigate this in scope of {{4.3.2}}. I'm shifting this issue to {{5.0}}. QE: if you will be able to find limited case where this issue happens, we can fix it. was (Author: lfryc): We can't reproduce the issue on a minimal sample in framework tests (to be committed to {{richfaces5}} repo). The behavior we can reproduced on minimal sample is same in 2.1.17 and 2.1.21 - it means "the validation error for regular bean validation isn't shown when group is selected in graph validator". This behavior is consistent with what you can see in Metamer in 2.1.21. We don't know why it behaved differently in Metamer with Mojarra 2.1.17 yet. After discussion with Brian and Pavol we don't consider that priority to investigate this in scope of {{4.3.2}}. I'm shifting this issue to {{5.0}}. QE: if you will be able to find limited case where this issue happens, we can fix it. > Graph validator's behavior changed in Mojarra 2.1.18 > ---------------------------------------------------- > > Key: RF-12965 > URL: https://issues.jboss.org/browse/RF-12965 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-validators > Affects Versions: 4.3.2 > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 4.3.2-SNAPSHOT > works in Mojarra 2.1.17 and 2.1.7, broken in 2.1.18 to 2.1.21 > Apache Tomcat 7.0.35 > OpenJDK Runtime Environment 1.7.0_19-mockbuild_2013_04_19_20_08-b00 @ Linux > Chrome 26.0.1410.63 @ Linux x86_64, Firefox 20 > Reporter: Pavol Pitonak > Fix For: 5-Tracking > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > with Mojarra 2.1.17 and older: > # deploy Metamer to Tomcat and open http://localhost:8080/metamer/faces/components/richGraphValidator/all.xhtml > # set groups attribute to "ValidationGroupBooleanInputs" > # uncheck "Select Boolean Checkbox" > # click "Apply changes", *result: message "may not be empty" next to "Input Secret"* > # type ":-)" to input secret > # click "Apply changes", *result: message "Select Boolean Checkbox isn't checked!" at the top of form* > # check the checkbox > # click "Apply changes", *result: message "Action successfully done!" > with Mojarra 2.1.18 and newer: > # deploy Metamer to Tomcat and open http://localhost:8080/metamer/faces/components/richGraphValidator/all.xhtml > # set groups attribute to "ValidationGroupBooleanInputs" > # uncheck "Select Boolean Checkbox" > # click "Apply changes", *result: message "Select Boolean Checkbox isn't checked!" at the top of form* > # check the checkbox > # click "Apply changes", *result: message "Action successfully done!" > # *input secret isn't validated at all, the same can be reproduced with calendar, inplace input, input textarea, select many checkbox* -- 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

1
0
0 / 0

[JBoss JIRA] (RF-10715) collapsibleSubTable ignores attribute expanded=false

by Edward I (JIRA)

[ https://issues.jboss.org/browse/RF-10715?page=com.atlassian.jira.plugin.s... ] Edward I commented on RF-10715: ------------------------------- >From your screen shot, it seems that rowClasses is also not working. > collapsibleSubTable ignores attribute expanded=false > ---------------------------------------------------- > > Key: RF-10715 > URL: https://issues.jboss.org/browse/RF-10715 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.0.0.CR1 > Reporter: Juergen Zimmermann > Assignee: Nick Belaevski > Priority: Minor > Fix For: 5-Future > > Attachments: screenshot-expand-false-ignored.jpg > > > Although expanded=false is set for rich:collapsibleSubTable, it has no effect. The collapsibleSubTable is used inside a tab nested in a popup. I'll attach a screenshot. -- 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

1
0
0 / 0

[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: > 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: -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2013