Yeah, this was a really unfortunate change that had to be made. We
really wanted to keep the extensible functionality of [EMAIL PROTECTED] but it
ended up being just to incredibly slow. Moving all of the code
internal was the only way to receive any sort of speed up. Sorry about
that guys.
--John
On 7/5/07, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote:
On Wed, Jul 04, 2007, Ralf S. Engelschall wrote:
> On Wed, Jul 04, 2007, Diego A. wrote:
>
> > Hi John (and the team),
> >
> > Congratulations on the new release, it's looking great. Can't wait for
> > 1.2...
> >
> > The only small problem I've had is with an old plugin I've been used
> > for a while, which adds regular expression selectors:
> > (function($){
> > $.extend($.expr['@'], {
> > "=~": "z.match(RegExp(m[4]))!=null",
> > "!~": "z.match(RegExp(m[4]))==null"
> > });
> > $.parse[0] = /^\[ *(@)([a-z0-9_-]*) *([!*$^~=]*) *('?"?)(.*?)\4 *\]/
> > i;
> >
> > })(jQuery);
> >
> > In 1.1.3, $.expr['@'] is null and causes an error.
> > Has $.expr['@'] been dropped?
>
> Seems like the jQuery.expr stuff is now replaced by some inline code, so
> AFAIK the above way of adding the regex matching is no longer possible.
The jQuery patch (sorry, no jQuery extension possible here AFAIK)
I'm now personally using is:
Index: src/jquery/src/selector/selector.js
===================================================================
--- src/jquery/src/selector/selector.js (revision 2248)
+++ src/jquery/src/selector/selector.js (working copy)
@@ -343,6 +342,8 @@
z = jQuery.attr(a,m[2]) || '';
if ( (type == "" && !!z ||
+ type == "=~" &&
z.match(RegExp(m[5])) != null ||
+ type == "!~" &&
z.match(RegExp(m[5])) == null ||
type == "=" && z == m[5] ||
type == "!=" && z != m[5] ||
type == "^=" && z &&
!z.indexOf(m[5]) ||
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
