> I have fixed history support for IE in the history plugin. Maybe it's > now 0.1 and it's also in SVN now. Does it still eat up your processor? > Which browser? The only way to make history work is constantly poll > changes in the location.hash property - sigh. That sucks, its one giant > hack and I wish I hadn't started at all with that.
Ok, the version you commited works better then the one included with latest tab plugin. At least the problem in FF is gone. > I couldn't reproduce the other bug, maybe it had to do with the history > as well? No. The tabs plugin behaviour, with or without history, is quite weird. I'll try to render and extract the parts that show the problem. Debugging with browser-processed XSLT isn't that nice. -- Jörn Zaefferer http://bassistance.de -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
