[
https://jira.jboss.org/jira/browse/RF-8199?page=com.atlassian.jira.plugin...
]
Jay Balunas resolved RF-8199.
-----------------------------
Fix Version/s: 3.3.3.BETA1
Resolution: Done
This appears to have been resolved for the 3.3.3.BETA1 release. Sean if that is not the
case please update.
calendar documentation contains wrong example
---------------------------------------------
Key: RF-8199
URL:
https://jira.jboss.org/jira/browse/RF-8199
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: doc
Affects Versions: 3.3.2.SR1
Reporter: Ilya Shaikovsky
Assignee: Sean Rogers
Fix For: 3.3.3.BETA1
I the text from the buide highlighted below we getting example which not works since
3.3.0 and then making a not that it not works :) I prefer to just write actually working
sample with "onchanged" event. And dateselected could be mentioned but not too
wide as it not usefull in common use-cases after its functionality change
===============================
"ondateselect" attribute is used to define an event that is triggered before
date selection.
The "ondateselected" attribute is used to define an event that is triggered
after date selection.
For example, to fire some event after date selection you should use <a4j:support> .
And it should be bound to "ondateselected" event as it's shown in the
example below:
...
<rich:calendar id="date" value="#{bean.dateTest}">
<a4j:support event="ondateselected"
reRender="mainTable"/>
</rich:calendar>
...
Note:
When a timePicker was fulfilled, the "ondateselected" attribute does not allow
you to submit a selected date. It happens because this event rose when the date is
selected but the input hasn't been updated with new value yet.
==================================
--
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