On 2/3/07, Christophe Porteneuve <[EMAIL PROTECTED]> wrote: > > > I propose a rather simple patch to findFirstElement that would take this > into account: if at least one non-hidden (at the current level of > testing, that is, not accounting for container visibility), enabled > field has a tabindex, the one among those with the lowest value would be > the "first element."
+1 from me Regarding visibility: I don't think you should check for CSS visibility; I would only check for type=hidden or "disabled" properties. That seems enough. Christophe, I believe the speed reduction of the method would be insignificant? -m --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
