sizzlejs.com, as data

### Uh oh!The arguments for a filter method are the element and the captures from the regex corresponding to this filter (indicated above by what is in the match, starting at index 1). The return result must be boolean: true if the element matches the selector, false if not.#### `Sizzle.selectors.attrHandle.LOWERCASE_NAME = function( elem, casePreservedName, isXML ) {}`Handle an attribute which requires specialized processing (such as `href`, which has cross-browser issues). The return result must be the actual string value of that attribute.#### `Sizzle.selectors.pseudos.NAME = function( elem ) {}`*The most common extension to a selector engine*: adding a new pseudo. The return result from this function must be boolean: true if the element matches the selector, false if not.For example, this defines a simple `:fixed` pseudo:Sizzle.selectors.pseudos.fixed = function( elem ) {return $test.css( "position" ) === "fixed";#### `Sizzle.selectors.createPseudo(function)``createPseudo` is only required if the custom pseudo-selector accepts an argument.**Note**: In jQuery 1.8 and earlier, the API for creating custom pseudos with arguments was broken. In jQuery 1.8.1+, the API is backwards-compatible. Regardless, the use of `createPseudo` is greatly encouraged.Now that the parser compiles a single function containing other functions, custom pseudo-selectors with arguments are much cleaner.For example, within Sizzle, the implementation of the `:not( <sub-selector> )` pseudo is very similar to:`Sizzle.selectors.pseudos.not =Sizzle.selectors.createPseudo(function( subSelector ) {var matcher = Sizzle.compile( subSelector );Backwards-compatible plugins for pseudos with argumentsIn order to write a custom selector with arguments that can take advantage of the new API, yet still support all versions of Sizzle, check for the `createPseudo` method.The following example uses jQuery syntax. Live example`// An implementation of a case-insensitive contains pseudo