February 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8373) moving skins set to 4.x

by Ilya Shaikovsky (JIRA)

moving skins set to 4.x ----------------------- Key: RF-8373 URL: https://jira.jboss.org/jira/browse/RF-8373 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: skinning Affects Versions: 4.0.0.ALPHA1 Reporter: Ilya Shaikovsky Assignee: Lex Dmitriev Fix For: 4.0.0.ALPHA2 http://community.jboss.org/wiki/RichFaces40MarkupsAndSkinning#comment-2778 Add two new parameters for tables, and calculate values for every skin which will be ported to 4.x -- 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

14 years

1
2
0 / 0

[JBoss JIRA] Created: (RF-994) Non-Modal Panel

by Christian Bauer (JIRA)

Non-Modal Panel --------------- Key: RF-994 URL: http://jira.jboss.com/jira/browse/RF-994 Project: RichFaces Issue Type: Feature Request Reporter: Christian Bauer Priority: Critical There is no floating non-modal panel in RichFaces. It could be as easy as adding a "nonmodal" option to the Modal Panel. Of course, Modal Panel shouldn't have been called Modal Panel in the first place, it should be Dialog with the option to make it modal when needed. -- 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

14 years

7
16
0 / 0

[JBoss JIRA] Created: (RF-3051) Demo site: Background image is not applied if page content is wider then browser window.

by Sergey Halipov (JIRA)

Demo site: Background image is not applied if page content is wider then browser window. ---------------------------------------------------------------------------------------- Key: RF-3051 URL: http://jira.jboss.com/jira/browse/RF-3051 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.5, 3.2.1 Environment: Firefox Reporter: Sergey Halipov Attachments: firefox.png -- 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

14 years

4
9
0 / 0

[JBoss JIRA] Created: (RF-5733) extendedTable: Allow to be used without vertical scroller.

by Ilya Shaikovsky (JIRA)

extendedTable: Allow to be used without vertical scroller. ---------------------------------------------------------- Key: RF-5733 URL: https://jira.jboss.org/jira/browse/RF-5733 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski lets allow the table optionally to produce simplier markup analogous to dataTable one. Some forum guys wanna use extendedTable features but without this one. -- 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

14 years

5
9
0 / 0

[JBoss JIRA] Created: (RF-8336) UIDataAdaptor: events broadcasting is happening with wrong client id

by Nick Belaevski (JIRA)

UIDataAdaptor: events broadcasting is happening with wrong client id -------------------------------------------------------------------- Key: RF-8336 URL: https://jira.jboss.org/jira/browse/RF-8336 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 3.3.2.SR1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 4.0.0.BETA1 The following code: <rich:dataTable var="top" value="#{forum5Bean.data}" rowKeyVar="row"> <rich:column> <h:outputText value="#{top}" /> <a4j:commandButton value="Delete"> <a4j:actionparam value="#{row}" assignTo="#{forum5Bean.itemValue}" /> </a4j:commandButton> </rich:column> </rich:dataTable> doesn't work because parameter is submitted with name=clientId (i.e. including row number), but in the time of event broadcast, clientId of a4j:actionparam component doesn't include row index. -- 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

14 years

1
1
0 / 0

[JBoss JIRA] Created: (RF-8197) Optimize AjaxChildrenRenderer render component check algorithm

by Jan Ziegler (JIRA)

Optimize AjaxChildrenRenderer render component check algorithm -------------------------------------------------------------- Key: RF-8197 URL: https://jira.jboss.org/jira/browse/RF-8197 Project: RichFaces Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 3.3.2.SR1 Environment: Myfaces 1.2.8, Facelets 1.1.15, Tomcat 6.0.20 Reporter: Jan Ziegler I just realized some possible "lifecycle processing overhead" when doing ajax actions: In render response phase each ajax component is checked for rendering by the method AjaxChildrenRenderer.encodeAjaxComponent(). That - what I could see - is the case when: # the component´s rendered-attribute is true # the component is ajaxRendered # the componentId is defined in the reRenderId-List This also reflects the order of checking, so the first thing to be done is check if the component´s rendered-attribute is true. But this might also lead to additional lifecycle processings when rendered-conditions are bound to managed beans by el expressions. To evaluate the rendered condition, request scoped managed beans must be created. to my opion this is suboptimal, like in my case the managed bean performs some (time intensive?) actions in its constructor or the rendered conditions relies on a list which must be fetched from the database - and this also happens even if the componentId is not in den reRenderId-List. So why not first evaluate if the componentId is in the reRenderId-List or the component is ajaxRendered and then (if one of this conditions is true) additionally check the rendered-condition? This might be accomplished with a small change AjaxChildrenRenderer.encodeAjaxComponent(): {code} public void encodeAjaxComponent(FacesContext context, UIComponent component, String currentPath, Set<String> ids, Set<String> renderedAreas) throws IOException { if (component.isRendered()) { // skip not-rendered components. boolean found = false; boolean limitToList = AjaxContext.getCurrentInstance(context).isLimitToList(); String elementId = component.getId(); String absoluteId = currentPath + elementId; if (!ids.isEmpty()) { // list for rendering may contains absolute id ( best ), // component Id or client ID // String clientId = element.getClientId(context); if (ids.contains(absoluteId) || ids.contains(elementId)) { if (log.isDebugEnabled()) { log.debug(Messages.getMessage( Messages.RENDER_AJAX_AREA_INFO, absoluteId)); } // renderChild(context, element); found = true; } } // if (!found && limitToList && component instanceof NamingContainer && noIdUnderPath(absoluteId + NamingContainer.SEPARATOR_CHAR, ids)) { return; } if (!found && !limitToList && component instanceof AjaxOutput) { if (((AjaxOutput) component).isAjaxRendered()) { // renderChild(context, element); found = true; } } if (!found) { if (component instanceof AjaxChildrenEncoder) { ((AjaxChildrenEncoder) component).encodeAjaxChild(context, currentPath, ids, renderedAreas); } else { // Special case - for control components, not produced // html code - such as message bundles loaders, // MyFaces aliases etc. we call encodeBegin/end methods // even if components not in rendered areas. boolean special = isSpecialElement(context, component); if (special) { component.encodeBegin(context); } encodeAjaxChildren(context, component, currentPath, ids, renderedAreas); if (special) { component.encodeEnd(context); } } } else { renderedAreas.add(component.getClientId(context)); renderChild(context, component); } } } {code} Patched version (the isRendered()-condition is moved the the last else-Block before the component will be rendered): public void encodeAjaxComponent(FacesContext context, UIComponent component, String currentPath, Set<String> ids, Set<String> renderedAreas) throws IOException { boolean found = false; boolean limitToList = AjaxContext.getCurrentInstance(context).isLimitToList(); String elementId = component.getId(); String absoluteId = currentPath + elementId; if (!ids.isEmpty()) { // list for rendering may contains absolute id ( best ), // component Id or client ID // String clientId = element.getClientId(context); if (ids.contains(absoluteId) || ids.contains(elementId)) { if (log.isDebugEnabled()) { log.debug(Messages.getMessage( Messages.RENDER_AJAX_AREA_INFO, absoluteId)); } // renderChild(context, element); found = true; } } // if (!found && limitToList && component instanceof NamingContainer && noIdUnderPath(absoluteId + NamingContainer.SEPARATOR_CHAR, ids)) { return; } if (!found && !limitToList && component instanceof AjaxOutput) { if (((AjaxOutput) component).isAjaxRendered()) { // renderChild(context, element); found = true; } } if (!found) { if (component instanceof AjaxChildrenEncoder) { ((AjaxChildrenEncoder) component).encodeAjaxChild(context, currentPath, ids, renderedAreas); } else { // Special case - for control components, not produced // html code - such as message bundles loaders, // MyFaces aliases etc. we call encodeBegin/end methods // even if components not in rendered areas. boolean special = isSpecialElement(context, component); if (special) { component.encodeBegin(context); } encodeAjaxChildren(context, component, currentPath, ids, renderedAreas); if (special) { component.encodeEnd(context); } } } else if (component.isRendered()) { // skip not-rendered components. renderedAreas.add(component.getClientId(context)); renderChild(context, component); } } {code} -- 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

14 years

2
7
0 / 0

[JBoss JIRA] Created: (RF-4903) ScriptUtils: StackOverflowException occurs for cycle references

by Nick Belaevski (JIRA)

ScriptUtils: StackOverflowException occurs for cycle references --------------------------------------------------------------- Key: RF-4903 URL: https://jira.jboss.org/jira/browse/RF-4903 Project: RichFaces Issue Type: Bug Reporter: Nick Belaevski Priority: Minor -- 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

14 years

4
7
0 / 0

[JBoss JIRA] Created: (RF-8067) keyboard navigable rich:datascroller

by Gary Hu (JIRA)

keyboard navigable rich:datascroller ------------------------------------ Key: RF-8067 URL: https://jira.jboss.org/jira/browse/RF-8067 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.2.SR1 Reporter: Gary Hu The rich:datascroller generates the markup html code like this: <td class="dr-dscr-inact rich-datascr-inact" onclick="Event.fire(this, 'rich:datascroller:onscroll', {'page': '1'});">1</td> The code above is not keyboard navigable. For example, it can not be set focus. Can we generate the html markup like the following? <td class="dr-dscr-inact rich-datascr-inact" onclick="Event.fire(this, 'rich:datascroller:onscroll', {'page': '1'});"><a href="javascript:void(0)">1</a></td> The <a> tag will enable it to be keyboard navigable. Furthermore, maybe we can add one property for rich:datascroller to determine if needing to generate keyboard navigable page link or 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

14 years

5
5
0 / 0

[JBoss JIRA] Created: (RF-8425) rich:tooltip performance

by Mark Torres (JIRA)

rich:tooltip performance ------------------------ Key: RF-8425 URL: https://jira.jboss.org/jira/browse/RF-8425 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-output Affects Versions: 3.3.1 Reporter: Mark Torres We have used rich:tooltip in a lot of places within our application. And while profiling, we came to a bottleneck caused by repeated calls to RendererBase.getResource(String resourceURI ) during the constructor of ToolTipRenderer. I think the main issue is the ToolTipRenderer.getRenderer(UIToolTip toolTip) method never caches the subclasses and thus created a lot of HtmlToolTipRendererBlock, HtmlToolTipRenderer objects, and calls to RendererBase.getResource(String resourceURI ). We've overriden the renderer in our environment to use something that caches the subclass and it improved performance a lot. -- 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

14 years

8
12
0 / 0

[JBoss JIRA] Created: (RF-4354) SuggestionBox, Calendar and ComboBox positioning could be fixed in scrollable containers.

by Ilya Shaikovsky (JIRA)

SuggestionBox, Calendar and ComboBox positioning could be fixed in scrollable containers. ----------------------------------------------------------------------------------------- Key: RF-4354 URL: https://jira.jboss.org/jira/browse/RF-4354 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.2.1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Checked with livedemo. Seems that recalculation position on scroll isn't good idea.. But may be we just should close this popups on scroll also as for simple loosing focus. (We could add attribute to make it optionall) Let wait for votes. -- 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

14 years

7
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2010