Upon further investigation, it looks like our reference systems may be flawed. We'll be testing on about 100 systems today, and it looks like the 5 QA reference system we were using yesterday may be having problems due to the test automation software that was installed.
A clean machine (Win2k as mentioned previously) passes all Mochikit test fine, but after installed the automated test client, the javascript error appears. So we're trying to isolate what the test client is doing to screw up javascript...specifically with that syntax. More information as it becomes available. I'm pleased that it looks like it's not some weird browser version problem. -L Bob Ippolito wrote: > That syntax is part of the ECMA spec and has been with JavaScript for > a very long time. I can't imagine that they'd break it in an update. > > -bob
