Hi Jesse,
I have the same problem with refresh. I was looking at the link you
sent and notice that the signatures for cancel and refresh are both:
refresh:function(form, submitName)
and
cancel:function(form, submitName)
while the submit function is:
submit:function(form, submitName, parms)
The javascript call on my submit button is:
tapestry.form.cancel('Form','Submit_0',{"async":true,"json":false,"url":"/MyPage,$Component.$Form.sdirect?state:=BrO0ABXcPAAAAAQAACG1vZHVsZUlkc3IADmphdmEubGFuZy5Mb25nO4vkkMyPI98CAAFKAAV2YWx1ZXhyABBqYXZhLmxhbmcuTnVtYmVyhqyVHQuU4IsCAAB4cD5FVuANcyrP"})"
As you can see the call to cancel includes three parameters but the
cancel function defines only two and calls the submit function with
only two parameters. I'm not a javascript expert and have never used
it extensively, but it seems to me both cancel and refresh should take
three parameters and pass the third parameter on to submit. It would
make sense that my request is not being don asynchronously since the
third parameter is the one that instructs it to do it asynchronously.
Am I on the right track? Is this a bug? Or am I not understanding the
javascript correctly?
On 2/8/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I would look at the functions here:
http://tapestry.apache.org/tapestry4.1/javascript/form.html
That page also provides handy links to online source views of the
files they document so it should be easy to use as a reference.
On 2/8/07, Daniel Tabuenca <[EMAIL PROTECTED]> wrote:
> Any tips on how to debug this on the client side? I can use firebug,
> but where do I break to see where the decision is made to not do it
> via an ajax request?
>
>
> On 2/8/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > None. Maybe an unfortunate combination of the form and submit button
> > being async ? (potential bug , not sure)
> >
> > On 2/7/07, Daniel Tabuenca <[EMAIL PROTECTED]> wrote:
> > > I have a simple form:
> > >
> > > <form jwcid="@Form" delegate="ognl:delegate" async="true"
> > > listener="listener:submit" cancel="listener:cancel">
> > >
> > > with a simple cancel button:
> > >
> > > <input jwcid="@Submit" async="true" submitType="cancel" value="Cancel"/>
> > >
> > >
> > > When it renders the page tapestry generates:
> > >
> > > <input type="submit"
> > >
onclick="tapestry.form.cancel('Form','Submit_0',{"async":true,"json":false,"url":"/residency/residency/html/Login,$PasswordRecover.$Form.sdirect?state:residency/html/Login=BrO0ABXcPAAAAAQAACG1vZHVsZUlkc3IADmphdmEubGFuZy5Mb25nO4vkkMyPI98CAAFKAAV2YWx1ZXhyABBqYXZhLmxhbmcuTnVtYmVyhqyVHQuU4IsCAAB4cDsrzkil5pr3"})"
> > > value="Cancel" id="Submit_0" name="Submit_0"/>
> > >
> > > However.. this seems to not be donde throuh an asynchronous request
> > > and the entire page loads. Any ideas why this could be happening?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
