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 in the code, that translates to a > Selector with a '*' expression. Using next(null, 1) solves the > slowdown problem. Also, since this might be related, > getElementsByClassName is also very slow in this release.
Possibly because those methods tend to DOM-extend every node on the way, and IE is the only browser that doesn't support native prototypes for DOM stuff. That should be avoided if possible, especially in getElementsByClassName. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
