This was intentionally removed. Including extra code for doing code evaluation was seriously affecting other environments like Adobe AIR and Caja. (Not to mention the fact that having those code strings was probably just a bad idea to begin with.)
We deprecated that behavior a while back, actually, and just finally got around to removing it in 1.3. In this case the switch to using functions for the selector filters isn't that much harder. --John On Thu, Feb 12, 2009 at 8:46 AM, THD <[email protected]> wrote: > > Custom expressions like the ones in jQMinMax fail with an error when > used in the selector. (jQMinMax is found here: > http://davecardwell.co.uk/javascript/jquery/plugins/jquery-minmax/) > > All browsers fail with an error that 'filter is not a function' in the > line: > return filter( elem, i, match, array ); > > Is the old method of adding a new expression as a string instead of a > function not valid anymore or was this method wrong from the start? > > Old method: $.expr[':']['expression'] = expr; // this works in 1.2.6, > but fails in 1.3.1 > Simple fix: $.expr[':']['expression'] = function(a) { eval(expr); } > > Maybe jQuery can check if the expression is a string and use the eval > to create a function, this way scripts like the old jQMinMax won't be > broken by upgrading to 1.3.x. > > Regards, > THD > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" 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/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
