matchesSelector is missing oooOOOOOooOOoOOO!

[jonathantneal]

Line 4987 of ​http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.js reads:

matches = html.matchesSelector || html.mozMatchesSelector || html.webkitMatchesSelector || html.msMatchesSelector;

Whoa whoa whoa, buddy, hang on a minute, cause nobody is singing' but I swear it looks like somebody prematurely ended an Opera. Ahem, OPERA, ahem!

Oh yea! html.oMatchesSelector? Yea! html.oMatchesSelector!

Think of how much you could improve the experience of dozens upon dozens of web users by patching this.

​http://caniuse.com/matchesselector

​http://bit.ly/pcKuoK

[dmethvin]

Well considering they just added it in 11.5, we aren't too far behind. Seems like an easy fix though.

you could improve the experience of dozens upon dozens of web users by patching this

Will you be here all week?

[miketaylr]

Heh, nice catch. I can send along a pull request later this afternoon.

[jdalton]

Keep in mind matchesSelector is still pretty buggy: ​http://dl.dropbox.com/u/513327/chrome_matchesselector_bug.html

NWMatcher pulled its matchesSelector support because it was slower (with all the checks) than its manual match method.

​https://github.com/dperini/nwmatcher/issues/40 ​https://github.com/dperini/nwmatcher/commit/10a48ac54c3673c125c540447bb74c75cd1a9ed4

[miketaylr]

Oof, looks buggy indeed in Webkit--passing in Opera. ;)

[miketaylr]

​https://github.com/jquery/sizzle/pull/74

[Timmy Willison]

I think we should consider removing all matchesSelector usage as well.

[Timmy Willison]

matchesSelector has been removed.