May 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12285) collapsible panel: add section about headerCollapsed and headerExpanded facets

by Lance Sloan (JIRA)

Lance Sloan created RF-12285: -------------------------------- Summary: collapsible panel: add section about headerCollapsed and headerExpanded facets Key: RF-12285 URL: https://issues.jboss.org/browse/RF-12285 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: doc, examples Affects Versions: 4.1.0.Final, 4.0.0.Final Reporter: Lance Sloan While attempting to use collapsiblePanels, I found it extremely frustrating that the "header" facet doesn't work for it like it does for most components. After searching, I learned from the forum that the facets to use are "headerCollapsed" and "headerExpanded". There's no mention of that in the documentation. Please update the documentation and examples. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (RF-10989) Reimplement AbstractPanel.getActiveItem() more defensively

by Lukáš Fryč (JIRA)

Reimplement AbstractPanel.getActiveItem() more defensively ---------------------------------------------------------- Key: RF-10989 URL: https://issues.jboss.org/browse/RF-10989 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Final Reporter: Lukáš Fryč Based on the discussions in RF-10951, it will be good to implement AbstractPanel.getActiveItem(), because it will fail each time you remove the active tab. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
11
0 / 0

[JBoss JIRA] (RF-11706) showcase - rich:editor - Auto-saving sample - panel were output is rendered is too small for the picture

by Juraj Huska (Created) (JIRA)

showcase - rich:editor - Auto-saving sample - panel were output is rendered is too small for the picture -------------------------------------------------------------------------------------------------------- Key: RF-11706 URL: https://issues.jboss.org/browse/RF-11706 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, component-output, component-panels-layout-themes, showcase Affects Versions: 4.1.0.CR1 Environment: app: richfaces-showcase-4.1.0.20111111-CR1 container: all browsers: all Reporter: Juraj Huska Attachments: editorOutput.png When I remove all text from editor, in other words when there is less text than the size of the picture, then the *output panel* which should *serves as a container* for the output from the editor is *too small* for the picture. Please see *the attachment*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (RF-1107) Scrollable dataTable. Header scrolled badly on TAB button.

by Ilya Shaikovsky (JIRA)

Scrollable dataTable. Header scrolled badly on TAB button. ---------------------------------------------------------- Key: RF-1107 URL: http://jira.jboss.com/jira/browse/RF-1107 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Environment: FF 2.0.0.6 Reporter: Ilya Shaikovsky Assigned To: Konstantin Mishin Fix For: 3.2.0 Two use-cases failed: "case - 1.png" frozenColCount=0 all the columns with inputs last columns aren't in visible part When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!) "case - 2.png" frozenColCount=2 all the columns with inputs last columns aren't in visible part I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

9
27
0 / 0

[JBoss JIRA] (RF-12059) RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation

by Jean ANDRE (JIRA)

Jean ANDRE created RF-12059: ------------------------------- Summary: RichFaces.ui.Message is not a constructor - Nested Tab Panel - Tab Creation Key: RF-12059 URL: https://issues.jboss.org/browse/RF-12059 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: Websphere 8.0.0.2 - RAD 8 - JSF Mojorra 2.1.6 - Spring 3.0.6 Final - Firefox 10.0.2 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT - RichFaces 4.2.0 Final - Hibernate Validator 4.2.0 Final Reporter: Jean ANDRE Priority: Blocker We got the following error message, just after a tab has been created or during its creation: {code} RichFaces.ui.Message is not a constructor > return new Function("event", handlerCode); richfaces.js.jsf (ligne 481) {code} This bug is linked to RF-11763 and RF-12030 but the error message and the context are not the same. The rich:messages is also involved in this bug, the rich:message is attached to a rich:calendar. Removing the rich:message removes the error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] (RF-12234) Taglib: rich:extendedDataTable missing clientRows attribute

by Jan Papousek (JIRA)

Jan Papousek created RF-12234: --------------------------------- Summary: Taglib: rich:extendedDataTable missing clientRows attribute Key: RF-12234 URL: https://issues.jboss.org/browse/RF-12234 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.2.2.Final Reporter: Jan Papousek Component rich:extendedDataTable is missing clientRows attribute in taglib. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (RF-10569) MyFaces 2.0.X on Tomcat 7 does not property inject managed properties prior to calling @PostConstruct on Beans

by Jay Balunas (JIRA)

MyFaces 2.0.X on Tomcat 7 does not property inject managed properties prior to calling @PostConstruct on Beans -------------------------------------------------------------------------------------------------------------- Key: RF-10569 URL: https://issues.jboss.org/browse/RF-10569 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: third-party Affects Versions: 4.0.0.Milestone6 Environment: MyFaces 2.0.X Tomcat 7 Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 4.0.0.CR1 See https://issues.apache.org/jira/browse/MYFACES-3035 to details. We have several jira's that are all traced back to this issue, and there seems not quick workaround. We are following the issue, and discussing with MyFaces team. For now please be very conscious of this when testing MyFaces on Tomcat 7. If you believe an issue could be related to this please ask or investigate so we don't get overloaded with jiras related to this. Note that to see these issues with the richfaces showcase you must turn on extra logging via the logging.properties file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
2
0 / 0

[JBoss JIRA] (RF-11732) packed.js rendered multiple times using myfaces

by wojtek k (Created) (JIRA)

packed.js rendered multiple times using myfaces ----------------------------------------------- Key: RF-11732 URL: https://issues.jboss.org/browse/RF-11732 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.1.0.CR1 Environment: MyFaces (2.1.1, 2.1.4) Reporter: wojtek k Priority: Critical Fix For: 4.1.0.Final It looks like RichFaces with MyFaces only replace old js (for example richfaces-event.js) with "packed.js" when component need different javascripts. So browser load multiple times packed.js. Rendered Html page: //--></script><script type="text/javascript" src="/test-app/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.20111111-CR1/PackedCompressed/packed/packed.js"></script><script type="text/javascript" src="/test-app/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.20111111-CR1/PackedCompressed/packed/packed.js"></script><script type="text/javascript" src="/test-app/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.20111111-CR1/PackedCompressed/packed/packed.js"></script><script type="text/javascript" src="/test-app/org.richfaces.resources/javax.faces.resource/org.richfaces.staticResource/4.1.0.20111111-CR1/PackedCompressed/packed/packed.js"><!-- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
4
0 / 0

[JBoss JIRA] (RF-11902) [rich:autocomplete] add attribute queueId

by Rene O (JIRA)

Rene O created RF-11902: --------------------------- Summary: [rich:autocomplete] add attribute queueId Key: RF-11902 URL: https://issues.jboss.org/browse/RF-11902 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Final Reporter: Rene O It would be nice if rich:autocomplete has an attribute queueId like a4j:ajax component. With this you will have more control over the ajax requests if ajax mode is enabled within autocomplete component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
11
0 / 0

[JBoss JIRA] (RF-12245) Adding to org.richfaces.model.TreeNodeImpl's map of children whose keys contain whitespace produce invalid JSF IDs

by Karsten Wutzke (JIRA)

Karsten Wutzke created RF-12245: ----------------------------------- Summary: Adding to org.richfaces.model.TreeNodeImpl's map of children whose keys contain whitespace produce invalid JSF IDs Key: RF-12245 URL: https://issues.jboss.org/browse/RF-12245 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Environment: JBoss AS 7.1.1.Final + Mojarra 2.1.7 Reporter: Karsten Wutzke Adding to org.richfaces.model.TreeNodeImpl's map of children whose keys contain whitespace/spaces produce invalid JSF IDs (they break <f:ajax> but not <a4j:ajax> for really strange effects). Generating JSF IDs containing spaces is defined to be invalid. I had asked this in the forum without any answers here: https://community.jboss.org/thread/199142 Also note the original question/example over at SO: http://stackoverflow.com/a/10413232/396732 Also note the answer http://stackoverflow.com/a/10412444/396732 <a4j:ajax> should not really be able to handle these invalid IDs (if you ask me), since the implementation is said to fully based on JSF 2 <f:ajax>, which can't handle the wrong generated IDs. But ultimately that's something for the developer team to figure out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2012