Tamas Rudnai gmail.com> writes: > There is something with the script engine I think (maybe there are some > other rendering issues as well). It all goes back to developers testing the JavaScript insufficiently on 'other' platforms. Due to JavaScript implementation incompatibility a working JavaScript function written for windows can become a denial-of-service type resource hog on other platforms, in the form of an endless loop with high resource utilization or other coding horrors. The fact that JavaScript mostly continues by default instead of stopping on errors in a program (consistent with the potentially human-deadly 'ignore unknown tags' policy in plain html) does not help here. The short version: sufficiently compatible sites which are tested for cross-browser compatibility with the 4 main broswers: IE, Firefox, Opera and Safari, work flawlessly, beyond that, it's a bog, and *do* expect to sink in it. I have been using *nix as a destop for 12 years now and browsers with plugins and scripting turned on are the *only* applications I have that can require a session logout and login or even machine freeze + subsequent reboot. Server mode machines that run the exact same software (but not the browsers, plugins or 'proprietary' media players - who knows what coding horrors lurk in there) *never* need to be rebooted. Uptimes equal the time between mandatory kernel updates or upgrades, measured in several months to years. Old graffiti strategically placed on pub washroom wall comes to mind here to go with 'input garbage -> output garbage' in computers: 'beer in, beer out'. Peter -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist