The array literals fix worked, thanks. Next up: the changes around equality are a problem. <div><br></div><div>Specifically, the NULL operator, which used to evaluate to true on both null and undefined, now applies strict equality, meaning that (null undefined) is false. Since we use the NULL operator in a great many places precisely to check whether something is null or undefined, this change breaks our code. In general, I&#39;ve found it to be good to conflate null and undefined in most of our PS code; it simplifies things and works fine. So I guess we have to go on record as protesting this change... especially since there already existed ways to distinguish null from undefined in the minority case when it&#39;s needed.<div>

<br></div><div>Others&#39; thoughts?</div><div><br></div><div>Dan</div></div><div><br></div><div>p.s. I haven&#39;t looked closely at the other implications of the equality changes, because the NULL issue is such a big one that I thought I&#39;d start there.</div>