[JBoss JIRA] Created: (RF-970) DDMenu in Toolbar and Opera
by Carsten H?hne (JIRA)
DDMenu in Toolbar and Opera
---------------------------
Key: RF-970
URL: http://jira.jboss.com/jira/browse/RF-970
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.0
Reporter: Carsten H?hne
Priority: Minor
The dropDown Menu does not work in Opera (9.23) in this constellation:
<ui:component ...>
<rich:toolBar>
<h:form>
<rich:toolBarGroup >
<rich:dropDownMenu value="Collection" >
<rich:menuItem value="List working collection" action="list" />
</rich:dropDownMenu>
</rich:toolBarGroup>
</h:form>
<rich:toolBarGroup location="right">
<h:form>[....]
</h:form>
</rich:toolBarGroup>
</rich:toolBar>
</ui:component>
But it works with IE and Firefox.
If the form is put into the toolbargroup, than the menue is functioning in opera. Or if you put the form around the whole toolbar it works also.
--
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
13 years, 10 months
[JBoss JIRA] Created: (RF-9426) Check iteration state saving for facets of dataTable component
by Nick Belaevski (JIRA)
Check iteration state saving for facets of dataTable component
---------------------------------------------------------------
Key: RF-9426
URL: https://jira.jboss.org/browse/RF-9426
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: component-tables, performance
Affects Versions: 4.0.0.Milestone3
Reporter: Nick Belaevski
Assignee: Konstantin Mishin
Fix For: 4.0.0.Milestone4
Here is the excerpt from the letter I've just received:
>>>> There is memory leak in UIDataAdaptorBase/rich:dataTable.
>>>> It affects:
>>>> - external filtering (input in "header" facet)
>>>> - embedded filtering ("filterBy" column attribute) - facet
>>>> "filterValueInput" is added internally
>>>>
>>>> Code in UIDataAdaptorBase#saveChildState:
>>>> itr = c.getFacets().values().iterator();
>>>> while (itr.hasNext()) {
>>>> saveChildState(faces, (UIComponent) itr.next(), childState);
>>>> }
>>>>
>>>> Column facet state is saved in the view for each row.
>>>>
>>>> For the table with 500 rows 5 columns with filtering that resulst in
>>>> 350kB
>>>> of extra view size.
>>>> UIDataAdaptorBase$DataState size - 350 kB
>>>> There are 2500 (500 rows * 5 columns) instances of
>>>> UIDataAdaptorBase$SavedState.
>>>>
>>>> The same table without filtering does not have this issue and
>>>> UIDataAdaptorBase$DataState size is 1 kB.
>>>>
This affects 3.x. Please check if 4.x is affected by 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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (RF-3632) Lost input focus after rerendering parent form
by Benno Markiewicz (JIRA)
Lost input focus after rerendering parent form
----------------------------------------------
Key: RF-3632
URL: http://jira.jboss.com/jira/browse/RF-3632
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.1
Environment: RF 3.2.1.CR3
IE 6
Firefox 2.0.0.11
Java 1.5.0_15
jetty-6.1.9
WinXP SP2
Reporter: Benno Markiewicz
A control within a parent form looses its focus when the parent form is rerendered. The rerendering was forced by an event fired from the child control. See the source (based on http://livedemo.exadel.com/richfaces-demo/richfaces/support.jsf?c=support)
<h:form id="myform">
<h:panelGrid columns="2">
<h:inputText id="myinput" value="#{userBean.name}">
<a4j:support event="onkeyup" reRender="myform" />
</h:inputText>
<h:outputText id="outtext" value="#{userBean.name}" />
</h:panelGrid>
</h:form>
Notice the difference. Instead of "outtext" "myform" will be rerendered.
Background: You have a detail form with several components. Every control on the form changes the internal state. The view represents the actual state, so the whole form has to be rerendered. But when you rerender the parent form, the focus/selection state of the actual component is lost.
--
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
13 years, 10 months