On May 25, 3:10 am, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> It calls Element.hasClassName for every node, I hope we can agree on that.
> Now, let us remember what do methods from the Element namespace all have in
> common.
>
> Hint: it has something to do with the first argument and the $ f
On 5/25/07, Andrew Dupont <[EMAIL PROTECTED]> wrote:
>
>
> It extends only those nodes that match the class name.
It calls Element.hasClassName for every node, I hope we can agree on that.
Now, let us remember what do methods from the Element namespace all have in
common.
Hint: it has something
As a side note, the bigger the document you are working with is, the
slower the methods will be - obviously!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send emai
On May 24, 5:53 am, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> Andrew, it doesn't matter - getElementsByClassName tends to extend EVERY
> node in the document! If that isn't slow I don't know what is.
No, it doesn't. It extends only those nodes that match the class
name. I've personally spen
On May 24, 5:40 am, Andrew Dupont <[EMAIL PROTECTED]> wrote:
> On May 23, 7:16 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>
> > With the latest prototype (1.5.1), the next() function (and probably
> > also prev() and the rest of the navigation function) cause a
> > tremendous slowdown
On 5/24/07, Andrew Dupont <[EMAIL PROTECTED]> wrote:
>
>
> > Also, since this might be related,
> > getElementsByClassName is also very slow in this release.
>
> Compared to which release? Care to post some benchmarks?
Andrew, it doesn't matter - getElementsByClassName tends to extend EVERY
node
On May 23, 7:16 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> With the latest prototype (1.5.1), the next() function (and probably
> also prev() and the rest of the navigation function) cause a
> tremendous slowdown in IE if they are used with the following syntax:
> next(Number). From what
On 5/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> With the latest prototype (1.5.1), the next() function (and probably
> also prev() and the rest of the navigation function) cause a
> tremendous slowdown in IE if they are used with the following syntax:
> next(Number). From what I saw
