The point is, it's more likely the broken code you're using/writing being the issue, than it is jQuery's compatibility with IE10 being the issue.
Yes, old IEs can be a pain to work with, but the problem here could be several things specific to IE10, possibly it being more strict about certain things than Firefox or Chrome, or like Matt said, transparent elements over the target, or some slight difference in how IE interprets some CSS.
The point is
you don't know, which is why everyone is telling you to open IE's console/dev tools and find out what the actual cause of the problem is, and fix that, rather than resorting to horrible inline-JS hackery.
EDITED: 27 Aug 2013 15:19 by CAER