Has anybody else seen this? When I have an eventlink (and presumably
actionlink and other types of links) with async="true", like this:
Delete...
then when I click OK on the confirmation dialog, the request is sent
BOTH via xhr and as a regular full-page request. (Naturally, the
second one
I did some experimenting and discovered that the confirm mixin works fine
for things like an actionlink, but it doesn't work on a form button. Is
this intended behavior? I was able to hack around it by styling an action
link to look like a button and putting it outside of my form. In this
Hi all,
I've got a pretty simple test project in Tap 5.4.1. Everything works as
expected, but when I add the built-in Confirm mixin to a component form,
the onSuccessFrom... event does not work. The confirm dialog works as
expected, but when I click ok, nothing happens (Other than the co
below, fixes this:
${message:delete}
Likewise, if I remove the confirm mixin and leave the async="true", then
it only sends one xhr event as expected (but without the confirm
bit older version of Tapestry: 5.1.05. There
> is no
> > Tapestry.FORM_VALIDATE_FIELDS_EVENT defined but there are
> > Tapestry.FORM_VALIDATE_EVENT and
> > Tapestry.FIELD_VALIDATE_EVENT
> > which I guess should do the same thing.
> >
> >
> >
> >
.alreadyClickedOnce = false;
},
3000);
}
};
Оригинално писмо
От: Taha Siddiqi tawus.tapes...@gmail.com
Относно: Re: Confirm mixin with form validation errors
До: "Tapestry users"
Изпратено на: Понеделник, 2012, Септемв
x27; is
> not a function
>
> I have to mention I'm on a bit older version of Tapestry: 5.1.05. There is no
> Tapestry.FORM_VALIDATE_FIELDS_EVENT defined but there are
> Tapestry.FORM_VALIDATE_EVENT and
> Tapestry.FIELD_VALIDATE_EVENT
> which I guess should do the same thing.
>
>
>
&
- Оригинално писмо
От: Josh Canfield joshcanfi...@gmail.com
Относно: Re: Confirm mixin with form validation errors
До: Tapestry users
Изпратено на: Петък, 2012, Септември 14 07:07:20 EEST
I don't think this addresses the problem though, right?
If client-side form validation fa
I don't think this addresses the problem though, right?
If client-side form validation fails you still are in a state where you
can't click the submit button again after fixing the error.
Tapestry doesn't have an event for "validation failed", and I don't know of
an approved way to workaround tha
$('#'+specs.id + '
:submit').attr('disabled', 'disabled');
});
}
});
}) ( jQuery );
You need to look for the formprepareforsubmit event.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Confirm-m
{
// use the reponse to update the zone.
zoneManager.processReply(t.responseJSON);
}.bind(this)
});
};
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/problems-getting-rid-of-the-JS-confirm-box-from
/problems-getting-rid-of-the-JS-confirm-box-from-confirm-mixin-tp5444911p5451126.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional
No answers?? :(( Please help!
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/problems-getting-rid-of-the-JS-confirm-box-from-confirm-mixin-tp5444911p5450938.html
Sent from the Tapestry - User mailing list archive at Nabble.com
:
> I have a confirm mixin that I use. I can added it to a and it
> works fine. When I try to use it with a the confirmation
> box is displayed but the cancel button doesn't stop the submit.
>
> t:mixins="Confirm" t:message="Are you sure you want to rem
Have you tried the confirm Mixin in Tapx ?
https://github.com/hlship/tapx/
Shing
--- On Fri, 14/1/11, mwilliam...@kcp.com wrote:
> From: mwilliam...@kcp.com
> Subject: Confirm Mixin
> To: "Tapestry users"
> Date: Friday, 14 January, 2011, 2:01
> I have a confi
I have a confirm mixin that I use. I can added it to a and it
works fine. When I try to use it with a the confirmation
box is displayed but the cancel button doesn't stop the submit.
Dose anyone know how to make this work with a LinkSubmit or know of another
way to do this?
Confirm
e linkZone method sets the onclick function on the object
>>> directly instead of using Event.observe. I haven't looked at it hard
>>> enough to pass judgement but this gives you the opportunity to chain
>>> the onclick handler by saving a copy in your object and replaci
handler by saving a copy in your object and replacing it
>> with your own function. Since you can't enforce ordering for observed
>> events, or prevent them from running maybe this is why onclick is set
>> directly.
>>
>> Josh
>>
>>
>> On Thu, Ma
r by saving a copy in your object and replacing it
> with your own function. Since you can't enforce ordering for observed
> events, or prevent them from running maybe this is why onclick is set
> directly.
>
> Josh
>
>
> On Thu, May 13, 2010 at 5:22 PM, Geoff Callender
observed
events, or prevent them from running maybe this is why onclick is set
directly.
Josh
On Thu, May 13, 2010 at 5:22 PM, Geoff Callender
wrote:
> I have a Confirm mixin that works fine until I put it in a zone. It still
> pops up a confirmation dialog but when Cancel is pressed the
I'm not doing that - Tapestry is when it adds zone support.
On 14/05/2010, at 10:54 AM, Paul Stanton wrote:
> just as an aside, you don't need to prefix your onclick with 'javascript:'
>
> Geoff Callender wrote:
>> > shape="rect" href="./simplewithzone:delete">Delete...
>>
>
> --
just as an aside, you don't need to prefix your onclick with 'javascript:'
Geoff Callender wrote:
Delete...
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...
On Thu, 13 May 2010 21:22:25 -0300, Geoff Callender
wrote:
shape="rect" href="./simplewithzone:delete">Delete...
I'm no JavaScript guru (very far from that, actually), but have you tried
setting onclick to null?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hi
I have a Confirm mixin that works fine until I put it in a zone. It still pops
up a confirmation dialog but when Cancel is pressed the mixin fails to stop the
event.
My mixin adds javascript that observes the element, but the zone seems to upset
it by adding javascript directly to the element
24 matches
Mail list logo
