[JBoss JIRA] Created: (RF-1107) Scrollable dataTable. Header scrolled badly on TAB button.
by Ilya Shaikovsky (JIRA)
Scrollable dataTable. Header scrolled badly on TAB button.
----------------------------------------------------------
Key: RF-1107
URL: http://jira.jboss.com/jira/browse/RF-1107
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Environment: FF 2.0.0.6
Reporter: Ilya Shaikovsky
Assigned To: Konstantin Mishin
Fix For: 3.2.0
Two use-cases failed:
"case - 1.png"
frozenColCount=0
all the columns with inputs
last columns aren't in visible part
When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!)
"case - 2.png"
frozenColCount=2
all the columns with inputs
last columns aren't in visible part
I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case).
--
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
12 years, 7 months
[JBoss JIRA] Created: (RF-2494) Multiple clicks on a particular Tree node doesn't fire nodeSelectListener method for each click (only for the first time)
by Mareks Malnacs (JIRA)
Multiple clicks on a particular Tree node doesn't fire nodeSelectListener method for each click (only for the first time)
-------------------------------------------------------------------------------------------------------------------------
Key: RF-2494
URL: http://jira.jboss.com/jira/browse/RF-2494
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4
Reporter: Mareks Malnacs
Here is the problem:
-construct Tree with recursiveTreeNodesAdaptor, switchType="client" and ajaxSubmitSelection="true"
-add method binding to nodeSelectListener so that every click on tree node executes some business method (for tests - simple log message displaying clicked node id for example)
Result:
-tree is rendered fine, clicks on different node elements in a tree executes specified nodeSelectListener method also fine, BUT when user clicks same tree node twice, nodeSelectListener method is not fired - to get it fired for this particular node again You have to click some other node in a tree and then click back on desired one. Shouldn't nodeSelectListener be fired on each click on a tree node even though user is clicking on the same node multiple times ?
--
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
[JBoss JIRA] Created: (RF-4192) Add "noDataLabel" to rich:dataTable for purposes of display a message if the dataTable is empty
by Chris Simons (JIRA)
Add "noDataLabel" to rich:dataTable for purposes of display a message if the dataTable is empty
-----------------------------------------------------------------------------------------------
Key: RF-4192
URL: https://jira.jboss.org/jira/browse/RF-4192
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.1, 3.2.0.SR1, 3.2.0, 3.1.6, 3.1.5, 3.1.4
Reporter: Chris Simons
Priority: Optional
An excellent, small addition to rich:dataTable would allow for a textual message to be displayed in the event that a dataTable is empty.
For example:
<rich:dataTable id="myTable" noDataLabel="#{messages['dataTable.noData']}" ....> </rich:dataTable>
When the condition is true that the underlying data model or list is empty, the message would display in one row that spans the entire dataTable. The headers and dataTable title would still remain.
Please vote for this issue if you would like to see this feature added.
--
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, 3 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, 8 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, 8 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, 8 months