Custom matchesSelector doesn't work in FF 3.6

[josh@…]

This is a Sizzle bug specifically, but I'm not sure if this is the correct issue tracker.

Can be reproduced with a simple test case:

jQuery.find.matchesSelector($('input')[0], ':input')
// returns false

On old FF, invalid selectors passed to mozMatchesSelector would always return false instead of correctly throwing an exception. There used to be a feature detect in Sizzle to test for this.

// This should fail with an exception
// Gecko does not error, returns false instead
try {
  matches.call( div, "[test!='']:sizzle" );
  rbuggyMatches.push( Expr.match.PSEUDO );
} catch ( e ) {}

[sindresorhus]

Does this still happen with 1.8 final?

If yes, please create a jsfiddle testcase and report the issue on the ​Sizzle bug tracker.

[anonymous]

Yes, 1.8 final is still broken.

​https://github.com/jquery/sizzle/issues/142

[dmethvin]

jQuery 1.8 doesn't support Firefox 3.6 since it's no ​longer supported by Mozilla as of April this year. Is there a reason you still need to support it, given that there are no security patches being created for example?

[anonymous]

Thats fine. Just didn't see anything in the release notes about it.