October 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-7451) Can't resize scrollableDataTable columns if scrollableDataTable is placed in modal panel

by Denis Petrunin (JIRA)

Can't resize scrollableDataTable columns if scrollableDataTable is placed in modal panel ---------------------------------------------------------------------------------------- Key: RF-7451 URL: https://jira.jboss.org/jira/browse/RF-7451 Project: RichFaces Issue Type: Bug Components: component-ScrollableDataTable Affects Versions: 3.3.1 Environment: RichFaces 3.3.1, Firefox 3.0.11 Reporter: Denis Petrunin Can't resize scrollableDataTable columns if scrollableDataTable is placed in modal panel. Try the following code in Firefox 3.0.11. I'd like to note that there is no such issue in IE 6/7. <rich:modalPanel showWhenRendered="true"> <rich:scrollableDataTable width="200" height="100"> <rich:column> <f:facet name="header"> COLUMN </f:facet> </rich:column> </rich:scrollableDataTable> </rich:modalPanel> -- 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

15 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-7486) scrollableDataTable content disappears on browser window resizing

by Denis Petrunin (JIRA)

scrollableDataTable content disappears on browser window resizing ----------------------------------------------------------------- Key: RF-7486 URL: https://jira.jboss.org/jira/browse/RF-7486 Project: RichFaces Issue Type: Bug Components: component-ScrollableDataTable Affects Versions: 3.3.1 Environment: RichFaces 3.3.1, Firefox 3.0.11 / IE7 Reporter: Denis Petrunin scrollableDataTable content disappears on browser window resizing if scrollableDataTable is placed into tabPanel. Try the following code in FF. 1) switch to "TAB-B" 2) make a note that scrollableDataTable becomes visible. 3) switch back to "TAB-A" 4) resize browser window 5) switch to "TAB-B" 6) make a note that scrollableDataTable content is absent 7) resize browser window 8) make a note that scrollableDataTable becomes visible. Expected result: scrollableDataTable content should be visible on step 6. <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:rich="http://richfaces.org/rich"> <body> <rich:tabPanel switchType="client"> <rich:tab label="TAB-A"> TEST </rich:tab> <rich:tab label="TAB-B"> <rich:scrollableDataTable> <rich:column> <f:facet name="header"> COLUMN </f:facet> </rich:column> </rich:scrollableDataTable> </rich:tab> </rich:tabPanel> </body> </html> -- 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

15 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-7772) richfaces-demo a4j:status page throws TagAttributeException

by Jay Balunas (JIRA)

richfaces-demo a4j:status page throws TagAttributeException ----------------------------------------------------------- Key: RF-7772 URL: https://jira.jboss.org/jira/browse/RF-7772 Project: RichFaces Issue Type: Bug Components: examples Affects Versions: 4.0.0.ALPHA1 Reporter: Jay Balunas Assignee: Ilya Shaikovsky Priority: Critical Fix For: 4.0.0.ALPHA2 Deployed most recent ALPHA1 example build. When navigating to the a4j:status page I get the exception below. javax.faces.view.facelets.TagAttributeException: /richfaces/status.xhtml @22,65 <ui:include src="/richfaces/status/referencedusage.xhtml"> Invalid path : /richfaces/status/referencedusage.xhtml at com.sun.faces.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:107) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:91) at com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:97) at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:172) at com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:375) at com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:346) at com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:102) at javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:91) at javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:120) at com.sun.faces.facelets.tag.jsf.CompositeComponentTagHandler.applyNextHandler(CompositeComponentTagHandler.java:135) at com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:201) at javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:114) at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:160) at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:86) at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:75) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:283) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:342) at com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:321) at com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:180) at com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:149) at com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:86) at com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:75) at com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:130) at com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:823) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:311) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:637) -- 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

15 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-1145) DataScroller. Parameters(both a4j and f) always null.

by Ilya Shaikovsky (JIRA)

DataScroller. Parameters(both a4j and f) always null. ----------------------------------------------------- Key: RF-1145 URL: http://jira.jboss.com/jira/browse/RF-1145 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.2, 3.2.0 Reporter: Ilya Shaikovsky Assigned To: Anton Belevich Fix For: 3.2.0 <rich:datascroller id="scroller" pageIndexVar="pi" action="#{bean.action}"> <f:param name="index" assignTo="#{bean.property1}" value="#{pi}"/> </rich:datascroller> <rich:datascroller ajaxSingle="false" id="scroller" pageIndexVar="pi" action="#{bean.action}"> <a4j:actionparam name="index" assignTo="#{bean.property1}" value="#{pi}"></a4j:actionparam> </rich:datascroller> in seter: System.out.println("Setting property1 to _> "+ property1); in action System.out.println(FacesContext.getCurrentInstance().getExternalContext().getRequestParameterMap().get("pi")); Both sysouts prints null in log. -- 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

15 years, 11 months

6
15
0 / 0

[JBoss JIRA] Created: (RF-7650) a4j:region

by Nick Belaevski (JIRA)

a4j:region ---------- Key: RF-7650 URL: https://jira.jboss.org/jira/browse/RF-7650 Project: RichFaces Issue Type: Sub-task Affects Versions: 4.0.0.ALPHA1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 4.0.0.ALPHA1 -- 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

16 years

2
4
0 / 0

[JBoss JIRA] Created: (RF-2129) ScrollableDataTable : columns sizes are reset after a rerender

by Olivier Martin (JIRA)

ScrollableDataTable : columns sizes are reset after a rerender -------------------------------------------------------------- Key: RF-2129 URL: http://jira.jboss.com/jira/browse/RF-2129 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.1.3 Reporter: Olivier Martin The component ScrollableDataTable allows its columns to be resized, but after a rerender those new sizes are lost. -- 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

16 years

6
12
0 / 0

[JBoss JIRA] Created: (RF-7992) Dynamic Skin css resources escape special html characters.

by Alexander Smirnov (JIRA)

Dynamic Skin css resources escape special html characters. ---------------------------------------------------------- Key: RF-7992 URL: https://jira.jboss.org/jira/browse/RF-7992 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.2.GA Reporter: Alexander Smirnov Fix For: 3.3.3.CR1 In the dynamic CSS files ( .xcss ) <u:style> element uses ResponseWriter#writeText method that escapes special html characters like < > and & as XML entities. In the portal environment resource URL can contain parameters, so part of xcss file like this: <u:style name="background-image"> <f:resource f:key="org.richfaces.renderkit.html.iconimages.CalendarSeparator" /> </u:style> would be rendered incorrectly: background-image:url(/portal/auth/portal/default/SeamDemo/SeamPortletWindow?rfRes=org.richfaces.renderkit.html.images.ButtonBackgroundImage&action=b&cacheability=PAGE&DATA=%2FB%2FeAFjYGDg%21v%219049r- , there all parameter delimiters '&' are replaced by '&' entity. Therefore , most portals does not recognise these URL, and skin images are not loaded. -- 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

16 years

3
5
0 / 0

[JBoss JIRA] Created: (RF-7994) disabled rich:menuItem cause render problems

by Andreas Höhmann (JIRA)

disabled rich:menuItem cause render problems -------------------------------------------- Key: RF-7994 URL: https://jira.jboss.org/jira/browse/RF-7994 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.2.SR1 Environment: FF3 Reporter: Andreas Höhmann Priority: Blocker disabled menu items cause render problems -- 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

16 years

5
15
0 / 0

[JBoss JIRA] Created: (RF-7746) calendar: model updated when it's disabled.

by Ilya Shaikovsky (JIRA)

calendar: model updated when it's disabled. ------------------------------------------- Key: RF-7746 URL: https://jira.jboss.org/jira/browse/RF-7746 Project: RichFaces Issue Type: Bug Components: component-input Affects Versions: 3.3.2.CR1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski according to JSF spec - it should not. -- 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

16 years

6
9
0 / 0

[JBoss JIRA] Created: (RF-7694) suggestionBox: not valid markup according to w3c

by Ilya Shaikovsky (JIRA)

suggestionBox: not valid markup according to w3c ------------------------------------------------ Key: RF-7694 URL: https://jira.jboss.org/jira/browse/RF-7694 Project: RichFaces Issue Type: Bug Components: component-input Affects Versions: 3.3.2.CR1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski http://validator.w3.org/check?uri=http%3A%2F%2Flivedemo.exadel.com%2Frich... pay attention to "end tag for "tbody" which is not finished" error. alt and types messages - related to demo markup problems. But this one caused by suggestion box which encodes table with empty tbody on initial rendering. -- 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

16 years

6
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues October 2009