April 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12126) showcase - rich:editor - autosaving and toolbar & skinning demos exceed the edges

by Juraj Huska (JIRA)

Juraj Huska created RF-12126: -------------------------------- Summary: showcase - rich:editor - autosaving and toolbar & skinning demos exceed the edges Key: RF-12126 URL: https://issues.jboss.org/browse/RF-12126 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, showcase Affects Versions: 4.2.1.CR1 Environment: browser: Firefox 11 Reporter: Juraj Huska Priority: Optional The from summary exceed the bottom part of the area, they are supposed to be. Please see the screenshots. -- 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

2
6
0 / 0

[JBoss JIRA] (RF-12125) showcase - demo rich:dataGrid - outputText elements nested in panelGrids have big font and exceed the edges

by Juraj Huska (JIRA)

Juraj Huska created RF-12125: -------------------------------- Summary: showcase - demo rich:dataGrid - outputText elements nested in panelGrids have big font and exceed the edges Key: RF-12125 URL: https://issues.jboss.org/browse/RF-12125 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables, showcase Affects Versions: 4.2.1.CR1 Environment: container: JBoss AS 7.1.1.Final only browsers: Chrome, Firefox Reporter: Juraj Huska Please look at the screenshot, to see broken rich:dataGrid. The h:outputText elements has bigger font than normally, and it causes that they exceed from panelGrid edges. Note that this is occurring only on JBoss AS 7.1.1.Final and other demos based on dataGrid (like a4j:repeat) are also broken. -- 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

2
7
0 / 0

[JBoss JIRA] (RF-12124) showcase - a4j:repeat demo - the rendered grid is broken

by Juraj Huska (JIRA)

Juraj Huska created RF-12124: -------------------------------- Summary: showcase - a4j:repeat demo - the rendered grid is broken Key: RF-12124 URL: https://issues.jboss.org/browse/RF-12124 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: container: JBoss AS 7.1.1.Final only browsers: Chrome, Firefox Reporter: Juraj Huska Attachments: repeatBroken.png The rendered grid for a4j:repeat is broken. That is, the grid items have wrong position. It is occurring only when showcase deployed on JBoss AS 7.1.1.Final. Please see also the screenshot. -- 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

2
7
0 / 0

[JBoss JIRA] (RF-12147) Mobile Showcase: Mobile version is not shown when Opera Mobile/Mini is used

by Jan Papousek (JIRA)

Jan Papousek created RF-12147: --------------------------------- Summary: Mobile Showcase: Mobile version is not shown when Opera Mobile/Mini is used Key: RF-12147 URL: https://issues.jboss.org/browse/RF-12147 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: mobile, showcase Affects Versions: 4.2.0.Final, 4.2.1.CR1 Reporter: Jan Papousek Opera Mobile/Mini isn't detected correctly and common version of Showcase is displayed. Tested browsers have the following user agents: - Opera/9.80(Linux; Opera Mobi/32904; U; en) Presto/2.10.254 Version/12.00 - Opera/9.80(iPhone; Opera Mini/6.13548/27.1407; U; en) Presto/2.8.119 Version/11.10 Opera's User Agent is described here: http://my.opera.com/community/openweb/idopera/ -- 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

2
7
0 / 0

[JBoss JIRA] (RF-11737) WARNING: Queue with name 'xxx' has already been registered

by Milo van der Zee (Created) (JIRA)

WARNING: Queue with name 'xxx' has already been registered ---------------------------------------------------------- Key: RF-11737 URL: https://issues.jboss.org/browse/RF-11737 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.1.0.CR1 Environment: RF4.0.1.20111111RC1, Mojarry 2.1.4, Tomcat 7.0.21, Gentoo Linux Reporter: Milo van der Zee As soon as a component with a queue is put inside a composite it will create a continues stream of warnings. Even if components outside the composite are used. -- 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

10
14
0 / 0

[JBoss JIRA] (RF-12150) rich:menuItem is not sending request in IE8 with mode=ajax in RF4.2.1.CR1

by joesepp1974 (JIRA)

joesepp1974 created RF-12150: -------------------------------- Summary: rich:menuItem is not sending request in IE8 with mode=ajax in RF4.2.1.CR1 Key: RF-12150 URL: https://issues.jboss.org/browse/RF-12150 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.2.1.CR1 Environment: JBoss 7.1.1, Windows XP, Internet Explorer 8 Reporter: joesepp1974 Since RF4.2.1.CR1 the rich:menuItem does not send a request in mode=ajax in IE8. In Opera it is working correct, with version RF4.2.0 it was also working correct with IE8, -- 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

2
5
0 / 0

[JBoss JIRA] (RF-11975) Prototype script error in Portal

by Ken Finnigan (JIRA)

Ken Finnigan created RF-11975: --------------------------------- Summary: Prototype script error in Portal Key: RF-11975 URL: https://issues.jboss.org/browse/RF-11975 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: third-party Affects Versions: 3.3.3.Final Environment: GateIn v3.2 JBoss PortletBridge v2.2.0.Final Firefox Reporter: Ken Finnigan Priority: Minor When a user wants to add two separate portlets to the same portal page, with both portlets using RichFaces components, the JBoss PortletBridge needs to have the context parameter "org.jboss.portletbridge.WRAP_SCRIPTS" set to true. This wraps the RichFaces JavaScript files with a check to prevent the same file being loaded twice on the one page, as there are two portlets with RichFaces scripts being loaded. In this situation, the prototype.js script (or framework_pack.js when LoadScriptStrategy is ALL) returns "$A() is not defined" within Firefox, but in Chrome and IE it works fine. This JS error in Firefox can be resolved by moving the $A function to the very top of the file to ensure it is defined when needed. -- 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

3
6
0 / 0

[JBoss JIRA] (RF-12152) rich:autocomplete not allowing blank suggestions

by somanathan chandrasekaran (JIRA)

somanathan chandrasekaran created RF-12152: ---------------------------------------------- Summary: rich:autocomplete not allowing blank suggestions Key: RF-12152 URL: https://issues.jboss.org/browse/RF-12152 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.CR1 Environment: jboss 6.0/jsf2/richfaces 4 Reporter: somanathan chandrasekaran richfaces:autocomplete not allowing blank suggestions. In richfaces 3.3, rich:suggestion box allows blank suggestions. If user is not entering any filter char, all the suggestion items shall be populated. In richfaces 4, with rich:autocomplete empty suggestion ajax call is not happening. It is showing the list only if the user enters any character. -- 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

2
1
0 / 0

[JBoss JIRA] (RF-12149) Rendering from table row is broken

by Nick Dev (JIRA)

Nick Dev created RF-12149: ----------------------------- Summary: Rendering from table row is broken Key: RF-12149 URL: https://issues.jboss.org/browse/RF-12149 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.2.0.Final Environment: JSF Mojarra 2.1.7 Reporter: Nick Dev Rendering component in table header does not work when performed from table row. AJAX response has wrong id like "testform:table:5:out" instead of "testform:table:out". Affects both rich:dataTable and rich:extendedDataTable. -- 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

2
3
0 / 0

[JBoss JIRA] (RF-12142) treeSelectionChangeListener: attribute @for does not work

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12142: -------------------------------- Summary: treeSelectionChangeListener: attribute @for does not work Key: RF-12142 URL: https://issues.jboss.org/browse/RF-12142 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Environment: RichFaces 4.2.1.SNAPSHOT Metamer 4.2.1.SNAPSHOT Mojarra 2.1.7-jbossorg-1 JBoss AS 7.1.1.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 11.0 @ Linux x86_64 Reporter: Jiří Štefek Attribute @for of rich:treeSelectionChangeListener component does not work correctly. If the meaning of @for attribute is, that the component with it can be placed outside of a component[1] that it will work for and attribute @for holds its id[1]. -- 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

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2012