On 5/6/10 10:44 AM, Stewart Brodie wrote:
Taking the null, explicit undefined and implicit undefined test cases together, I don't think I've got any two browsers here that behave the same way. :-/
Yes, that's why we can't exit CR. ;)Note that part of the issue here is that the spec flip-flopped on its desired behavior and some of the browsers' shipping versions are still implementing the previous version of the spec.