August 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-4238) rich:panelMenu not clickable

by Rainer Flicker (JIRA)

rich:panelMenu not clickable ---------------------------- Key: RF-4238 URL: https://jira.jboss.org/jira/browse/RF-4238 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: RichFaces 3.2.2.BETA4 JBoss Seam 2.0.2.SP1 JSF 1.2 + Facelets 1.1.14 JBoss 4.2.2.GA JDK 1.5.0_11 Reporter: Rainer Flicker A rich:panelMenu is no expandable and panelMenuItem is not clickable -- 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

17 years, 7 months

2
3
0 / 0

[JBoss JIRA] Resolved: (RF-582) Problem with tree selection

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-582?page=com.atlassian.jira.plugin.... ] Nick Belaevski resolved RF-582. ------------------------------- Resolution: Done Assignee: Tsikhon Kuprevich (was: Nick Belaevski) > Problem with tree selection > --------------------------- > > Key: RF-582 > URL: https://jira.jboss.org/jira/browse/RF-582 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.1.0 > Environment: Mozilla FireFox 2.0.0.6 > Internet Explorer 6 > Internet Explorer 7 > Reporter: Alexander Belov > Assignee: Tsikhon Kuprevich > Fix For: 3.2.2 > > Attachments: 582.avi, src.zip, Test.war > > > I have a problem with tree selection. I shall attach files to reproduse the problem. > Firstly, we must select tree node. Then move selection by "up", "down" keys (it is important). > Then I select one field in the table. There are javascript events on <tr> element of table to move focus. For Firefox bug is reproduced for "Firefox" field. For IE you can select any field. > This time focus is not on tree component. So, press "up", "down" keys and see, that tree selection is moving. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Work started: (RF-582) Problem with tree selection

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-582?page=com.atlassian.jira.plugin.... ] Work on RF-582 started by Nick Belaevski. > Problem with tree selection > --------------------------- > > Key: RF-582 > URL: https://jira.jboss.org/jira/browse/RF-582 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.1.0 > Environment: Mozilla FireFox 2.0.0.6 > Internet Explorer 6 > Internet Explorer 7 > Reporter: Alexander Belov > Assignee: Nick Belaevski > Fix For: 3.2.2 > > Attachments: 582.avi, src.zip, Test.war > > > I have a problem with tree selection. I shall attach files to reproduse the problem. > Firstly, we must select tree node. Then move selection by "up", "down" keys (it is important). > Then I select one field in the table. There are javascript events on <tr> element of table to move focus. For Firefox bug is reproduced for "Firefox" field. For IE you can select any field. > This time focus is not on tree component. So, press "up", "down" keys and see, that tree selection is moving. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (RF-3131) Implement properly requests queue for a AJAX submit.

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-3131?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-3131: ------------------------------- Fix Version/s: 3.3.0 (was: 3.2.2) > Implement properly requests queue for a AJAX submit. > ---------------------------------------------------- > > Key: RF-3131 > URL: https://jira.jboss.org/jira/browse/RF-3131 > Project: RichFaces > Issue Type: Feature Request > Affects Versions: 3.2.0 > Reporter: Alexander Smirnov > Assignee: Alexander Smirnov > Fix For: 3.3.0 > > > For a any cases sequence if ajax requests is important. Existing events queue must be extended to a queue events from different components and send new request only afer previsious is completed. > Other possible option - merge parameters from a different events to a one request ( instead of replace ). > All behaviors ( collect events from one components, queue events and merge ) must be configurable. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-4221) rich:panelMenu has significant memory leak

by Tim Evers (JIRA)

rich:panelMenu has significant memory leak ------------------------------------------ Key: RF-4221 URL: https://jira.jboss.org/jira/browse/RF-4221 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Environment: Using jsf, facelets and richfaces 3.2.0 (I think 3.2.1 has same bug but I can't remember) Reporter: Tim Evers I have a rich:panelMenu for my application's side menu bar. This menu is visible on every page in the system. However, on every render(post/get etc) the memory footprint of IE will go up by around 1.5MB! This behaviour stops immediately when I remove the richfaces panelMenu. There is no dynamic content in the panelMenu. (See attached source) The memory leak is quite large and does not get cleaned up. I have waited up to 5 mins to see if footprint will decrease in size, but it does not. The application it is expected that users will be heavily using the system for most of the day. Thus a 1.5MB increase in the IE memory footprint on every navigation is not going to work. I havn't taken the time to investigate what is causing the leak. But a simple page should be good enough to reproduce the problem. -- 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

17 years, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (RF-4172) column: paging toolbar works incorrectly in the opera 9.51

by Tatyana Romanovich (JIRA)

column: paging toolbar works incorrectly in the opera 9.51 ---------------------------------------------------------- Key: RF-4172 URL: https://jira.jboss.org/jira/browse/RF-4172 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: RF-3.2.2.BETA4 demo site Opera 9.51 Reporter: Tatyana Romanovich Assignee: Nick Belaevski 1. Go to the demo application in the Opera 9.51 2. Select column component 3. Go to the Extended Data Model tab 4. Click Next button on the paging toolBar above dataGrid FAILURE: Next after first page is third 5. Click Previous page button on the paging toolBar above dataGrid FAILURE: first page appears instead of the second pade paging toolbar works incorrectly -- 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

17 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-4194) Sorting for rich:scrollableDataTable-rich:column not working unless column id attribute is set to a certain (evaluated?) value.

by Valery Tcherepanov (JIRA)

Sorting for rich:scrollableDataTable-rich:column not working unless column id attribute is set to a certain (evaluated?) value. ------------------------------------------------------------------------------------------------------------------------------- Key: RF-4194 URL: https://jira.jboss.org/jira/browse/RF-4194 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.1 Environment: Tomcat 6.0, Mojarra 1.2_09-b02 Reporter: Valery Tcherepanov My guess is that column id is being evaluated as part of expression while sorting. Sorting in column in scrollableDataTable is working only in case column id attribute can be evaluated as a property of a row of rich:scrollableDataTable's "value" attribute. In the demo sorting is working because column id matches the property of the table row object : <rich:scrollableDataTable rowKeyVar="rkv" frozenColCount="1" height="400px" width="700px" id="carList" rows="40" columnClasses="col" value="#{dataTableScrollerBean.allCars}" var="category" sortMode="single" binding="#{dataTableScrollerBean.table}" selection="#{dataTableScrollerBean.selection}"> <rich:column id="make"> <f:facet name="header"><h:outputText styleClass="headerText" value="Make" /></f:facet> <h:outputText value="#{category.make}" /> </rich:column> ... value="#{dataTableScrollerBean.allCars}" var="category" rich:column id="make" "category" here does have "make" property, sorting works OK, but if you change column id for something else, "noMatch" for instance, the column wouldn't be sortable anymore. This seems to be the source of other related issues like Sorting feature doesn't work for dynamic columns(rich:columns) https://jira.jboss.org/jira/browse/RF-2413. That bug is marked as closed, but I don't see how I can provide correct column ids for dynamic columns and not really sure dynamic columns issue was resolved. -- 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

17 years, 7 months

4
7
0 / 0

[JBoss JIRA] Closed: (RF-4200) combobox: 2nd calling of "showList()" JS API leads to component's popup list hiding.

by Mikhail Vitenkov (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4200?page=com.atlassian.jira.plugin... ] Mikhail Vitenkov closed RF-4200. -------------------------------- Verified at 3.2.2.BETA4 > combobox: 2nd calling of "showList()" JS API leads to component's popup list hiding. > ------------------------------------------------------------------------------------- > > Key: RF-4200 > URL: https://jira.jboss.org/jira/browse/RF-4200 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: IE6, IE7, FF 3.1, Safari 3.1, Opera 9.51(3.2.2.BETA4) > Reporter: Mikhail Vitenkov > Assignee: Mikhail Vitenkov > Fix For: 3.2.2 > > > # Add rich:combobox with "comboboxID" id on the page; > # Add following link: > <a4j:commandLink onclick="$('formID:comboboxSubviewID:comboboxID').component.showList()" value="showList"> > </a4j:commandLink> or > <a4j:commandLink onclick="#{rich:component('comboboxID')}.showList()" value="showList"> > </a4j:commandLink> > # Navigate on the page; > # Call showList() component's JS API by click "showList" link. > # Repeat previous step. > Actual behavior: > Popup comboboxe's list disappears. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (RF-4201) combobox: when popup list is called by showList() JS API, click out the component doesn't hide popup list.

by Mikhail Vitenkov (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4201?page=com.atlassian.jira.plugin... ] Mikhail Vitenkov closed RF-4201. -------------------------------- Verified at 3.2.2.BETA4 > combobox: when popup list is called by showList() JS API, click out the component doesn't hide popup list. > ---------------------------------------------------------------------------------------------------------- > > Key: RF-4201 > URL: https://jira.jboss.org/jira/browse/RF-4201 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: IE6, IE7, FF 3.1, Safari 3.1, Opera 9.51(3.2.2.BETA4) > Reporter: Mikhail Vitenkov > Assignee: Mikhail Vitenkov > Fix For: 3.2.2 > > > # Call rich:combobox component's popup list by "showList()" JS API calling. > # Click out the component. > Actual behavior: > Popup list is shown. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (RF-4203) combobox: enable() & disable() JS API using leads to changing style(font color: grey->dark) of defaultLabel, defined in corresponding attribute.

by Mikhail Vitenkov (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4203?page=com.atlassian.jira.plugin... ] Mikhail Vitenkov closed RF-4203. -------------------------------- > combobox: enable() & disable() JS API using leads to changing style(font color: grey->dark) of defaultLabel, defined in corresponding attribute. > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: RF-4203 > URL: https://jira.jboss.org/jira/browse/RF-4203 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: IE6, IE7, FF 3.1, Safari 3.1, Opera 9.51(3.2.2.BETA4) > Reporter: Mikhail Vitenkov > Assignee: Mikhail Vitenkov > Priority: Trivial > Fix For: 3.2.2 > > > Precondition: all attributes defined styles & style classes was removed from <rich:combobox tag; <style> section is empty; > Step 1. Navigate on page with combobox. > Step 2. Call enable() JS API by click on "enable" link: > <a4j:commandLink onclick="$('formID:comboboxSubviewID:comboboxID').component.enable()" value="enable"> > </a4j:commandLink> > Step 3. Call disable() JS API by click on "disable" link: > <a4j:commandLink onclick="$('formID:comboboxSubviewID:comboboxID').component.disable()" value="disable"> > </a4j:commandLink> > Actual behavior: > After Step 2: default label changes it's font color from "grey" to "black". > After Step 3: default label changes it's font color from "black" to "grey". Under Safari 3.1 default label is disappeared. -- 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

17 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2008