You should expect it to behave exactly the same way as it would if you had
just submitted the form normally without any ajax stuff.
In your case you are probably looking for the value to be in a temporary
property you use when iterating over your values in a For loop - when really
the value will
I grabbed the latest snapshot and now the callback is getting called for
all of my inputs. Thank you very much.
I still get NULL as the value, but I think that's my fault. I'm going
to have to do some serious thinking about how this page works.
For my understanding, when the "onchange" even
Yes the feeling was correct. The snapshot version should be fixed and
deployed already.
Sorry for the inconvenience, you caught me in the middle of some larger
changes and I guess this use case was a victim.
On 5/3/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Hmm...I have a bad feeling this i
Hmm...I have a bad feeling this is my fault - obviously it should work fine
as-is. I'll take a look...
On 5/3/07, Tony Nelson <[EMAIL PROTECTED]> wrote:
A little additional info.. when I change the value on any of the inputs
beyond the first one, it is causing the form to be submitted, it just
A little additional info.. when I change the value on any of the inputs
beyond the first one, it is causing the form to be submitted, it just
doesn't call my EventListener method. Also, I am using the latest
(today's) Tapestry build.
Thanks again
Tony
Tony Nelson wrote:
Is it possible to use
Is it possible to use an EventListener in a component that is displayed
multiple times on a page?
Specifically, I would like a component that has 2 inputs, and when the
1st one is updated an onchange event causes the 2nd component to update
it's value. From my testing, it appears that only th
