That was wrongly said. Replace "is because of Event Delegation" for
"is because of event bubbling, what you did was using event
delegation".

Ariel Flesler

On 5 ene, 20:52, Ariel Flesler <[EMAIL PROTECTED]> wrote:
> Checkhttp://docs.jquery.com/Frequently_Asked_Questions#Why_do_my_events_st...
>
> You can also do (suppose this is the way you generate the elements):
>
> $('<select id="id_of_select">...</select>').change(function()
> {}).appendTo('#id_of_div');
>
> The reason why binding to the div did work, is because of Event
> Delegation:http://icant.co.uk/sandbox/eventdelegation
>
> Ariel Flesler
>
> On 5 ene, 17:37, jason <[EMAIL PROTECTED]> wrote:
>
>
>
> > You can use .find() to "find" the dynamically generated elements
> > within the nearest static parent, i.e.:
>
> > $('#id_of_div').find('select').change(...);
>
> > Or, you can use the Live Query plugin to create your bindings if you
> > know the target is dynamically generated:
>
> >http://plugins.jquery.com/project/livequery
>
> > - jason
>
> > On Jan 4, 10:42 am, guellichs-erbe <[EMAIL PROTECTED]> wrote:
>
> > > Hello *,
>
> > > I've dynamically ( per javacript) generated <select/> lying in a div
> > > container (statically defined in <body/>).
>
> > > It does not work to bind a function to this select ($
> > > ("#id_of_select").change(...).
>
> > > $("#id_of_div).change(...) does work and is my workaround at the
> > > moment.
>
> > > But this means, that it is impossible to generate markup only
> > > dynamically, you always have to define your div/span/wathever
> > > containers.
>
> > > Is this right?
>
> > > Happy jQueriying
> > > Uli- Ocultar texto de la cita -
>
> > - Mostrar texto de la cita -- Ocultar texto de la cita -
>
> - Mostrar texto de la cita -

Reply via email to