Error thrown when closest() calls matchesSelector method

Reported by:	dygerati@gmail.com	Owned by:	dygerati@gmail.com
Priority:	undecided	Milestone:	1.6
Component:	unfiled	Version:	1.4.4
Keywords:		Cc:
Blocked by:		Blocking:

Description

Error is as follows:

expr.replace is not a function

This occurs due to the closest method calling calling jQuery.find.matchesSelector() with improperly typed arguments. The second parameter (selectors), should be passed as a string, but is an object.

At least I think that's whats going on :D.

This offending line is 4424 in uncompressed 1.4.4.

Attachments (0)

Change History (4)

Changed December 15, 2010 07:19PM UTC by jitter comment:1

owner:	→ dygerati@gmail.com
status:	new → pending

Thanks for taking the time to contribute to the jQuery project by writing a bug report but with information you provided it is not possible to determine if there is a bug.

So please submit a reduced test case, which reproduces the issue you are experiencing, on http://jsfiddle.net. Then we will be happy to investigate this issue further.

How to report bugs

Changed December 16, 2010 10:54PM UTC by anonymous comment:2

Honestly, I'm just not certain under what circumstances that part of the closest method is executed. There are hundreds of calls to matchesSelector() in our environment and only those originating from the closest method seem to exhibit this issue. It's clear if you look at the offending code that the parameters passed are of the wrong type.

Thanks,

Joel T

Replying to [comment:1 jitter]:

Thanks for taking the time to contribute to the jQuery project by writing a bug report but with information you provided it is not possible to determine if there is a bug. So please submit a reduced test case, which reproduces the issue you are experiencing, on http://jsfiddle.net. Then we will be happy to investigate this issue further. ----- How to report bugs

Changed December 16, 2010 11:15PM UTC by ajpiano comment:3

Surely you can create something on jsFiddle that simulates the conditions of your environment and shows the same error? That's all we need to continue...

(Hint: Use the Stack Trace in your debugger when the code throws an error to find which line of your own code invoked it)

If you can't, then it's very hard for us to see what's going wrong, or if it is just a problem with your environment or page.

Changed December 31, 2010 08:00AM UTC by trac-o-bot comment:4

resolution:	→ invalid
status:	pending → closed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Side navigation