Re: datefield onchange

2012-08-20 Thread Paul Stanton
It seems I have to combine a both approaches to achieve what I need - whether or not this should be improved within the tapestry framework is up for debate onchange="alert('1 onchange attribute');" /> $("selectedDateElem").observe("change", function(event) {

Re: datefield onchange

2012-08-20 Thread François Facon
Hi Paul In 5.3 DatePicker (DateField.js) save informations in Tapestry.currentFocusField and fire the Tapestry.FOCUS_CHANGE_EVENT like this document.fire(Tapestry.FOCUS_CHANGE_EVENT, this.field); what about listen to tapestry:focuschange like the Tapestry.FieldEventManager (tapestry.js) do? doc

Re: datefield onchange

2012-08-20 Thread Paul Stanton
Thanks brian, but i am assuming/hoping that the fix for issue 1844 allows me to do something a little more obvious. if not, i'm sure to use your solution. p. On 20/08/2012 9:16 PM, Bryan Lewis wrote: Ah yes, the problem of not catching changes made by clicking on the little calendar icon. He

Re: datefield onchange

2012-08-20 Thread Bryan Lewis
Ah yes, the problem of not catching changes made by clicking on the little calendar icon. Here's a crude work-around I'm using in 5.2.6, catching the click event. String scriptlet = "Event.observe('" + dateFieldId + "-trigger', 'click', function() { setChanged(true); });" javaScriptSuppor

Re: datefield onchange

2012-08-20 Thread Paul Stanton
I've just tried that too howard, $("selectedDate").observe("change", function(event) { alert('here'); }); However this is only fired when you type into the input field and the click out (blur) .. not when a date is selected via the

Re: datefield onchange

2012-08-19 Thread Howard Lewis Ship
Have you tried observing the change event? The onchange attr may get overwritten by the date field JS. On Sunday, August 19, 2012, Paul Stanton wrote: > Hi all, > > I've found the bug report: https://issues.apache.org/** > jira/browse/TAP5-1844 >

datefield onchange

2012-08-19 Thread Paul Stanton
Hi all, I've found the bug report: https://issues.apache.org/jira/browse/TAP5-1844 .. and am using tapestry 5.3.3 so the fix has been applied, however I still can't get tapestry to call my 'onchange' handler. Is there some extra wiring required? Thanks, Paul. -