May 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-11003) Component reference: wrong examples for tooltip

by Pavol Pitonak (JIRA)

Component reference: wrong examples for tooltip ----------------------------------------------- Key: RF-11003 URL: https://issues.jboss.org/browse/RF-11003 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.0.0.Final Reporter: Pavol Pitonak There are bugs in all examples for rich:tooltip # rename rich:toolTip to rich:tooltip in all examples # in Example 13.8. Defining tool-tip content the "Basic Content" sample doesn't work and probably will not work in RF 4.x (see RF-11002) # in Example 13.9. Attaching the tool-tip put the content inside the component instead of using attribute value # in Example 13.10. Unattached tool-tips put the content inside the component instead of using attribute value and fix attribute "onclick" of panel {code:xml} onclick="#{rich:component('toolTipId')}.show(event);" {code} # in Example 13.11. Advanced tool-tip usage put the content inside the component instead of using attribute value and change the direction attribute to "topRight" # check the text that it describes the examples correctly -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-11001) Component reference: remove a4j:form

by Pavol Pitonak (JIRA)

Component reference: remove a4j:form ------------------------------------ Key: RF-11001 URL: https://issues.jboss.org/browse/RF-11001 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: doc Affects Versions: 4.0.0.Final Reporter: Pavol Pitonak The component reference contains <a4j:form> on several places. Use <h:form> instead of <a4j:form>: section 9.4.2. Showing and hiding the pop-up section 9.4.5. Header and controls section 13.4.2. Attaching the tool-tip to another component -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-10999) include all columns in clientFilterFunction for autocomplete

by Tommy Bø (JIRA)

include all columns in clientFilterFunction for autocomplete ------------------------------------------------------------ Key: RF-10999 URL: https://issues.jboss.org/browse/RF-10999 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Final Environment: All Reporter: Tommy Bø In Richfaces 4 you can set clientFilterFunction in autocomplete, but the only value that is checked is the fetchValue. I have the need to scan all the columns of the suggestion in an autocomplete with table-layout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-10990) paint2d and Seam conversation propagation

by Laurent Grangier (JIRA)

paint2d and Seam conversation propagation ----------------------------------------- Key: RF-10990 URL: https://issues.jboss.org/browse/RF-10990 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-output Affects Versions: 3.3.3.Final Reporter: Laurent Grangier It is not possible to propagate the current Seam conversation cross a paint2D image request. Adding <s:conversationId /> to <rich:paint2d .../> tag has no effect. I'm not sure if the problems comes from Seam or RichFaces, but this problem should be resolved. That's sometimes useful to have images which takes part of the current conversation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-10986) Make background gradient in table headers and toolbars configurable

by Martin Vecera (JIRA)

Make background gradient in table headers and toolbars configurable ------------------------------------------------------------------- Key: RF-10986 URL: https://issues.jboss.org/browse/RF-10986 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: skinning Affects Versions: 3.3.2.SR1 Reporter: Martin Vecera The background gradient is by default present at table headers and toolbars. The background is a dynamically generated image and its presence in a web page is caused by XML snippets like the following one (part of richfaces-ui.jar:/org/richfaces/skin.xcss): <u:style name="background-image"> <f:resource xmlns:f="http:/jsf.exadel.com/template" f:key="org.richfaces.renderkit.html.GradientA"/> </u:style> This can be overrided by a custom CSS which is a recommended fix - http://community.jboss.org/wiki/RichFacesDataTableBackgroundOut The big issue here is that you still have the gradient style configured and loaded by your browser, and the background image generated at the server. It would be great if the background gradient was configurable by a skin property like other attributes (e.g. skin.properties: gradientStyle=NONE). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Updated: (RF-10985) richfaces-showcase: design and minor content problems

by Jay Balunas (JIRA)

[ https://issues.jboss.org/browse/RF-10985?page=com.atlassian.jira.plugin.s... ] Jay Balunas updated RF-10985: ----------------------------- Fix Version/s: 4.1.0.Milestone1 > richfaces-showcase: design and minor content problems > ----------------------------------------------------- > > Key: RF-10985 > URL: https://issues.jboss.org/browse/RF-10985 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.0.0.Final > Reporter: Ilya Shaikovsky > Fix For: 4.1.0.Milestone1 > > > 1) need to adjust "new" demos. The only new for now - arrangeable sample. Having that outdated for so long makes the user thinks that nothing changes there. > 2) http://50.richfaces-showcase.appspot.com/richfaces/component-sample.jsf?d... arrangeable tab get cut. > 3) minor content problem: http://50.richfaces-showcase.appspot.com/richfaces/component-sample.jsf?d..., all the colors has "Color 1" label. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-10983) provide possibility in rich:tree to hide connection lines between nodes

by u j (JIRA)

provide possibility in rich:tree to hide connection lines between nodes ----------------------------------------------------------------------- Key: RF-10983 URL: https://issues.jboss.org/browse/RF-10983 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 4.0.0.Final Reporter: u j There is no possibility to my knowledge to not display the connection lines between the nodes of a rich:tree. The easiest would be an attribute of the component. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (RF-10982) rich:column sorting will not function within a rich:togglePanel

by Chris Hornsey (JIRA)

rich:column sorting will not function within a rich:togglePanel --------------------------------------------------------------- Key: RF-10982 URL: https://issues.jboss.org/browse/RF-10982 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 3.3.3.Final Environment: mojarra 1.2 tomcat 7 Reporter: Chris Hornsey When placing a rich:table within a rich:togglePanel the sort feature of all the rich:columns does not function. I have attached an Eclispe project that reproduces this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-10977) validation should not be processed when @required=false and input is empty

by Nikhil Patil (JIRA)

validation should not be processed when @required=false and input is empty -------------------------------------------------------------------------- Key: RF-10977 URL: https://issues.jboss.org/browse/RF-10977 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.1.Milestone1 Environment: Ubuntu 10.04, Jboss 5.1.0 GA, Mojarra 2.0.4, Richfaces 4 (extracted from richfaces-showcase.war of 2011-04-28) Reporter: Nikhil Patil <h:inputText id="txtContact" value="#{user.contact}" required="false" validatorMessage="Invalid phone number" maxlength="10"> <f:validateRegex pattern="\d{10}" /> <rich:validator/> </h:inputText> Regex validation should not be processed when @required=false and input is empty -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-10974) a4:poll data being called twice

by Martin Sadowski (JIRA)

a4:poll data being called twice ------------------------------- Key: RF-10974 URL: https://issues.jboss.org/browse/RF-10974 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Affects Versions: 4.0.0.Final Environment: Tomcat 7.0.12 Reporter: Martin Sadowski Bean: @ManagedBean @SessionScoped public class TestBean { int i = 0; public String getPollData() { System.out.println("getPollData()"); return "" + i++; } } test.xhtml: <a4j:poll interval="10000" data="#{testBean.pollData}" oncomplete="alert(event.data);"/> Result: 1 3 5 ... -> Twice every polling cycle. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2011