Skip to main content

Bug Tracker

Side navigation

#12196 closed bug (invalid)

Opened August 04, 2012 03:55PM UTC

Closed August 14, 2012 11:46AM UTC

Last modified August 14, 2012 04:49PM UTC

Custom matchesSelector doesn't work in FF 3.6

Reported by: josh@joshpeek.com Owned by:
Priority: low Milestone: None
Component: selector Version: 1.8rc1
Keywords: Cc:
Blocked by: Blocking:
Description

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 ) {}
Attachments (0)
Change History (4)

Changed August 14, 2012 11:46AM UTC by sindresorhus comment:1

component: unfiledselector
priority: undecidedlow
resolution: → invalid
status: newclosed

Does this still happen with 1.8 final?

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

Changed August 14, 2012 04:26PM UTC by anonymous comment:2

Yes, 1.8 final is still broken.

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

Changed August 14, 2012 04:28PM UTC by dmethvin comment:3

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?

Changed August 14, 2012 04:49PM UTC by anonymous comment:4

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