if you want to stop the event try this - even works with observe / on
methods
function handle_submit( event )
{
event.stop();
//all other code
}
$("formid").observe("submit",handle_submit);
Jason Westbrook | T: 313-799-3770 | jwestbr...@gmail.com
On Wed, Sep 26, 2012 at 9:58 PM, kstubs <kst...@gmail.com> wrote:
> Yes, I'm just wondering if the clever .on method elminiates this, and
> perhaps it does not. I am finding that if I want to intercept the Submit
> event, then I have to bindAsEventListener so that I can actually trap the
> submit event and stop it (then do my own thing with the form and submit to
> my own custom (Ajax) script.
>
> Karl..
>
>
> On Wednesday, September 26, 2012 2:30:34 PM UTC-7, Jason wrote:
>
>>
>> my interpretation of the documentation is as follows
>>
>> if that is inside a class then you might have to use bind to make sure
>> that "this" still refers to your class instance - vs "this" would refer to
>> the element the event was fired on
>>
>>
>> Jason Westbrook | T: 313-799-3770 | jwest...@gmail.com
>>
>>
>>
>> On Wed, Sep 26, 2012 at 1:30 PM, kstubs <kst...@gmail.com> wrote:
>>
>>> OK, I have something like this:
>>>
>>> this.zz__**handleCommentFormSubmit = this.comment_form.on('submit',
>>> this.__**handleCommentFormSubmit);
>>>
>>> It is unclear to me, reading from the API, if I must bind or
>>> bindAsEventListener or leave it as it, the method:
>>> this.__**handleCommentFormSubmit,
>>> in the above statement.
>>>
>>> Karl..
>>>
>>> FYI.. "this" refers to my class.
>>>
>>>
>>> On Wednesday, September 26, 2012 12:08:31 PM UTC-7, kstubs wrote:
>>>>
>>>> OK, I understand what needs to be done, I just need to bind the form
>>>> submit each time it is created and then destroy it, the form and the
>>>> handler.
>>>>
>>>> Thanks,
>>>> Karl..
>>>>
>>>> On Wednesday, September 26, 2012 10:16:30 AM UTC-7, Jason wrote:
>>>>>
>>>>>
>>>>> my suggestion is to setup a function as the event handler and on form
>>>>> creation add the submit observe - also if you are worried about memory
>>>>> leaks remove all the child elements of the container on new form creation
>>>>>
>>>>> ie
>>>>>
>>>>> function handle_submit( event) {
>>>>> // handle submit action
>>>>> }
>>>>>
>>>>> $("container").childElements()****.invoke("remove");
>>>>> var form = new Element("form");
>>>>>
>>>>> form.observe("submit",handle_**s**ubmit);
>>>>>
>>>>> // add more elements to the form
>>>>>
>>>>> $("container").update(form);
>>>>>
>>>>> Jason Westbrook | T: 313-799-3770 | jwest...@gmail.com
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 26, 2012 at 6:24 AM, Walter Lee Davis
>>>>> <wa...@wdstudio.com>wrote:
>>>>>
>>>>>>
>>>>>> On Sep 26, 2012, at 5:00 AM, kstubs wrote:
>>>>>>
>>>>>> > Does a form submit bubble up to the containing element?
>>>>>> > I'd like to capture form submit on a container div for a form
>>>>>> submit. Reason being: I create the form on the fly based on whichever
>>>>>> child element the user has selected (if any). I'd like to add a form
>>>>>> submit handler to the container, much like I do for click events, to
>>>>>> handle
>>>>>> and setup the form submission one time.
>>>>>>
>>>>>> I'm not sure if it does in every browser. You may be able to simulate
>>>>>> this with synthetic events, using fire() on the form to send out the
>>>>>> broadcast, and observe() on the DIV to receive.
>>>>>>
>>>>>> Walter
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Prototype & script.aculo.us" group.
>>>>>> To post to this group, send email to prototype-s...@googlegroups.**co
>>>>>> **m.
>>>>>> To unsubscribe from this group, send email to
>>>>>> prototype-scriptaculous+**unsubs**cr...@googlegroups.com.
>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>> group**/prototype-scriptaculous?**hl=en<http://groups.google.com/group/prototype-scriptaculous?hl=en>
>>>>>> **.
>>>>>>
>>>>>>
>>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Prototype & script.aculo.us" group.
>>> To view this discussion on the web visit https://groups.google.com/d/**
>>> msg/prototype-scriptaculous/-/**zJ7lmI3W-5UJ<https://groups.google.com/d/msg/prototype-scriptaculous/-/zJ7lmI3W-5UJ>
>>> .
>>>
>>> To post to this group, send email to prototype-s...@**googlegroups.com.
>>> To unsubscribe from this group, send email to prototype-scriptaculous+**
>>> unsubscr...@googlegroups.com.
>>> For more options, visit this group at http://groups.google.com/**
>>> group/prototype-scriptaculous?**hl=en<http://groups.google.com/group/prototype-scriptaculous?hl=en>
>>> .
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Prototype & script.aculo.us" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/prototype-scriptaculous/-/BO6tcIh9qLQJ.
>
> To post to this group, send email to
> prototype-scriptaculous@googlegroups.com.
> To unsubscribe from this group, send email to
> prototype-scriptaculous+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/prototype-scriptaculous?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com.
To unsubscribe from this group, send email to
prototype-scriptaculous+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/prototype-scriptaculous?hl=en.
