Klaus Hartl schrieb:
> My assumption was wrong (sorry Brandon for the false alarm). That 
> happens if I attach a custom 'activate' event (for the history support). 
> This was done to have access to the plugin settings...: Ugh.
> 
> tabs.bind('activate', function() {});
> 
> Still no idea how to fix this.

I'm talking to myself a little bit in this thread :-)

The reason is dead simple. Never call a custom event "activate", because 
IE has a built-in onactivate event.

Sorry for the noise.


-- 
Klaus

_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/

Reply via email to