On Fri, Jan 15, 2010 at 1:27 PM, DBJDBJ <dbj...@gmail.com> wrote: > That would not be technically demanding but would be very usefull ...
"Not technically demanding" uh? I beg to differ on this one. First of all, what would the criteria be? If you can't see why this is a problem, maybe someone will explain it to you. Secondly: pretty much all of the JQuery classes and functions can use server side tags and code. The library has *no* knowledge(and rightfully so, imho) of what tags and/or selectors will be used. Thirdly: you'd have to scan what tag(s) is(are) associated with the selector. This would slow things down *A LOT* with many checks. Mind you, a JQuery tabs class may have any number of tabs for instance. Now do the checks for *all objects*. Fourth: plug-ins would have to do the same checks. Alternatively, they would have to be limited by the checks performed in JQuery. Both solutions are - imho - unacceptable. Fifth: *ANYONE* using improper selectors or using JQuery improperly deserves his/her fate. Reading the docs is the first thing you should do. All this, of course, imho. > --DBJ -- Andrea Raimondi Senior Software Analyst&Developer
-- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
