This is an issue I raised on StackOverflow at: ​http://stackoverflow.com/questions/3177446/slidetoggle-hover-animation-queue-issue

Basically is that when trying to use slideToggle() with hover() you get the animation queuing. I attempted to remedy this with stop() but this then caused the animation to stop working. The SO post contains a lot more info.

This JSFiddle: ​http://jsfiddle.net/SNhky/ contains the code that doesn't work.

I'm using Chrome 6.0.453.1 dev, but this error occurs in IE8 as well.

As demonstrated with this jsFiddle (​http://jsfiddle.net/yt7Jd/2/), the focusin even isn't being triggered when .focus() is called.

This appears to be a bug introduced in 1.4.3 as when you change the jQuery version 1.4.2, it works correctly (as seen in this jsFiddle ​http://jsfiddle.net/yt7Jd/1/

I am testing on Chrome Stable 7.0.517.41

line 514 of jquery-1.8.2.js

 return window.JSON.parse( data );

triggers error in firefox 15.0.1

Exposing chrome JS objects to content without __exposedProps__ is insecure and deprecated. See https://developer.mozilla.org/en/XPConnect_wrappers for more information.
file:///pject_folder/js/jq/jquery-1.8.2.js
Line 514

I was willing and able to simple delete jqm when it started causing such errors, but this I can't overlook. I'll call it a 'feature' issue, because I'm sure the expected behavior is to be in violation at this time.

Typically none disclosures and extreme complexity (in real world application/usage), make it pretty difficult for me to simply provide proof publicly, but you should know this stupid exposed props thingy is really causing a lot of problems.

Anyway I'll keep looking into it from this end, but it's strange that the jQuery code does not handle my basically simple usage well.

during a hashchange event I'm extracting some object parms from an xml file that's already loaded...

<state name="center" type="css"> { "left": 0, "top": 0, "z-index": 100 } </state>

via...

 return jQuery.parseJSON(objString);

which is called from textContent of the shown xml of course...

 $.extend(changes, getObjectFromString(item.textContent));

I'll keep hacking at it I guess (no other choice) but maybe this is really more officially a bug, it really shouldn't barf out (down the road, early warning for now) in this situation I don't think?