Sounds like a bug although I don't understand yet why it would not work. Please
open an issue.
On Jan 27, 2012, at 10:11 PM, Yohan Yudanara wrote:
> Thank you for your fast reply :)
>
> First, I want to say sorry because I'm copy pasting your
> DisableAfterSubmit.java and DisableAfterSubmit
Thank you for your fast reply :)
First, I want to say sorry because I'm copy pasting your
DisableAfterSubmit.java and DisableAfterSubmit.js.
When I was trying to use whole flowlogix library, I have difficulties fix
my pom.xml because many dependencies required by flowlogix when I run "mvn
jetty:ru
As I said before i never did extensive tests with client validation, but it
should work.
What exactly isn't working? Are the popups not showing up?
Is it working differently if the mixin isn't there?
Can you post your template / code? And if you really think this is a bug feel
free to open
I'm sorry to resurrect this thread :)
I've tried DisableAfterSubmit with Tapestry 5.3.1, it works great.
But the client side validation is not working. It seems client side
validation is not triggered at all when I'm using DisableAfterSubmit mixins.
Did you also having the same experience ? or did
Submitted JIRA case 2787 w/ code.
On Mon, Nov 21, 2011 at 8:21 PM, hongdengdao wrote:
> great !!
> thanks for sharing!!
>
>
> On 2011年11月22日 06:59, Lenny Primak wrote:
>
>> I just did a quick test with form/zone/clientValidations and the mixin
>> works correctly.
>>
>> On Nov 21, 2011, at 5:45
great !!
thanks for sharing!!
On 2011年11月22日 06:59, Lenny Primak wrote:
I just did a quick test with form/zone/clientValidations and the mixin works
correctly.
On Nov 21, 2011, at 5:45 PM, Lenny Primak wrote:
I see...
I actually never tried forms with client-side validation with the mixin.
On Mon, 21 Nov 2011 22:27:50 -0200, Ray Nicholus
wrote:
Thiago or Howard:Is there any chance Tapestry will natively prevent
multiple form submissions in a future version?
Adding it as a default behavior may not be the best option, specially with
a JavaScript-only solution. On the other ha
Thiago or Howard:Is there any chance Tapestry will natively prevent
multiple form submissions in a future version?
On Mon, Nov 21, 2011 at 4:59 PM, Lenny Primak wrote:
> I just did a quick test with form/zone/clientValidations and the mixin
> works correctly.
>
> On Nov 21, 2011, at 5:45 PM, Len
I just did a quick test with form/zone/clientValidations and the mixin works
correctly.
On Nov 21, 2011, at 5:45 PM, Lenny Primak wrote:
> I see...
> I actually never tried forms with client-side validation with the mixin.
> If it doesn't work, please feel free to submit an issue, even better a
I see...
I actually never tried forms with client-side validation with the mixin.
If it doesn't work, please feel free to submit an issue, even better a patch
with tests, if required.
On Nov 21, 2011, at 5:15 PM, hongdengdao wrote:
> sorry , still confused, in your code , you bind click event
sorry , still confused, in your code , you bind click event , but when
it's a link submit , you click it , if has a client validation error ,
it will still submit?
thanks for you patient.
On 2011年11月22日 06:02, Lenny Primak wrote:
It's _after_ submit. It doesn't have to do anything with vali
Sure I'd like to contribute. Gotta work on that documentation and there are
other generic things in there that would be useful in tapestry-core.
On Nov 21, 2011, at 5:09 PM, "Thiago H. de Paula Figueiredo"
wrote:
> On Mon, 21 Nov 2011 19:39:49 -0200, François Facon
> wrote:
>
>> Nice Wor
On Mon, 21 Nov 2011 19:39:49 -0200, François Facon
wrote:
Nice Work Lenny.
Agreed. :) Would you like to have it included in Tapestry-core? ;-) You
can always donate if you want. ;)
I just discovered your mixin
http://code.google.com/p/flowlogix/source/browse/services/src/main/java/com/
I'm wondering if tapestry should natively prevent multiple submits instead.
That way, we won't need a mixin. This seems like a good idea, unless
there is some case where multiple submits would be desirable, but I can't
think of any.
On Mon, Nov 21, 2011 at 3:56 PM, Lenny Primak wrote:
> Multipl
It's _after_ submit. It doesn't have to do anything with validation.
On Nov 21, 2011, at 4:57 PM, hongdengdao wrote:
> when validate failed, disable or enable?
>
> On 2011年11月22日 05:39, François Facon wrote:
>> Nice Work Lenny.
>>
>> I just discovered your mixin
>> http://code.google.com/p
when validate failed, disable or enable?
On 2011年11月22日 05:39, François Facon wrote:
Nice Work Lenny.
I just discovered your mixin
http://code.google.com/p/flowlogix/source/browse/services/src/main/java/com/flowlogix/web/mixins/DisableAfterSubmit.java
And his related prototype file
http://code
Multiple submits are allowed in the mixin. Perhaps I am misunderstood your us
case.
On Nov 21, 2011, at 4:51 PM, Ray Nicholus wrote:
> Looks interesting, and I do think a mixin is a good way to go here.
> However, I'm trying to think of a case where multiple submits would be
> permissible.
er natively, not naively.
On Mon, Nov 21, 2011 at 3:51 PM, Ray Nicholus wrote:
> Looks interesting, and I do think a mixin is a good way to go here.
> However, I'm trying to think of a case where multiple submits would be
> permissible. If there is no such case, perhaps it would be ideal for t
Looks interesting, and I do think a mixin is a good way to go here.
However, I'm trying to think of a case where multiple submits would be
permissible. If there is no such case, perhaps it would be ideal for this
to be handled naively by Tapestry. Has there been any discussion along
these lines?
Thanks for the kind words Francois, although the documentation is still
desperately lacking.
On Nov 21, 2011, at 4:39 PM, François Facon wrote:
> Nice Work Lenny.
>
> I just discovered your mixin
> http://code.google.com/p/flowlogix/source/browse/services/src/main/java/com/flowlogix/web/mixi
Nice Work Lenny.
I just discovered your mixin
http://code.google.com/p/flowlogix/source/browse/services/src/main/java/com/flowlogix/web/mixins/DisableAfterSubmit.java
And his related prototype file
http://code.google.com/p/flowlogix/source/browse/services/src/main/resources/com/flowlogix/web/mixi
Perhaps there are better solutions, but I solved it via DisableAfterSubmit
mixin in my FlowLogix utility module http://code.google.com/p/flowlogix/
On Nov 21, 2011, at 4:07 PM, Ray Nicholus wrote:
> I'm sure I am not the first one to encounter this problem, and before I go
> about re-inventing
Have a look at Jumpstart.
http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/creatingmixins1
2011/11/21 Ray Nicholus :
> I'm sure I am not the first one to encounter this problem, and before I go
> about re-inventing the wheel, I wanted to see if this is something that has
> al
I'm sure I am not the first one to encounter this problem, and before I go
about re-inventing the wheel, I wanted to see if this is something that has
already been elegantly solved in the tapestry circle. Anyone?
);
});
Regards,
Raul.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-Prevent-multiple-form-submits-tp5477609p5484072.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
Raul.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-Prevent-multiple-form-submits-tp5477609p5484015.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail:
er an ajax submit
completes (or whether I should even show it for those forms). Wonder if a
form has it's zone in $T()...
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-Prevent-multiple-form-submits-tp5477609p5482199.html
Sent from the Tapestry Users mailing
cally only on normal submits).
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-Prevent-multiple-form-submits-tp5477609p5478598.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
---
Have a look at this example (if javascript is an option):
http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/creatingmixins1
Sigbjørn Tvedt
On Mon, Aug 30, 2010 at 1:57 PM, joris wrote:
> Yes, the client validation is the biggest problem. I tried something
> similar. I disabl
Yes, the client validation is the biggest problem. I tried something
similar. I disable the submit button for 2 seconds, to work around the
client site validation problem. I get it work for IE and Firefox, but in
Chrome it doesn't work.
Event.observe(window, 'load', function() {
$$("inpu
not submit due to an
error (probably listening to wrong event).
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/T5-Prevent-multiple-form-submits-tp5477609p5477739.html
Sent from the Tapestry Users mailing list a
Hello,
I try to prevent multiple form submits, if the user clicks more then
ones a submit button.
Is there a build in way for this problem?
Or is there a preferred solution?
Thanks.
Joris
-
To unsubscribe, e-mail: users
32 matches
Mail list logo
