unfiled → event
1.next → 1.5.1
undecided → high
new → assigned
Thanks for taking the time to contribute to the jQuery project by writing a bug report and providing a test case (http://jsfiddle.net/LtDan__/JwKP8/).
After checking your report I took the time and had a look at this and came up with the following:
- works in Chrome 8.X
- doesn't work in Chrome 9.X-stable and 10.X-dev
- works if you manually attach to mouseover/mouseout test case no jQuery
- doesn't work with
.hover() jQuery test case
- both test cases work in all other browsers
This already gives a good indication that this is a regression in Chrome. So what is actually happening? When moving from the div to the input field Chrome fires a
mouseout event where the
relatedTarget property is set to some "internal detached div" instead of the actual input element.
So this is definitely a bug in Chrome as it sets relatedTarget to an element that shouldn't be accessible to user code. It has already been reported here http://code.google.com/p/chromium/issues/detail?id=68629 over a month ago, but there was no action taken and now this bug made it into a stable release.
So although this is a bug in Chrome, I will fix this in jQuery as it's easy enough to workaround this (because we already check for a similar bug with FF).
But again: This is a bug in Chrome. Go on and comment on the ticket linked to above and urge them to fix it.