[JBoss JIRA] Created: (RF-5320) inputNumberSlider: incorrect slider position with rich:tabPanel
by Tsikhon Kuprevich (JIRA)
inputNumberSlider: incorrect slider position with rich:tabPanel
---------------------------------------------------------------
Key: RF-5320
URL: https://jira.jboss.org/jira/browse/RF-5320
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: jsp
myfaces 1.2.5
tomcat 6
Reporter: Tsikhon Kuprevich
Assignee: Nick Belaevski
<body topmargin=20 leftmargin=20>
<h:form id="form">
<rich:tabPanel switchType="client">
<rich:tab label="First">
Here is tab #1
<rich:inputNumberSlider value="20" />
</rich:tab>
<rich:tab label="Second">
Here is tab #2
<rich:inputNumberSlider value="80" />
</rich:tab>
</rich:tabPanel>
<h:commandButton action="submit" value="Submit" />
<a4j:commandButton reRender="form" value="reRender"></a4j:commandButton>
</h:form>
</body>
Click on second tab
see image attached
--
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
13 years, 5 months
[JBoss JIRA] Created: (RF-7134) provide facets for rich:suggestionBox
by nimo stephan (JIRA)
provide facets for rich:suggestionBox
-------------------------------------
Key: RF-7134
URL: https://jira.jboss.org/jira/browse/RF-7134
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.3.0
Reporter: nimo stephan
Priority: Minor
I have a rich:suggestionbox coupling with a query. The query is limited to fetch at most 50 rows.
So I need something like a scroller or a paginator within my suggestionbox, which triggers a action to fetch the next 50 rows and update my suggestionbox with these new fetched rows.
I tried to integrate a a4j:commandLink within my suggestionbox as a footer-facet or header-facet, but rich:suggestionbox cannot render these facets:
<rich:suggestionbox ...>
<f:facet name="footer">
<a4j:commandLink action="#{myBean.nextSuggestions}" value="previous suggestions.." />
</f:facet>
<h:column>
..
</h:column>
<f:facet name="footer">
<a4j:commandLink action="#{myBean.nextSuggestions}" value="next suggestions.." />
</f:facet>
</rich:suggestionbox>
for a example of a Navigation within a suggestionBox, look at
http://toolkit.itmill.com/demo/sampler/#Components/Selects/ComboBoxStarts...
--
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
13 years, 6 months
[JBoss JIRA] Created: (RF-4222) Nice to have multiple events in a4j:support tag
by Jan Hoeve (JIRA)
Nice to have multiple events in a4j:support tag
-----------------------------------------------
Key: RF-4222
URL: https://jira.jboss.org/jira/browse/RF-4222
Project: RichFaces
Issue Type: Feature Request
Reporter: Jan Hoeve
Priority: Minor
in the a4j:support tag, it is now possible enter an event for which you want to occur something (e.g. reRender):
<a4j:support event="onblur" reRender="usernameDecorate"/>
Sometimes it would be very userful if reRenders occur for multiple events.
For example there are two events in which you are interesed: onblur and onkeyup.
The onblur should check where a username containts valid characters (by using a regexp)
The onkeyup should display the current length of the username (in an <h:outputText />)
So, based on above example it would me nice if the support tag supported (hehe) more than one event).
For example: <a4j:support event="onblur,onkeyup" reRender="usernameDecorate"/>
I already tried to create a separate a4j:support for each event, but then only the first one is executed.
--
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
13 years, 7 months
[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, 7 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, 7 months