March 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11884) Multiple Errors with IE8/9

by Friedhelm Kuehn (JIRA)

Friedhelm Kuehn created RF-11884: ------------------------------------ Summary: Multiple Errors with IE8/9 Key: RF-11884 URL: https://issues.jboss.org/browse/RF-11884 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-panels-layout-themes, component-tables, component-tree Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when RF is removed) Reporter: Friedhelm Kuehn Priority: Critical Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px). Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen. Problem 3: <a4j:commandlink> with icon: Icon is surrounded by dark border Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also). Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode Problem 6: Javascript Error in ExtendedDataTable.js Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement. I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ?? Please help ! -- 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, 9 months

5
30
0 / 0

[JBoss JIRA] (RF-11560) Showcase on OpenShift Express: Push stops to work after first long-polling request

by Lukáš Fryč (Created) (JIRA)

Showcase on OpenShift Express: Push stops to work after first long-polling request ---------------------------------------------------------------------------------- Key: RF-11560 URL: https://issues.jboss.org/browse/RF-11560 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.1.0.Milestone3 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Critical Fix For: 4.1.0.Milestone4 Both demos affected: TopicsContext and Push CDI. -- 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, 9 months

8
10
0 / 0

[JBoss JIRA] (RF-12109) Showcase in AS 7.1.1 (JSF 2.1.7) missing doctype and <html> root

by Brian Leathem (JIRA)

Brian Leathem created RF-12109: ---------------------------------- Summary: Showcase in AS 7.1.1 (JSF 2.1.7) missing doctype and <html> root Key: RF-12109 URL: https://issues.jboss.org/browse/RF-12109 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Assignee: Brian Leathem Priority: Critical Fix For: 4.2.1.CR1 Changes to how ui:include and templates are processed in Mojarra 2.1.7 result in the doctype and html root element being omitted from the showcase. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] (RF-12086) Update the RichFaces WFK version in the archetypes

by Brian Leathem (JIRA)

Brian Leathem created RF-12086: ---------------------------------- Summary: Update the RichFaces WFK version in the archetypes Key: RF-12086 URL: https://issues.jboss.org/browse/RF-12086 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: archetype Reporter: Brian Leathem Priority: Critical Fix For: 4.2.1.CR1 -- 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, 9 months

1
6
0 / 0

[JBoss JIRA] (RF-12082) Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName)

by Jan Papousek (JIRA)

Jan Papousek created RF-12082: --------------------------------- Summary: Components: Output UI module doesn't pass unit tests (AbstractTogglePanelTest#testGetChildName) Key: RF-12082 URL: https://issues.jboss.org/browse/RF-12082 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.3.0.Milestone1 Reporter: Jan Papousek Priority: Critical {code} ------------------------------------------------------------------------------- Test set: org.richfaces.component.AbstractTogglePanelTest ------------------------------------------------------------------------------- Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.022 sec <<< FAILURE! testGetChildName(org.richfaces.component.AbstractTogglePanelTest) Time elapsed: 0.005 sec <<< FAILURE! java.lang.AssertionError: Expected exception: java.lang.IllegalArgumentException at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) {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, 9 months

2
3
0 / 0

[JBoss JIRA] (RF-12042) Metamer: rich:contextMenu doesn't disappear after clicking out of the menu

by Jan Papousek (JIRA)

Jan Papousek created RF-12042: --------------------------------- Summary: Metamer: rich:contextMenu doesn't disappear after clicking out of the menu Key: RF-12042 URL: https://issues.jboss.org/browse/RF-12042 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.2.0.Final Environment: •RichFaces 4.2.1-SNAPSHOT •Metamer 4.2.1-SNAPSHOT •Mojarra 2.1.5-SNAPSHOT •JBoss AS 7.1.0.Final •Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux •Internet Explorer 9.0 @ Win32 Reporter: Jan Papousek -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] (RF-12043) Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode

by Jan Papousek (JIRA)

Jan Papousek created RF-12043: --------------------------------- Summary: Metamer: rich:contextMenu isn't rendered correctly in IE 9 compatibility mode Key: RF-12043 URL: https://issues.jboss.org/browse/RF-12043 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux Internet Explorer 7.0 @ Win32 (this is IE 9 Compatibility Mode) Reporter: Jan Papousek -- 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, 9 months

2
6
0 / 0

[JBoss JIRA] (RF-11781) rich:list and rich:dataScroller: numbering on other than the first page

by Jan Papousek (Created) (JIRA)

rich:list and rich:dataScroller: numbering on other than the first page ----------------------------------------------------------------------- Key: RF-11781 URL: https://issues.jboss.org/browse/RF-11781 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.1.0.CR2 Reporter: Jan Papousek When the rich:list and rich:dataScroller are used together, the first items in lists on pages 2, 3, ... shouldn't be numbered with number 1. For example, when the number of items on one page is limited to 10, the first item on the second page should be numbered with 11 (not 1). To try the behaviour of this components working together deploy Metamer and open http://localhost:8080/metamer/faces/components/richList/scroller.xhtml. -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] (RF-12074) Showcase mediaOutput refers to GAE limitations

by Brian Leathem (JIRA)

Brian Leathem created RF-12074: ---------------------------------- Summary: Showcase mediaOutput refers to GAE limitations Key: RF-12074 URL: https://issues.jboss.org/browse/RF-12074 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: showcase Reporter: Brian Leathem Fix For: 4.2.1.CR1 {quote} As the Google Application Engine restricts AWT class usage, this example reads the existing image and only performs re-indexing of the palette using colors you selected below. {quote} The example, and the wording should be re-worked to not refer to the GAE limitation. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] (RF-11977) Multiple fileUpload controls on the same page do not work

by Roxana Roxana (JIRA)

Roxana Roxana created RF-11977: ---------------------------------- Summary: Multiple fileUpload controls on the same page do not work Key: RF-11977 URL: https://issues.jboss.org/browse/RF-11977 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 4.1.0.Final Environment: IE7,8,9, FireFox, Google Chrom Reporter: Roxana Roxana Priority: Critical Situation: Two rich:fileUpload controls, in the same form. When: 1) choose first file for upload 2) choose second file for upload 3) click upload button for the first file The first control disappears from the page and you cannot upload the second file (the upload event is never caught). Could you please indicate a solution for this problem? Thank you very much! Part of the code used for testing is the following: <h:form id="uploadForm"> <rich:panel> <rich:panel> <rich:fileUpload id="uploadFile1" fileUploadListener="#{bean.method1}" maxFilesQuantity="1" immediateUpload="true" listHeight="65px"</rich:fileUpload> </rich:panel> <rich:panel> <rich:fileUpload id="uploadFile2" fileUploadListener="#{bean.method2}" maxFilesQuantity="1" immediateUpload="true" listHeight="65px"</rich:fileUpload> </rich:panel> <rich:panel> <a4j:commandButton id="addB" value="value" action="#{bean.method3}" render="stg" /> </rich:panel> </rich:panel> </h:form> -- 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, 9 months

4
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2012