September 2012 - richfaces-issues

[JBoss JIRA] (RF-12161) Mobile Showcase: rich:contextMenu is hiding after action is performed

by Jan Papousek (JIRA)

Jan Papousek created RF-12161: --------------------------------- Summary: Mobile Showcase: rich:contextMenu is hiding after action is performed Key: RF-12161 URL: https://issues.jboss.org/browse/RF-12161 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.2.1.Final Environment: iPhone 4.2.1 JBoss AS 7.1.1.Final 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

11 years, 6 months

3
7
0 / 0

[JBoss JIRA] (RF-11649) Mobile Showcase: some demos overflow from a small screen

by Jan Papousek (Created) (JIRA)

Mobile Showcase: some demos overflow from a small screen --------------------------------------------------------- Key: RF-11649 URL: https://issues.jboss.org/browse/RF-11649 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase, skinning Affects Versions: 4.1.0.Milestone4 Reporter: Jan Papousek The page width of all demos in showcase should fit the screen, even if the screen is small. -- 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

11 years, 6 months

4
7
0 / 0

[JBoss JIRA] (RF-11871) Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click

by Jan Papousek (Created) (JIRA)

Mobile Showcase and a4j:poll demo: stop button doesn't respond on the first click --------------------------------------------------------------------------------- Key: RF-11871 URL: https://issues.jboss.org/browse/RF-11871 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.1.1.Final Environment: richfaces-showcase-4.1.1-20120106.230242-18 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

11 years, 6 months

6
15
0 / 0

[JBoss JIRA] (RF-11966) Radiobuttons not visible in firefox but visible in IE

by Roopa Shenoy (JIRA)

Roopa Shenoy created RF-11966: --------------------------------- Summary: Radiobuttons not visible in firefox but visible in IE Key: RF-11966 URL: https://issues.jboss.org/browse/RF-11966 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Roopa Shenoy Priority: Blocker Hi , We are facing certain issues regarding rendering radio buttons in firefox. It works fine in IE but doesnot work in Firefox Please find the below block of code. In the code shown below,there are two panels for displaying radio buttons. Last piece of code which displays commandlink is visible ,but the radiobuttons which needs to be shown on pageload is not visible. When we click on commandlink , the flag showMoreValues turns true and only on click of this link the radiobuttons in second part of the code is visible. Can you please help me out regarding this issue? <a4j:form id="subscriptionForm" ajaxSubmit="true"> <f:loadBundle basename="dk.tdc.resources.Messages" var="msgs" /> <h:panelGrid columns="1"> <h:panelGroup rendered="#{subscriptionCard.showValues}" id="ValuesList"> <h:panelGrid columns="4" columnClasses="address_col1,address_col1,address_col1,address_col1"> <c:forEach var="privateProducts" items="#{subscriptionCard.Values}"> <h:selectOneRadio id="#{privateProducts.description}" valueChangeListener="#{subscriptionCard.productChanged}" value="#{subscriptionCard.selectedProductCode}"> <a4j:support event="onclick" reRender="convertingForm,privateParamCard,businessParamCard,errorDetailsSubs,facilitiesCard,numberSelectCard,npPanel,paymentFormCard" /> <f:selectItem itemLabel="#{privateProducts.label}" itemValue="#{privateProducts.value}" /> </h:selectOneRadio> </c:forEach> </h:panelGrid> </h:panelGroup> <h:panelGroup rendered="#{subscriptionCard.showMoreValues}" id="moreValues"> <h:panelGrid columns="4" columnClasses="address_col1,address_col1,address_col1,address_col1"> <c:forEach var="privateAllProducts" items="#{subscriptionCard.showMoreValues}"> <h:panelGroup> <h:selectOneRadio id="#{privateAllProducts.description}" valueChangeListener="#{subscriptionCard.productChanged}" value="#{subscriptionCard.selectedProductCode}"> <a4j:support event="onclick" reRender="convertingForm,privateParamCard,businessParamCard,errorDetailsSubs,facilitiesCard,numberSelectCard,npPanel,paymentFormCard" /> <f:selectItem itemLabel="#{privateAllProducts.label}" itemValue="#{privateAllProducts.value}" /> </h:selectOneRadio> </h:panelGroup> </c:forEach> </h:panelGrid> </h:panelGroup> <h:panelGroup style="float:right;" rendered="#{subscriptionCard.showValues}"> <h:panelGroup style="float:right;" rendered="#{subscriptionCard.ValuesLinkVisible}"> <a4j:commandLink id="index" action="#{subscriptionCard.retrieveMoreValuess}" reRender="moreValues" value="#{msgs.subscriptioncard_link_more_Values}"></a4j:commandLink> </h:panelGroup> </h:panelGroup> -- 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

11 years, 6 months

3
4
0 / 0

[JBoss JIRA] (RF-12214) Resource plugin: pack plain skin

by Nicolas Daniels (JIRA)

Nicolas Daniels created RF-12214: ------------------------------------ Summary: Resource plugin: pack plain skin Key: RF-12214 URL: https://issues.jboss.org/browse/RF-12214 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: resource handling Affects Versions: 4.2.1.Final Reporter: Nicolas Daniels Priority: Minor The plain skin is not packed/compresses as other styles, mainly because images generation is failing due to null property values. It could be good to have it as well. Beside it, probably that image generation with null value should be handled. Of course, any failed image generation should not be referenced in resulting css. (Fyi, currently, generating plain skin is working despite the warnings but missing images are still referenced in resulting css. This is not really good for resources optimization ;-)) -- 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

11 years, 6 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-9850) Support of header in autocomplete with table layout

by Tommy Bø (JIRA)

Support of header in autocomplete with table layout --------------------------------------------------- Key: RF-9850 URL: https://jira.jboss.org/browse/RF-9850 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Milestone4 Environment: All Reporter: Tommy Bø It would be nice to be able to set the headers for columns when we're specifying layout="table" in the autocomplete-component. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
3
0 / 0

[JBoss JIRA] (RF-12483) Showcase - lot of JS errors, Ajax functionality broken for every component

by Juraj Húska (JIRA)

Juraj Húska created RF-12483: -------------------------------- Summary: Showcase - lot of JS errors, Ajax functionality broken for every component Key: RF-12483 URL: https://issues.jboss.org/browse/RF-12483 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: base functionality , showcase Affects Versions: 4.3.0.Milestone2 Environment: richfaces-showcase-4.3.0-SNAPSHOT Reporter: Juraj Húska Priority: Blocker Interacting with components (or just loading the demo) causes firing lot of JS errors, all of them starts with: {code} TypeError: Richfaces.ajax is not a function. {code} {code} Uncaught ReferenceError: jQuery is not defined packed.js:887 (anonymous function) {code} then depending on the demo it continues for example for a4j:poll with these: {code} Uncaught TypeError: Cannot read property 'PanelMenu' of undefined component-sample.jsf:68 Uncaught TypeError: Cannot read property 'PanelMenuGroup' of undefined Uncaught TypeError: Cannot read property 'Tab' of undefined component-sample.jsf:70 Uncaught TypeError: Cannot read property 'Poll' of undefined {code} Is not this caused by JQuery update to 1.8.1 ? -- 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

11 years, 6 months

3
8
0 / 0

[JBoss JIRA] (RF-12482) rich:fileUpload, the upload button disappeared after deleting a uploaded file

by Janli Lee (JIRA)

Janli Lee created RF-12482: ------------------------------ Summary: rich:fileUpload, the upload button disappeared after deleting a uploaded file Key: RF-12482 URL: https://issues.jboss.org/browse/RF-12482 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: IDE: eclipse 3.7.1 plugin: jboss plugin richface ver: 4.2.0 System: windows 7 Browser: IE 8 Reporter: Janli Lee <h:form prependId="false"> <rich:fileUpload/> </h:form> code is too easy, isn't it~~ the steps below show my problem. 1. Choose "Add", select file1.txt, and then click "Upload". After uploaded, i can see a "Clear" link label for this file. 2. Choose "Add" again, select file2.txt, and then click the "Clear" link label for file1.txt created in the first step (Not the Clear All on top right). 3. After these, the "Upload" button disappeared, my god. -- 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

11 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (RF-10277) XML Parsing Error in response due to invalid character in attribute

by Michael Heinen (JIRA)

XML Parsing Error in response due to invalid character in attribute -------------------------------------------------------------------- Key: RF-10277 URL: https://issues.jboss.org/browse/RF-10277 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Environment: richfaces 3.3.3 myfaces 1.2.9 facelets neko parser 1.9.12 Reporter: Michael Heinen An ajax response is not updated on clientside if it contains ISO control characters like 'START OF HEADING' (in windows Alt + 01 or U+0001) in attributes of tags. (see http://www.fileformat.info/info/unicode/char/1/index.htm) The ajax console shows during rendering: error[14:57:16,523]: Error parsing XML error[14:57:16,523]: Parse Error: XML Parsing Error: Invalid unicode character. The parser error occurs in combination with neko filter if such a special character is used as an attribute value, e.g. as value of an inputText field. This is caused by a wrong transformation in class org.ajax4jsf.xml.serializer.ToXHTMLStream. Method ToXHTMLStream.writeAttrString contains following check: String outputStringForChar = m_charInfo.getOutputStringForChar(ch); if (null != outputStringForChar) { writer.write(outputStringForChar); } else if (escapingNotNeeded(ch)) { writer.write(ch); // no escaping in this case } else { writer.write("&#"); writer.write(Integer.toString(ch)); //THIS IS CALLED! writer.write(';'); } The 'START OF HEADING' control char is transformed to the entity  which results in an parsing error on client side. The char is correctly processed and displayed in NON-Ajax requests. The char is correctly processed and displayed in Ajax requests in outputfields (as \u0001). The char is correctly processed but not displayed in the response if tidy filter is used for ajax requests. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
2
0 / 0

[JBoss JIRA] (RF-12501) Upgrade jsf-test to JSF 2.1.11

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12501: ------------------------------- Summary: Upgrade jsf-test to JSF 2.1.11 Key: RF-12501 URL: https://issues.jboss.org/browse/RF-12501 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: tests - unit Affects Versions: 4.2.2.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Minor Fix For: 4.3.0.Milestone2 When I have upgraded Core to {{2.1.11}}, staging server fails to start because of {{NullPointerException}}. Similar exception happens in {{jsf-test}} unit tests, let's upgrade to address an issue. {code} org.jboss.test.faces.TestException: Server not started due to listener error at org.jboss.test.faces.staging.StagingServer.init(StagingServer.java:575) at org.jboss.test.faces.FacesEnvironment.start(FacesEnvironment.java:399) at org.richfaces.context.ExtendedPartialVisitContextTest.setUp(ExtendedPartialVisitContextTest.java:307) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) 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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) java.lang.NullPointerException at org.richfaces.context.ExtendedPartialVisitContextTest.tearDown(ExtendedPartialVisitContextTest.java:341) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:37) 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.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) {code} -- 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

11 years, 6 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues September 2012