I've researched this issue with Policies Manager toggling different js-restrictions on/off.
This was about setting timer.
That is working setting.
I think (after digging into page source) this is this function effect:
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-295158-1");
pageTracker._trackPageview();
pageTracker._trackPageLoadTime();
} catch(err) {}</script>
Speaking generally, I think using Policies may be the way to get KM-1.6 compatibility with such modern-scripted sites.
Most obvious decision is to create Policy with all JS-option boxes unchecked (
image below). It doesn't affect actual content generally but effectively prevents unwanted script behavior.
It's almost same effect as 'Secure-High' option in
dugbug's build but a bit more complicated (needs extension and some setting up) but the same time it's more universal and customizable in order to handle differently coded sites, if needed.
Edited 3 time(s). Last edit at 12/01/2011 01:05PM by rodocop.