2007/9/13, Flesler <[EMAIL PROTECTED]>:
>
> My opinion.. Live Query is a great plugin, but it's not the fastest
> way to do that (although it is the safest, easiest, cleaniest). All
> the work I made on tables, I solved it using event delegation. Instead
> of binding, unbinding, rebinding, bind once to the container (the
> table or the tbody) and solve it from there. I made a plugin for that
> (jQuery.Intercept) if you are interested. jQuery.Bubble can be useful
> as well...
>
hi ariel,
i tried your plugin. it seems a good strategy to fight slowlyness... i
didn't get the 4th parameter to work. as i understand it, i should be
able to narrow the context of the listener.
ex: i want to listen to all clicks on <a> elements that are *within
the navigation div*
$.listen("#navi a", 'click', function(e){
console.debug(this);
console.debug(e);
e.preventDefault();
$("#content").load(this.href);
};
works for the whole document
same to this one..
$.listen("a", 'click', function(e){
console.debug(this);
console.debug(e);
e.preventDefault();
$("#content").load(this.href);
}, document.getElementById("navi"));
the same goes to "#navi" or $("#navi")...
what am i doning wrong?
cheers,
robert
> Ariel
>
> On 13 sep, 09:20, Phillip B Oldham <[EMAIL PROTECTED]> wrote:
> > We've been using jQuery (1.2 since its release) with a webapp we're
> > building, and it's all been plain-sailing, until now.
> >
> > We've got a table which uses livegrid to load in new rows. 2 out of
> > the 4 columns contain elements which have events bound using livequery
> > (so any new rows also get bound). When we get to more than say 20
> > rows, the app sees serious degredation in speed on FF (untested
> > elsewhere), rendering it pretty-much unusable.
> >
> > Has anyone else come across similar issues? Are there any common fixes
> > for this sort of problem?
>
>
