> Bit of an strange effect, and for once it seems to be OK with IE7 but > not with Chrome.
Ooh... there was an issue with the JS framework we're using. We had a workaround in place. But when I updated the framework, the issue should have been fixed. Thus I removed the workaround. Though I tested with Safari only. Just to make sure... please do the clean your cache and force a reload routine. Maybe it's still using the old framework's .js file, while running our latest code with it. Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
