Reading these discussions and how fragile the detection of "undefined"-ness can be in some situations, now I am beginning to see the cause of the bug reported in https://groups.google.com/forum/#!topic/mozilla.dev.tech.js-engine/EkJwTOZUmv0
and specifically Bug 1003240 - JS Engine reports FALSE-POSITIVE(?) "strict warning" for "undefined property" under a certain condition Now that the particular strict warning does not get produced any more [I checked yesterday], maybe I should close the bug 1003240 (assuming that the JS engine's handling of this issue more correct or more in line with user expectation.) ??? What do people involved in JS Engine development think? TIA _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
