Yep, that's the default (but I tried it anyway.) It appears to be
working, since causing a javascript error does abort properly. Odd
that it works properly for non-ajax requests, too.
Perhaps I'll try a simple case and see if that works.
Norman Franke
Answering Service for Directors, Inc.
ww
did you try dojo.event.connect("before", dojo.byId ?
2008/10/27 Norman Franke <[EMAIL PROTECTED]>
> I've now upgraded to T4.1.6 and the problem remains on Firefox, IE and
> Safari. Here is how I coded it:
>
> dojo.event.connect(dojo.byId('delete'), 'onclick',
>function (evt) {
>
I've now upgraded to T4.1.6 and the problem remains on Firefox, IE and
Safari. Here is how I coded it:
dojo.event.connect(dojo.byId('delete'), 'onclick',
function (evt) {
if (!confirm('Are you sure?')) {
dojo.event.browser.stopEvent(evt);
I did that exact same thing and it did submit. Very strange! I'm using
Firefox 3.0 and T4.1.5. Where did you put the connect? I tried at the
end of the body and outsize the body, before the
Norman Franke
Answering Service for Directors, Inc.
www.myasd.com
On Oct 24, 2008, at 5:00 PM, Andrea
just tried something like
dojo.event.connect(dojo.byId('fepSubm'),'onclick',
function(e){dojo.event.browser.stopEvent(e);});
and it prevented the submit
On Fri, Oct 24, 2008 at 11:29 PM, Norman Franke <[EMAIL PROTECTED]> wrote:
> According to the documentation, before is the default. Either way, i
According to the documentation, before is the default. Either way, it
still doesn't work. The ajax submit is still called. If I call a non-
function, then it doesn't work, e.g. "foobar()". It generates an error
in the console, but does stop.
Norman Franke
Answering Service for Directors, Inc
sorry - dojo.event.connectBefore is what you need :)
On Fri, Oct 24, 2008 at 11:00 PM, Norman Franke <[EMAIL PROTECTED]> wrote:
> I'm using T4.1.5 which has dojo 0.4.x and no dojo. event.stopEvent. I tried
> dojo.event.browser.stopEvent but that didn't work. Nor did e.stopPropigation
> or e.preven
I'm using T4.1.5 which has dojo 0.4.x and no dojo. event.stopEvent. I
tried dojo.event.browser.stopEvent but that didn't work. Nor did
e.stopPropigation or e.preventDefault. In fact, I tried all three
together (and separate) and it still fires.
Norman Franke
Answering Service for Directors,
You can also just use @EventListener. Call a Javascript operation to display
the status and hook up your EventListener to an arbitrary Javascript call.
Kalle
On Fri, Oct 24, 2008 at 12:31 PM, Andreas Andreou <[EMAIL PROTECTED]>wrote:
> dojo.event.connect to it and in there do dojo.event.stopEven
dojo.event.connect to it and in there do dojo.event.stopEvent (or
something like that) if you
dont want to go on with the submit
On Fri, Oct 24, 2008 at 10:22 PM, Norman Franke <[EMAIL PROTECTED]> wrote:
> Thanks. I apparently forgot to look at contrib.
>
> As for the second question, I'd love to,
Thanks. I apparently forgot to look at contrib.
As for the second question, I'd love to, but how can I update the
formhidden section of the form such that my controls (that were
created via AJAX) will be sent on the next AJAX action? If I don't
update the entire form, I never get the values
To answer your initial question, just use contrib:ajaxStatus from
http://tapestry.apache.org/tapestry4.1/tapestry-contrib/componentreference/ajaxstatus.html
For the second, why not update only the part in question?
On Fri, Oct 24, 2008 at 9:22 PM, Norman Franke <[EMAIL PROTECTED]> wrote:
> I sort
I sort of have it working by doing an "onclick" and relying on the
entire form to update, which resets my div.
But that brings up another point. I want to AJAX fetch a list of
elements with a checkbox. Is there a better way to do this than by
setting the entire form as one of the updateComp
13 matches
Mail list logo
