February 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-10754) extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear

by Ilya Shaikovsky (JIRA)

extendedDataTable: two or more components placed on the page causes horizontal scroll to disappear -------------------------------------------------------------------------------------------------- Key: RF-10754 URL: https://issues.jboss.org/browse/RF-10754 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky just get any example where table has horizontal scroll and add one more table by copy/paste. (change id's if need) result: scroll disappear. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
14
0 / 0

[JBoss JIRA] (RF-11739) Components that don't require jsf.js can break ResourceMapping

by Brian Leathem (Created) (JIRA)

Components that don't require jsf.js can break ResourceMapping -------------------------------------------------------------- Key: RF-11739 URL: https://issues.jboss.org/browse/RF-11739 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.0.0.CR1 Reporter: Brian Leathem Fix For: 4.2.0.Tracking This bug is only observable when resourceMapping is enabled. If a component doesn't require jsf.js, and it is the first component to require a resource, it will trigger packed.js to redner before jsf.js. This breaks some of the scripts in packed.js, that require jsf.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, 8 months

7
23
0 / 0

[JBoss JIRA] (RF-11544) RichFaces BOM jsf-* dependencies should be fixed

by Karel Piwko (Created) (JIRA)

RichFaces BOM jsf-* dependencies should be fixed ------------------------------------------------ Key: RF-11544 URL: https://issues.jboss.org/browse/RF-11544 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.1.0.Milestone2 Reporter: Karel Piwko Description of problem: RichFaces bom contains com.sun.faces for jsf-api definition. Version-Release number of selected component (if applicable): 4.1.0-20110910-M2-redhat-1 How reproducible: Always. Steps to Reproduce: 1. Import org.richfaces:richfaces-bom Actual results: There is com.sun.faces:jsf-api and com.sun.faces:jsf-impl Expected results: There should be javax.faces:jsf-api and com.sun.faces:jsf-impl -- 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, 8 months

11
29
0 / 0

[JBoss JIRA] (RF-11760) Remove parent section from richfaces-bom

by Karel Piwko (Created) (JIRA)

Remove parent section from richfaces-bom ---------------------------------------- Key: RF-11760 URL: https://issues.jboss.org/browse/RF-11760 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.1.0.CR1 Reporter: Karel Piwko Priority: Blocker Having <parent> element in the BOM file is fundamentally wrong. If user imports dependencyManagement of the BOM file, it imports even the dependencies from its parent and upper ancestors. Since the ancestor is jboss-parent, it includes virtually the whole world. -- 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, 8 months

9
13
0 / 0

[JBoss JIRA] Created: (RF-8210) switchType=ajax on modalPanel

by Gonzalez Adrian (JIRA)

switchType=ajax on modalPanel ----------------------------- Key: RF-8210 URL: https://jira.jboss.org/jira/browse/RF-8210 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gonzalez Adrian Lately, I'm mostly (80% of times) rendering my rich:modalPanels in ajax mode [1] : - a4j:commandButton calls a backing bean method, and rerenders the a4j:outputPanel surrounding rich;modalPanel. oncomplete js handler call Richfaces.showPanel. - the rich:modalPanel is inside a a4j:outputPanel nd its rendered attribute points to a backing bean property. This is because each modalPanels weights more or less 5 ko (I've seen 4 different application and it was always at least 5 ko). This code is repetitive. Could it be possible to add a switchType (or mode) attribute on rich:calendar, the meaning of which would be : 1. if switchType=client, behaviour unchanged. 2. if switchType=ajax, Richfaces.showModal would make an ajax call, rerender the rich:modalPanel (so rich:modalPanel would always be contained in an invisible <span> or shting like this) and show it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
5
0 / 0

[JBoss JIRA] (RF-11842) Support for macrosubstitutions in the contextMenu

by Brian Leathem (Created) (JIRA)

Support for macrosubstitutions in the contextMenu ------------------------------------------------- Key: RF-11842 URL: https://issues.jboss.org/browse/RF-11842 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.1.1.Final Reporter: Brian Leathem Fix For: 4.2.0.Tracking The RichFaces 3 contextMenu supported _macrosubstitutions_, whereby a single instance of the contextMenu will be created and among multiple components. This RichFaces 4 contextMenu should support this feature. See the [RichFaces 3 showcase|http://livedemo.exadel.com/richfaces-demo/richfaces/contextMenu.jsf] for an example of this behaviour. -- 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, 8 months

5
4
0 / 0

[JBoss JIRA] (RF-11948) [rich:extendedDataTable] js-error this.normalPartStyle is undefined

by Rene O (JIRA)

Rene O created RF-11948: --------------------------- Summary: [rich:extendedDataTable] js-error this.normalPartStyle is undefined Key: RF-11948 URL: https://issues.jboss.org/browse/RF-11948 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.CR1 Environment: richfaces-4.2.0-SNAPSHOT, Firefox 10 Reporter: Rene O If you use rich:extendedDataTable and manually set the width of a column afterwards, a js error occurs {code:title=page-snippet to reproduce the issue} <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:a4j="http://richfaces.org/a4j" xmlns:rich="http://richfaces.org/rich" > <h:head> <title>JSF Test</title> </h:head> <h:body> <h:form id="myForm"> <rich:extendedDataTable id="tableA" var="item" value="#{model.tableList}" rows="5"> <f:facet name="header"> <h:outputText value="HeaderA" /> </f:facet> <rich:column id="colA" width="100px"> <f:facet name="header"> ColA </f:facet> #{item.itemA} </rich:column> </rich:extendedDataTable> <script type="text/javascript"> #{rich:component('tableA')}.setColumnWidth('colA','200'); </script> </h:form> </h:body> </html> {code} {code:title=js error} Fehler: this.normalPartStyle is undefined Quelldatei: http://localhost:8080/jsftest/javax.faces.resource/extendedDataTable.js.j... Zeile: 279 {code} -- 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, 8 months

4
24
0 / 0

[JBoss JIRA] Created: (RF-11392) rich:collapsibleSubTable - can't scroll in Mojarra

by Jan Papousek (JIRA)

rich:collapsibleSubTable - can't scroll in Mojarra -------------------------------------------------- Key: RF-11392 URL: https://issues.jboss.org/browse/RF-11392 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.1.0.Milestone2 Environment: RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79 Metamer 4.1.0.20110910-M2 r.22701 Mojarra 2.1.2-FCS Apache Tomcat 7.0.16 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.112 Safari/534.30 RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79 Metamer 4.1.0.20110910-M2 r.22701 Mojarra 2.1.2-FCS Apache Tomcat 7.0.16 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 Reporter: Jan Papousek Open Metamer page in */faces/components/richCollapsibleSubTable/scroller.xhtml*: *The First Problem* - User can't move to the page 3 using the button *»*. - Number buttons work properly. *The Second Problem* - Move in the *Men* section to the second page - Move in the *Women* section to the second page. - The first page in the section *Men* is displayed (wrong). ---- Using MyFaces everything is OK. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
4
0 / 0

[JBoss JIRA] (RF-11940) mobile showcase - a4j:push - not retrieving pushes from server

by Juraj Huska (JIRA)

Juraj Huska created RF-11940: -------------------------------- Summary: mobile showcase - a4j:push - not retrieving pushes from server Key: RF-11940 URL: https://issues.jboss.org/browse/RF-11940 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: container: JBoss AS 7.1.0.CR1b device: Motorola Xoom(Android 3.2.1) Reporter: Juraj Huska There is no push done in demo for a4j:push, however push demo work for desktop fine. -- 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, 8 months

3
16
0 / 0

[JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup

by Pavol Pitonak (Created) (JIRA)

Label for calendar results in non-valid markup ---------------------------------------------- Key: RF-11833 URL: https://issues.jboss.org/browse/RF-11833 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.1.0.Final Reporter: Pavol Pitonak The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate). {code:xml} <h:outputLabel value="From date" for="fromDate" /> <rich:calendar id="fromDate" .../> {code} {code:xml} <label for="dateForm:fromDate">From date</label> <span class="calendar" id="dateForm:fromDate"> <span id="dateForm:fromDatePopup" style="white-space: nowrap;"> <input class="rf-cal-inp " id="dateForm:fromDateInputDate" name="dateForm:fromDateInputDate" readonly="readonly" style="vertical-align: middle; " type="text" value="Nov 19, 2011" /> ... {code} -- 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, 8 months

5
19
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2012