Bug Tracker

Opened 7 years ago

Closed 7 years ago

#12201 closed bug (wontfix)

Sizzle filter api incompatible when adding a custom pseudo selector

Reported by: softlion@… Owned by:
Priority: low Milestone: None
Component: selector Version: 1.8rc1
Keywords: Cc:
Blocked by: Blocking:

Description

This code works on 1.7.2 and fails on 1.8 RC1 with error Uncaught TypeError: Cannot read property '3' of undefined.

$.extend($.expr:?, {

someOp: function(a, i, m, s) {

var dist = parseInt(m[3]); ... return false;

}

});

Change History (2)

comment:1 Changed 7 years ago by softlion@…

jsFiddle demonstrating the problem: http://jsfiddle.net/VuWNg/

comment:2 Changed 7 years ago by timmywil

Component: unfiledselector
Priority: undecidedlow
Resolution: wontfix
Status: newclosed

The new way to create custom pseudos with arguments is much clearer and faster.

The documentation can be found here: https://github.com/jquery/sizzle/wiki/Sizzle-Documentation#wiki-pseudo-selectors.

Your example adjusted to conform to the new API: http://jsfiddle.net/timmywil/VuWNg/1/

Custom pseudos that don't require arguments work the same way.

Note: See TracTickets for help on using tickets.