Re: T4 AutoCompleter onkeypress event never triggered

2008-02-28 Thread Andreas Andreou
I'd connect a key handler somewhere higher at the html hierarchy (perhaps at the containing div or form level) and do something like: dojo.event.connect(dojo.byId('container'), 'onkeydown', function(e) { if (e.keyCode==13) // or use e.target to refine the condition for ENTER trapping

Re: T4 AutoCompleter onkeypress event never triggered

2008-02-28 Thread Paul Stanton
Well that works for FireFox, but not IE. in IE the event listener is never triggered so I'm assuming it has trouble propagating the event handler from the container to the child. I worked out another solution yesterday though, it's pretty exhaustive but it works: 1. this function finds the

Re: T4 AutoCompleter onkeypress event never triggered

2008-02-27 Thread Paul Stanton
looking a bit deeper, the script for registering the onValueChanged event looks like this: tapestry.cleanConnectWidget(addrSearch, onValueChanged, formEvent1152711902); tapestry.formEvent1152711902=function(e){ // do some stuff }; tapestry.connectWidget(addrSearch, onValueChanged,

T4 AutoCompleter onkeypress event never triggered

2008-02-21 Thread Paul Stanton
Hi all, I'm using the AutoCompleter component and noticed that hitting the enter key submits the form in IE. I've tried disabling keyCode 13 but since the component actually creates a select field, onkeypress, onkeydown and onkeyup are never triggered! Does anyone know of a way to disable