I thought t:clientEvent should be just 'click', not 'onclick'. Unless
prototype Event.observe takes both or something.
In any case I think you're doing this the long way. Why not completely do
the confirm in javascript instead of going to the server in both cases? So
if they click cancel on the
Hi,
I found this thread
http://tapestry-users.832.n2.nabble.com/Confirm-mixin-won-t-cancel-when-in-zone-td5048950.html#a5048950
but it's not exactly what I'm trying to do because it's for eventlinks.
I'm a bit stuck getting the pieces of a custom mixin I'm trying to write
to work, and my tale
