Seaside anchors and #click event bubbling

Hi there,

        I need to understood better how anchors work and how they do in Seaside.
I need to be able to make them to execute the callback action even when the
click event is stopped in parent elements. Right now seems that Seaside needs to
complete the click event bubbling to execute an anchor action and I really need
to stop the bubbling before the bubbling completes without a lack of anchor
action execution.

        Any pointers/readings will be very much appreciated,

        thanks

Sebastian Sastre


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

>         Any pointers/readings will be very much appreciated,

This has absolutely nothing to do with Seaside.

See: http://www.quirksmode.org/js/introevents.html

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Probably I wasn't making the right question. It was easier than it sounds.
For the record I've achieved it by making:

window.location.href="http://localhost:9090/blahapp?_s=RTVYmewBoGXMVFVz&_k=YFZtd
ORz&5"

So.. when you hook the click event in some anchor, then stop the event (so
hooked parents dont see it) and then make the anchor's href to be assigned to
the window.location.href you got it: an anchor which'll make a Seaside full
render programatically invoked using javascript.

For submit buttons the story is different. They have this function .click()
which seems appealing at first but for this case of use it's useless due to the
stop of the click event. There is no problem in send submit() to the form but I
think I need more than that because Seaside use to identify the submit button
pressed to perform the button's callback and seems is using the button name
attribute. I'm still trying to figure out that part.

Note this will be usefull also for the future when Seaside where able to work
fully ajaxian,

        cheers,

Sebastian
 

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

>  For submit buttons the story is different. They have this function .click()
>  which seems appealing at first but for this case of use it's useless due to the
>  stop of the click event. There is no problem in send submit() to the form but I
>  think I need more than that because Seaside use to identify the submit button
>  pressed to perform the button's callback and seems is using the button name
>  attribute. I'm still trying to figure out that part.

You can give the button an ID and use that from JavaScript. IDs are
used to identify DOM nodes, names are used to name submit fields.

I still don't get what this has to do with Seaside? ;-)

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

>
> You can give the button an ID and use that from JavaScript. IDs are
> used to identify DOM nodes, names are used to name submit fields.
>
> I still don't get what this has to do with Seaside? ;-)
>
> Lukas
>
Thanks, I see now I need to generate a POST programmatically with the fields you
mention.

It has to do with Seaside because I'm adding a new way to invoke the callbacks
we use to use in full renders. This new way is more prepared to intense AJAX. As
I previously said I want to use the click event in some child node (invoking the
seaside callback) and, at the same time, preventing the parents to receive this
click event (due to their own reactions at UA level).

        cheers,

Sebastian

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside