[jQuery] Re: Help Test jQuery 1.1.3

2007-06-07 Thread Volker Mische
Hi, > I've added a new patch to the ticket based on Volker's patch. Can you please > confirm that it does indeed fix the problem?http://dev.jquery.com/ticket/1143 No it doesn't work as it doesn't travers all node recursively. I've written a new patch, please take a look at http://dev.jquery.com/

[jQuery] Re: Help Test jQuery 1.1.3

2007-05-25 Thread Volker Mische
Hi, > > I have to admit that I haven't found a faster solution. > > removeAttribute() just takes to much time. So perhaps the serializer > > should be "fixed". This would mean a slow down for Internet Explorer > > on html(), but this seems ok for me, as this is a Internet Explorer > > bug. > > Th

[jQuery] Re: Help Test jQuery 1.1.3

2007-05-24 Thread Volker Mische
thing different: merge() uses "for ( var i = 0; second[i]; i++ )" for loops, all other cases where such a loop was used, it's like "for ( var i = 0, fl = first.length; i < fl; i++ )". If the way merge() does it work a few bits could be saved. Cu, Volker. PS: Sorry for mul

[jQuery] Re: Help Test jQuery 1.1.3

2007-05-24 Thread Volker Mische
I think mergeNum won't be added everytime, it gets only added if you need to run an uniqueness test (when find() was called). I even think unique() can be removed when merge gets changed a bit. I've some ideas, at the end it should be faster and have a smaller file size. Cu, Volker. On 24 Mai,

[jQuery] Re: Help Test jQuery 1.1.3

2007-05-24 Thread Volker Mische
Hi, On 24 Mai, 22:39, "John Resig" <[EMAIL PROTECTED]> wrote: > $(...).find("*").each(function(){ delete this.mergeNum; }); This won't work in Internet Explorer. > Having the value come up as mergeNum="null" tells me that there's > something very wrong at play here. What exactly are you using